ReSkate
You are viewing a potentially older version of this package. View Latest Version
Install with App

Details

Date Uploaded
Downloads
1.7K
Size
23KB

Sponsorship Progression Core 0.6.7

The new architecture is sponsorship-only. Core owns shared saves, game observations and reward validation. Sponsorship Progression owns brand presentation; Sponsorship Challenges owns challenge rules and UI. Future sponsor packs register with Core through ReSkate's existing plugin APIs. The original 0.6.74 demo remains unchanged.

Current implementation

  • Core owns board sales, separate brand levels 1-25, contracts, game observations and one-time reward payments.

  • Challenges owns shoot definitions, score evaluation, timers, Owned/Killed tiers, assignment controls and the active challenge HUD.

  • Sponsors offers access to those assignments and retains brand cards, previews, contracts and the idle career HUD.

  • Sponsors can be signed immediately. There are no lessons, trick unlock requirements, skill percentages, proficiency, added bails or input interception.

  • Photo shoots: 60 seconds; Owned 1,500 points / 100 boards, Killed 3,500 / 175 boards. Best confirmed landed line counts.

  • Video shoots: 90 seconds; Owned 6,000 points / 250 boards, Killed 12,000 / 425 boards. Confirmed landed score gains are added across lines.

  • There is no consistency bonus. Native collisions/falls remain natural game behavior; their unlanded score gains are discarded.

  • Existing cumulative sales milestones are retained: 100, 250, 500, 900 and 1,250 boards reach levels 2-6. Level 25 at 26,900 boards completes a contract and unlocks switching.

  • Scores are read by Core and passed through the separate stateless challenge engine, not accepted from frontends. No frontend endpoint can award arbitrary boards. Submission is idempotent while cached and an assignment can only be paid once.

  • Assignment time pauses in menus. Map transitions, lost local-skater state or teleporting cancel the current run without rewards. Signing, progression and shoot rewards work in multiplayer sessions. Joining or leaving without a world reload keeps the current run. Your score and career remain local to your client.

  • The new career refuses to run while the old demo plugin is running. Disable the demo before testing all three new modules.

Core requests no skater-control permission and contains no wipeout calls. It has no overlay images. The first Sponsors pack has 15 images: 3 logos and 12 sheets of short silent hover previews. It preserves the native brush/tile styling, career HUD, board-sales XP bars and brand hover animations.

Layout

  • mod/: Core runtime and metadata.

  • ../sponsorship-sponsors/mod/: Sponsors frontend and its 15 images.

  • ../sponsorship-challenges/mod/: challenge engine, rules, controls, HUD and one native Y icon.

  • sdk/: connection helper for API 2 clients.

  • tests/: pure service and simulated two-plugin integration tests.

  • tools/migrate_demo.py: prepares a sponsor-only Core save candidate plus an exact original demo backup. It never overwrites an existing output.

  • archive/lesson-foundation-0.1.0/: preserved old foundation; excluded from all runtime packages.

Core uses API 2; the earlier unreleased lesson foundation's API 1 is retired. An existing schema-1 Core profile is backed up before converting its sponsorship section. Removed lesson/skill data is not used by the new runtime. Unsupported profiles are left untouched.

Test installation

Keep the demo installed as a fallback, but disable it in the launcher. Install the new modules into separate folders:












Mods/ZtupidModZ-Sponsorship_Progression_Core











Mods/ZtupidModZ-Sponsorship_Progression_Sponsors











Mods/ZtupidModZ-Sponsorship_Progression_Challenges











For the local development kit, close the game and run Update-Sponsorship-Progression-Test.cmd in the Core folder. The installer backs up all three existing module folders, preserves an existing Core save, and copies only the demo sponsorship section into a new Core save if one does not exist. It never changes the demo save or mods.json. You still enable/disable the modules in the launcher.

Each folder must contain its own manifest.json and reskate-plugin.json at the root. Enable all three modules in the launcher and approve their plugins when requested. Load order is handled by discovery/retry. Missing Challenges blocks shoot starts; an engine unload/reload cancels an unfinished run without paying boards. Open Insert > Sponsorship Progression to choose a brand. Its OPEN CHALLENGES button opens the separate challenge section. You can also use Insert > Sponsorship Challenges.

Do not run two copies of the same module. Do not replace the old demo folder with Core. The three development archives are not uploaded to Thunderstore. On publication, upload Core 0.6.7, then Challenges 0.6.7, then Sponsors 0.6.7. Challenges depends on Core; Sponsors depends on both.

Demo save migration

Migration is explicit. Core cannot read the demo's sandboxed storage on its own. Run this tool from the Core project to prepare files outside the live save directory:












python tools/migrate_demo.py --source <demo-storage.json> --output <new-core-storage.json>











It carries over the demo's sponsorship section (selected brand, sales and challenge totals), omits lesson/skill records from active Core data, and keeps the complete original as a .demo-backup.json. Stop the game, back up any existing Core storage.json, and review the candidate before placing it in Core's own plugin storage directory. Never overwrite a Core career that already has newer sales. The old demo save is never modified.

Developer console












rpscore on











rpscore status











rpscore sign enuff











rpscore unsign











rpscore sell enuff 1000











rpscore remove enuff 250











rpscore reset enuff











rpscore off











