SpotPins
Save and scout per-map spots, publish native-map flags, export selected SpotPacks, and recover edits with controller-friendly menus.SpotPins
Find a spot you love, save it, and travel back whenever you want. Your spots stay organized by map, with notes, favorites, colored pins and full controller navigation.
Built for ReSkate 2.1.4-5-hotfix-2 with plugins enabled. Update ReSkate before installing.
Start here
- Press P to open SpotPins, or choose Plugins > Spot Pins > Open SpotPins and close the ReSkate/pause menu with Back. The workspace opens after you release the closing button.
- Choose Save Spot to keep your current location.
- Choose Travel beside a saved spot to return to it. Its More menu contains notes, rename, favorite, color, guide, update and delete.
- With a controller connected, close the menu after traveling and let the automatic native-marker attempt finish. Settings > Close after travel can close it for you.
Use the mouse wheel, scrollbar or D-pad to move through the list. A selects; B goes back or closes. The sidebar switches between Spots, History, Spot Packs, Settings and Session.
What's new in 1.7.0
- Smart Pins: nearby pins refresh on a cache, stay within your chosen range/count, and avoid overlapping names. Defaults: 24 nearest within 500 m. Configure Settings > Advanced > Pins / Recovery. The active guide stays independent of those limits; overlays hide in host menus and the replay editor.
- Selected SpotPack export: choose exactly which spots to share, then name your JSON. Up to 64 spots per file; larger libraries start unselected. Long valid names/notes export without shortening through extended v2 files, while short packs remain v1-compatible.
- Recovery snapshots: automatic before delete, position update and pack import, with manual Backup now and reviewed Recover missing spots in Spot Packs. Five rotating snapshots across maps; recovery adds copies and preserves current spots. Snapshots use their own file, separate from player-spot storage.
This release also fixes Scout keyboard capture, left/right arrival turns, shortcut conflicts and modifier handling; retains unknown saved preferences; and adapts opening/cleanup to ReSkate's native menu/replay state. No new permissions compared with 1.6.1. Read PACKS-AND-RECOVERY.md for formats, limits and paths.
Scout, map flags and Session
Scout Mode with adjustable flight: press F4 to start or end Scout, or open P > Scout > Start Scout. Fly without moving your skater, aim at a supported surface and press RT / Enter to name and save it. Y / G locks that destination and makes its arrival direction face the camera, with confirmation. Choose movement speed, look sensitivity, invert Y, aim range and arrival turn steps on the Scout screen. Record your own start/end shortcut or disable it. While flying, D-pad Up/Down or = / - changes speed; hold L3 / Shift for a 3x boost. Adjustable flight uses right mouse + mouse movement to look. The original Native / ReSkate flight mode remains available as a fallback; its movement settings belong to ReSkate. Scouted spots use the same library, packs and map separation as ordinary spots. Read SCOUT-MODE.md for controls and limits.
Native-map flags: publish this map's saved spots as individually tracked native QuickDrop flags. The Map Flags manager shows your spot names and present/missing/protected status, supports refresh/stop/cleanup, and keeps your saved list intact. The game's cards retain generic labels.
Reviewed Session packs: choose a player, review your current-map selection and send a whole SpotPack. Recipients review before importing; nothing automatically saves or teleports. Optional private chat shortcuts and a compact guide HUD are under Settings > Advanced > Integrations.
Read before updating: keep your installation folder/package identity unchanged to retain local player data. SpotPins 1.7.0 uses the same permissions as 1.6.1. When upgrading older builds, follow ReSkate's normal plugin approval screen.
Testing status: automated regression and ownership/input/collision tests pass. The original native Scout flight has been tried locally; the new adjustable flight, shortcut and revised Y behavior still need an in-game check. Several simultaneous local native-map cards and real multiplayer pack delivery also need live validation. These features are labeled experimental. A single native flag card and the native-marker controller gesture have been confirmed locally. The Studio-native guide frontend asset is not included; compact guidance is the working overlay.
Map-flag workflow added in this release
- One native flag per saved spot: open Map Flags beside Save Spot, choose Publish all, review and confirm. Each published spot has its own tracked flag rather than moving one shared flag. The batch uses all saved spots on this map, even if the list is currently filtered to Favorites or Search.
- Flag management: see named status rows and tracked/present/missing/protected counts. Refresh checks the world, Stop batch cancels remaining work, and Remove all asks before cleaning up this copy's verified flags. Your saved spots remain intact.
- Repair on Publish: removing a flag with the native map's X leaves it removed. The next explicit Publish recreates it in the same request; it no longer needs two attempts. Rename/reorder/position/heading updates retain the association through a private local spot identity.
The game's native flag cards keep generic labels such as Custom Placement. The current API does not accept per-object card names. SpotPins shows your names in Map Flags and preserves them in saves and packs. One local native-map card has been confirmed in-game; multiple simultaneous local cards still need testing. The batch stops if placing a flag makes an earlier tracked flag disappear.
Features added in 1.5.0
| Feature | How to try it |
|---|---|
| Native-map meetup flag | A saved spot's More > Publish map flag. Confirm to enable publishing and place or update that spot's own QuickDrop flag. |
| Session SpotPacks | Session > choose a player > Send map pack. Review your selection before sending; the recipient uses Session > Packs > Review pack > Add selected. |
| Local chat shortcuts | Enable under Settings > Advanced > Integrations, then use /spot in a lobby. If the name is taken, the settings show /spotpins instead. |
| Compact guide HUD | Enable under Settings > Advanced > Integrations, then choose More > Guide me. Shows camera-relative bearing and distance. |
Map flags, chat and the compact HUD are off by default. Pack sharing follows the main Session sharing switch and has its own switch under Integrations. No received spot or pack is automatically saved or traveled to.
Multiple simultaneous native-map flags and real multiplayer transfer still need in-game testing. The compact HUD uses SpotPins' working overlay; numeric bindings for a future Studio-native widget are prepared, but no native widget asset is included. See SCOUT-MODE.md for Scout controls and collision limits.
Features retained from 1.4.0
| Feature | What it does | Where to find it |
|---|---|---|
| Native session markers | Automatically attempts to update the game's own marker after SpotPins travel. Enabled by default; requires a connected controller. | Settings > Advanced > Auto marker |
| Record your shortcuts | Press your own key combination instead of choosing a preset. The list remains available for controller use. | Settings > keyboard key / Return key |
| A cleaner workspace | Square controls, consistent dropdowns, color-accented cards and clear controller focus across the custom screens. | Press P |
| Safer controller travel | Close after travel waits until A is released, preventing the same press from pushing the skater. | Settings > Close after travel |
| Choose your arrival | Explicitly request the board or an on-foot arrival. | Settings > Advanced > On Board |
Travel and the game's native marker
Auto marker is experimental and enabled by default. It has been confirmed working during local in-game testing. Different controllers, game states or other input mods may prevent it from running.
After an accepted travel request, SpotPins waits until you are near the destination and gameplay has input. It then waits 0.5 seconds and adds a D-pad Up hold to your connected controller. The default and minimum configurable hold is 1.2 seconds. You can change the delay, hold duration and controller under Settings > Advanced.
- Close menus after travel. The attempt waits while a menu is open and expires after 30 seconds. Close after travel is optional; release controller A to let it close.
- A message saying the game reported a marker save means SpotPins observed a native saved event. Sending Up alone is not treated as success.
- The attempt copies your real controller input and releases its temporary input layer when finished or interrupted. Another mod owning that controller can block it. Keyboard-only play without a connected controller cannot use this method.
- Turn Auto marker off to use the ordinary manual reminder instead. The reminder is on by default and also serves as a fallback when an automatic attempt fails; you can disable it in Settings.
ReSkate asks for input.write so SpotPins can briefly add Up to controller input, and marker.read so it can observe native marker-save events. This updates the game's session marker. The separate Map Flags feature explicitly publishes an individually tracked QuickDrop flag for each selected saved spot. Session markers and native-map flags are different game features.
Make the list yours
Open a spot's More menu to rename it, add notes, favorite it, change its pin color or visibility, and start guidance. Names wrap when needed; notes appear below them. Color and visibility controls keep the menu open while you edit.
Use All / Favorites to filter and Saved / Nearest to sort. Reorder changes your saved order: drag a grip with the mouse or use Move up / Move down with a controller. Choose Saved sorting to see that order. World markers can be hidden globally in Settings or individually in More.
Guide me displays a temporary target and distance, with a left/right cue when the target is off screen. Stop Guide in the sidebar ends it.
Position updates and deletion ask for confirmation. Undo Edit appears in the sidebar after a successful delete or position update. It restores the latest such edit on that map; another delete/update replaces it. Undo is held in memory and clears when the plugin reloads or the game restarts.
Shortcuts and controller use
P opens or closes the menu by default. In Settings, select the keyboard key and choose Record shortcut, press a letter, digit, F1–F12 or Space with optional Ctrl/Shift/Alt, then release to save. Choose from list is the controller-friendly alternative. Cancel, timeout or focus loss keeps the previous shortcut. ReSkate's own saved Binds overrides take priority.
The Return shortcut defaults to R, enabled. While skating, it returns to where you were immediately before your last SpotPins travel. It alternates between those two positions and only works on the current map. The return point and History are session-only.
An optional L3 or LB + L3 menu shortcut is available in Settings; it is off by default. D-pad Up/Down stays in the current section, Left reaches the sidebar from the leftmost control, and Right returns to content. B backs out of a dialog or screen before closing the workspace. Controller focus has a gold outline.
Native text editors remain in use for names, notes, search, filenames and coordinates so paste and game-supported text entry remain available.
SpotPacks: try, import and share
Spot Packs > Review starter offers three San Vansterdam spots: Seaside Park, Carvatron 2 and Casper Campus. Nothing is added automatically, and the starter spots are not marked as favorites. Review them, choose the ones you want, then select Add selected.
To export, choose Spot Packs > Export pack, select up to 64 spots, choose Export selected, enter a filename and save. A library larger than 64 starts unselected so you decide what goes in each file. Existing files are never overwritten. JSON includes this map's names, notes, coordinates and headings, without personal favorites, settings or local native-flag IDs. Names/notes are never silently shortened. Extended v2 packs need SpotPins 1.7.0+; ordinary short packs stay v1-compatible.
To import a friend's pack:
- Open Spot Packs > Folder guide to see the path for your installed copy.
- In Windows File Explorer, open your ReSkate folder, then
Mods\.reskate_plugin_data\BallJack-SpotPins\SpotPacks. Create the folders if needed, or export once to create them. Copy your friend's.jsonfile there. - Load the pack's map. Choose Spot Packs > Import pack, then Refresh after adding files. Only compatible packs for the current map appear; the list shows up to 64 matching packs.
- Select Load, review the spots, toggle any you do not want, and choose Add selected. Cancel leaves your list unchanged. Matching coordinates are skipped.
Imports add independent copies to your saved list. Removing the original JSON later does not remove imported spots. Exports are written to the same folder; send the JSON to a friend to share it. Different installation folder names have separate data folders, so follow the in-game Folder guide if your path differs. SpotPins does not open File Explorer for you.
Recovery
Use Spot Packs > Backup now for a local snapshot, or Recover missing spots to review one of five snapshots across all maps. Automatic snapshots are enabled before delete, position update and pack import; disable them in Settings > Advanced > Pins / Recovery. Recovery adds missing location copies to the current map, skips matching coordinates and leaves existing spots alone. It does not roll back a rename/note at an existing location; an old moved position may be added as another spot.
Snapshots live under Mods/.reskate_plugin_data/<installed-folder>/Recovery/snapshots.json. The in-game recovery Folder guide uses your actual installed identity. Each snapshot is limited to 64 KiB and the managed file to 512 KiB. A failed/oversized snapshot reports failure without blocking the ordinary edit; malformed existing recovery data is protected. The five slots rotate, so JSON export remains the portable backup. These files are never included in the release ZIP.
Session Spots and SpotPacks: multiplayer preview
Experimental: sharing has not yet been tested between two players in a live multiplayer session. Delivery or confirmation may fail. Both players need compatible SpotPins copies. Switch sharing off under Settings > Advanced if desired.
In a lobby, open Session, choose one saved spot from the current map and a player, then choose Send spot. Use Send map pack to review and send a selection from your current map instead (up to 64 spots / 64 KB). Lobby transfers retain the established 32-byte name / 120-byte note format; use a local v2 JSON export for longer metadata. Acknowledged chunks retry briefly when packets are lost. A delivery confirmation means the other copy received the offer, not that the player saved it.
Received offers show the sender and map. The player chooses Travel, Save or Dismiss; receiving never automatically teleports or saves. Travel and Save require the matching map. Save adds a copy without replacing existing spots. Unsaved offers are temporary and disappear when you leave the session or switch sharing off. Multiplayer travel remains subject to game and host rules.
Received packs appear under Session > Packs. Choose Review pack, select the spots you want, then Add selected. Import requires the matching map, skips duplicate coordinates and preserves your own spots and preferences. A completed transfer is an offer for review, not an import. Keep a JSON export if you want a portable backup. Unsaved packs disappear when you leave, reload the plugin or disable sharing. Two incoming transfers and four completed packs are accepted at a time; unfinished transfers expire after 90 seconds.
Both players need compatible versions and the same message-channel name from manifest.json. Our dev manifest is SpotPinsDev and the release manifest is SpotPins, so these copies are intentionally isolated. Folder names determine local storage; renaming a folder alone does not change a manifest-defined multiplayer channel. An unavailable or incompatible recipient produces a timeout, not an automatic fallback. Live multiplayer has not yet been verified.
Native-map flags
On the saved spots screen, choose Map Flags > Publish all, then confirm. This publishes one flag per saved spot on the current map, subject to normal object limits and overlapping destinations. Existing flags linked to those spots are updated instead of duplicated. The list's Search, Favorites and sorting do not narrow this batch. Close menus and release A so the serialized queue can run. Reopen Map Flags to see status, stop the batch or refresh its inspection.
Use a spot's More > Publish map flag to publish/update only that spot. More > Remove this flag removes only its verified linked flag. Map Flags > Remove all confirms removal of this copy's verified flags on the current map, including flags whose saved spots were deleted. These actions never delete saved spots or deliberately change unrelated park objects.
Native cards keep the game's generic labels. SpotPins cannot currently pass a spot name into an individual native card. Names remain visible in the SpotPins library, flag manager and shared packs. Other players' cards may use the owner's player name. Do not rename global game strings or your player to impersonate per-spot native names.
Flags are real QuickDrop park objects and may persist after closing SpotPins or disabling publishing. They follow the game's map-object limit (up to 1024 total) and host limits; a batch may stop before every spot is published. Existing unrelated flags and destinations already occupied by a flag are skipped. Objects moved, rotated, scaled or retyped outside SpotPins are protected and skipped. Missing tracking is retained to avoid losing ownership during asynchronous map restoration; a later explicit Publish can repair it after a replacement is confirmed. No background recreation occurs.
Publish all is an explicit refresh, not continuous synchronization. After saving, importing or updating spots, use Publish all again, or publish a single spot. Deleting a saved spot keeps its world flag until you explicitly remove it through Map Flags. Canceling a batch preserves completed work. If an accepted placement cannot be verified before cancel/reload/timeout, inspect Park Editor before publishing again.
The old one-flag tracking key is retained unchanged. New tracking uses a separate v2 key; per-spot identities are saved only after Publish confirmation and never included in JSON or Session packs. Failed identity saves prevent placement; failed tracking saves stop the batch while keeping removal control in memory. Keep the installation folder stable when updating.
The world.objects permission is for explicit flag actions, chat.commands registers the optional local command, and ui.models publishes the optional guide's six numeric widget values. No additional permission is introduced in 1.5.1.
Optional chat and compact guidance
Chat commands are typed locally in a multiplayer lobby and are not broadcast. Enable them in Settings > Advanced > Integrations. Use /spot menu, save <name>, go <exact spot name>, guide <exact spot name>, flag <exact spot name>, return, or packs. A name collision uses /spotpins instead; the settings show the active name. Duplicate names require the menu. Flag still asks for confirmation. Turning commands off blocks their handlers; the autocomplete entry may remain until plugin reload.
The optional Compact guide HUD shows bearing and distance only while Guide me is active. Stop Guide clears it. Its Studio-native frontend is not included in this build; NATIVE-UI-BINDINGS.md documents the numeric contract and remaining asset work.
Scout Mode
Open Scout beside Map Flags and Save, choose an aim range and select Start Scout. Release A and close menus. Scout takes its own skater hold, native freecam and controller-flight requests; a busy camera, host refusal or pending SpotPins teleport can prevent entry.
| Action | Keyboard | Controller |
|---|---|---|
| Fly / look | ReSkate freecam movement and mouse | Left/right sticks |
| Rise / descend | Q / E | LB / RB |
| Name and save the checked destination | Enter | RT |
| Lock/unlock target | F | LT |
| Turn arrival direction in 15-degree steps | [ / ] | D-pad Left / Right |
| Match arrival to camera heading | G | Y |
| End scouting | Escape | B |
Saving opens a normal text-entry dialog and keeps a frozen target/map snapshot. Save adds a normal independent spot; Cancel leaves the list alone. No travel occurs. Duplicate coordinates are skipped, failed writes preserve the previous list, and holding a save button cannot repeatedly add spots. Exit waits briefly for controls to release, then returns to Scout setup. Focus loss, map changes and unload release this copy's requests.
The preview is a limited supporting-surface/headroom check, not a full collision-free arrival guarantee. No-hit, unavailable collision, uneven support, blocked headroom and a floor that moved during naming all prevent saving. Visible scenery far from your skater may have no loaded collision. Scout does not move your skater to force it to load. Range is measured from the camera; a larger range does not solve missing collision.
Scout is dormant when off: it performs no idle camera, input or ray polling. While flying it samples at 10 Hz (normally five probes/sample); save rechecks are explicit. Use ReSkate's own Freecam settings for movement speed. Full controller/keyboard behavior still needs an in-game test on your setup.
Advanced travel
On Board: On explicitly requests board arrival; Off requests arrival on foot. The game or session may still determine the final state.
Enter coords starts with your current X, Y, Z. Y is height. Floor off preserves the entered height, including sky drops. Floor on checks below the target and uses a detected surface; if none is detected, travel is canceled. Distant collision may not be loaded, and neither mode guarantees an obstacle-free destination. Review and confirm before traveling. Return is available after an accepted request.
Long-distance travel may need a moment for scenery and collision to stream in.
Updating and your saved spots
Spots and settings are local and stored by ReSkate separately from the mod package. Keep the package name and installation folder unchanged when updating. A renamed or separate copy has its own storage. This package contains no player save/settings file to replace yours.
Spot lists are separated by map. Unreadable saved records are preserved rather than overwritten, and failed saves keep the previous data. ReSkate may ask you to approve permissions again after an update.