These are offline-only, explicitly armed tools. The first mutation backs up Core's profile. Commands cancel unfinished assignments; no lessons or skill records exist to alter. The distinct command name avoids a collision with the old demo's rpsponsor command.

Verified sources and limits

The implementation follows the installed 2.1.4-2 public scripting interfaces, confirmed in official source:

Exports use JSON-copy proxies; plugin events include host-provided sender identity. Only Core owns progression storage. Each independent frontend plugin has its own image-path allowance, but the renderer still shares a 32-picture cache and can recycle idle slots. This does not raise the runtime limit or enable full video playback. Only the active brand's owning frontend draws its career HUD.

The tests simulate three separate Lua environments, load-order recovery, requests/replies, score and landing events, fixed rewards, save isolation, contracts, expansion registration and demo/world-state guards. Online tests cover signing, rewards, session join/leave continuity, menu pause and cancellation on actual map/skater loss. Additional checks cover engine unload/reload, invalid result rejection, request deduplication and all four existing reward tiers. Live score update timing and multi-plugin rendering still need an in-game test. No live compatibility result is claimed.

Challenge service extraction

Core no longer ships assignments.lua. It discovers Sponsorship_Progression_Challenges engine API 1 and passes it copied run state and Core-observed score/landing data. Challenges evaluates the run without owning a save. Core retains the in-flight run, locks a definition at start, validates the returned tier and boards against that definition, and pays once. Neither Sponsors nor a challenge UI can directly award boards.

Core forwards observations at up to 10 Hz and retains the existing delayed ground-confirmation check for landings. Exact native update timing still needs testing. Missing, invalid, stopped or reloaded challenge engines cancel the run; they do not produce fallback rewards. Existing sponsor saves and milestones are unchanged. Update all three development modules together to avoid old and new HUDs overlapping.

Temporary shoots: native flag and explicit start

Choose Photo/Video, edit the temporary area and confirm NEXT: FLAG. Control passes to the game's stock native Throwdown setup page and flag picker. Place its real flag inside the selected area and confirm using the game's placement controls. No homemade flag mesh or triangle marker is drawn. Native placement from another mod is never replaced; a busy picker reports an error. Native flag cancellation returns without creating a shoot, and out-of-area placement returns to area editing.

Skate to the flag. Within three metres, the prompt reads Press [native Y graphic] To Start Shoot. A fresh Y press (or keyboard Y) requests start from Core; mere proximity never starts the shoot. Core independently checks the rider is nearby and grounded before arming the three-second countdown. Pre-start points/time do not count. The native flag retires once start is accepted. Photo/Video scoring then runs for its usual 60/90 gameplay seconds and pays automatically at expiry.

The gradient exists only on vertical boundary walls, fading upward. There are no ground/ceiling polygons or blanket over water. Gameplay walls use lower opacity than editing walls. Ground probes remain read-only and only assist placement/floor fitting. Areas and flags remain temporary and clear on completion, cancellation, map changes or module loss.

Challenges requests throwdowns permission to use the stock flag registration/placement API. It creates a one-player temporary Sponsor Shoot registration, not a network match, and publishes a waiting document solely to retain the native flag. It removes that registration/mode on start or cancellation. It uses one packaged image: the game asset UI/Textures/Icons/Inputs/XBOX/img_Xbox_Y_108_108_108 (108px RGBA), extracted with the existing ReSkate texture exporter. No runtime binaries are built. Core has zero image paths, Sponsors 15 and Challenges one.

Challenge service API 4 and Core 0.6.7 are required together. Automated tests cover explicit start/proximity, native placement events and ownership, Y artwork, vertical-only wall rendering, scoring and teardown. Native picker presentation still needs live playtesting.

Source references: ReSkate plugin_api_throwdowns.cpp flag.begin/state/leave; plugin_api_world.cpp throwdowns.mode; native_flag_session.cpp flag_placed/game/XYZ/yaw events and waiting lifetime. Installed Domination's native_entry.lua uses the same native event contract; no other mod code or assets were copied.

0.6.7 placement recovery

The reported log showed two 15-second native setup timeouts, and Core initialization failing because its page title exceeded the host's 24-character limit. Core now registers the shorter Progression Core page, and the simulated host enforces that native limit.

After area confirmation, the editor closes its own screen and waits at least 250ms, and for other interfaces to close, before requesting native setup. Challenges publishes the setup ownership document before native navigation and throughout placement, uses setup_page=true, and follows the native confirmation path. Confirm the native setup page, then place the flag. Failure or Back returns to the same edited area; it does not clear the vertices or start a scoring run. SDK ownership loss after timeout is detected and reported. Brief local-skater unavailability during setup releases the camera without discarding geometry; explicit map changes/cancellation still clear it.

Boundary walls now span the actual selected height, with a softer fill and exact bottom/top loops and four uprights. No horizontal fill is rendered. Regression tests reproduce the SDK timeout and preserve edited vertices beyond ten seconds. The native setup/picker still requires live verification; automated API mocks do not prove a world flag rendered.

Other Throwdowns

Tracked shared native Throwdowns award one board per 25 confirmed landed trick points when finished or left. Sales are saved once, and sponsorship HUD stays hidden during the match. Unlanded points do not pay. Own photo/video shoots are excluded. Community modes that do not use the shared native lifecycle require individual integrations; custom minigame scores are not read.

Thunderstore development is made possible with ads. Please consider making an exception to your adblock.