The All You Need Save Manager Continued
Continued PEAK save manager with synchronized luggage, player revival, owner-confirmed teleport and inventory restoration. Every player in the room needs the same version. Keeps existing saves and settings.
| Date uploaded | 3 weeks ago |
| Version | 1.2.2 |
| Download link | LeonYew-The_All_You_Need_Save_Manager_Continued-1.2.2.zip |
| Downloads | 33 |
| Dependency string | LeonYew-The_All_You_Need_Save_Manager_Continued-1.2.2 |
This mod requires the following mods to function
BepInEx-BepInExPack_PEAK
BepInEx pack for PEAK. Preconfigured and ready to use.
Preferred version: 5.4.2403README
The All You Need Save Manager Continued
![]()
All-in-one save manager for PEAK. Save a run, load it later, and restore the run setup, players, inventory, and world state as closely as the game allows.
An independent community continuation of llucasandersen's The All You Need Save Manager, maintained by LeonYew / LeonYew-Ley. Original source and attribution are retained in NOTICE.md.
Continued 1.2.2
- Fix luggage that looks closed but cannot be opened after loading. Restore appearance, interaction state and attached objects together on every client.
- Restore closed boxes in multiplayer, cancel delayed openings and clear stale loot history. Restoring an open box never creates more loot.
- Match same-path boxes by type, name and nearby position. Missing or ambiguous boxes report a load failure instead of changing another box.
- Confirm restoration on all current clients and send fresh live state to late joiners. Keep the saved-map, player, inventory and format 6 compatibility fixes.
Every player in the room must install 1.2.2 and restart PEAK. Automated managed and game API checks pass; actual Unity/Photon multiplayer testing remains pending.
What It Syncs
Run setup
- Scene name (
Level_X) - Level id and segment
- Seed and ascent
- Run day, run timer, and time of day
Player state
- Position and rotation
- Saved death, unconsciousness and petrification state
- Player motion is cleared on load; saved velocity fields remain compatible with old saves
- Stamina and extra stamina
- Status effects
- Checkpoint ownership links
Inventory
- Main slots
- Backpack slots
- Temp slot
- Equipped and selected slot
- Held item id when available
- Item uses and item data entries
World and interactables
- Campfire state and progress
- Luggage and cursed luggage state
- Respawn chest and mirage luggage state
- Ground items with transform and rigidbody data
Deployables and world objects
- Piton and piton handle
- Rope anchor, rope, rope anchor with rope, rope anchor projectile
- Chain launcher
- Magic bean vine
- Cloud fungus
- Bounce fungus
- Shelf fungus
- Portable stove
- Checkpoint flag and checkpoint constructable
- Scout cannon
How To Use
- Open the pause menu and click
SAVE MANAGER. - Click
Quick Save, or enter a save name and clickSave. - In the save list, click
Loadon the save you want. - Use
Overwriteto replace an existing save with your current run state.
Autosave
Autosave can be disabled in the BepInEx config file.
- Config file:
BepInEx/config/com.lucasandersen.peakallyouneedsavemanager.cfg - Section:
AutoSave - Setting:
Enable AutoSave = false - Timer setting:
Interval Seconds = 300
If the config file does not exist yet, launch the game once with the mod installed and BepInEx will generate it.
Loading Notes
-
Explicit saved scenes are loaded from their own map bundle; a missing scene never falls back to the daily map or the active run.
-
New saves also record the live biome. Loading checks this value, or the unambiguous volcano code in legacy volcano saves, before restoring players/world objects. A game update may change a same-named map; old geometry cannot be reconstructed from player snapshots.
-
You can load from Airport.
-
You can load while already in a run. Luggage is matched within 20 game units using type, prefab name and position; a missing or ambiguous match stops loading with an error. A game update can change the saved map geometry.
-
In multiplayer, the host controls save and load.
-
Multiplayer loads now restore every saved player that matches, even if the full saved party is not present yet.
-
Every player in the room must install the same build, including unmatched scouts. Loading checks client support before restoring world objects and waits for luggage acknowledgements; timeouts and disconnects report a failure.
-
Teleport completion and native held-item attachment are checked on the character's owner before reporting success. Timeouts and disconnects report a load failure.
-
Players resume at rest at the saved position and view. Airborne or climbing saves still need physical support to stand; loading does not move players to a guessed ground position.
-
Living saved scouts use the game's network revival without extra revival penalties before inventory is restored.
-
Player names must be unique and match the save. Missing, renamed, ambiguous or uninitialized players are skipped and reported as a partial load.
Save Files
- Folder:
<PEAK root>/PeakSaves - Extension:
.peaksave.json - Versioned format with compatibility checks for safe loading
- If the game install folder is not writable, TAYNSM falls back to a writable save folder automatically
Installation
- Disable or uninstall the original The All You Need Save Manager before installing this continuation.
- Install this package and BepInEx through your mod manager.
- Fully restart PEAK.
For manual installation, extract so this path exists:
BepInEx/plugins/PeakSaveManagerContinued/PeakSaveManagerContinued.dll
The original plugin GUID and configuration filename are retained. Load an existing complete save and save to a new name when checking the update. Items already missing from a saved file cannot be reconstructed by this fix.
Source And Contributing
The GitHub repo now includes the source project and the verification tool.
- Source project:
src/PeakSaveManager - Verification tools:
tools/SaveVerificationTests,tools/Verify-ItemUsageData.ps1,tools/Verify-Compatibility.ps1,tools/Verify-PlayerRestoration.ps1 - Issues: https://github.com/LeonYew-Ley/PeakSaveManagerContinued/issues
- Pull requests: https://github.com/LeonYew-Ley/PeakSaveManagerContinued/pulls
- Contribution guide: CONTRIBUTING.md
Build command:
./Build.ps1 -GameManagedPath '<PEAK>/PEAK_Data/Managed' -BepInExCorePath '<profile>/BepInEx/core'
This builds build/PeakSaveManagerContinued.dll and runs the managed verification checks. Requires PowerShell 7, a .NET SDK with .NET 9 runtime support, and local PEAK/BepInEx assemblies. Third-party assemblies are not included.
Package the mod and a separate source archive:
./scripts/package.ps1
Changelog
1.2.0
- Combined player revival, teleport completion and held-item restoration fixes.
- Requires the same version on the host and restored teammates.
- Reports ambiguous player matches, partial loads, timeouts and disconnects.
1.1.0
- Community continuation with backpack and item data restoration repairs.
- Added 36 managed item-restore regression cases and game assembly compatibility checks.
Older release notes are in CHANGELOG.md.
Known Bugs
- Shelf fungus can fail to restore in some saves.
- Bounce fungus can fail to restore in some saves.
Validation
Release compilation, saved-map and warp-lock regressions, 36 item-restore cases, 27 player-load workflow cases, 512 life-state combinations, 32 combined life/warp scenarios and save serialization checks pass against installed PEAK 3.0 assemblies. Luggage checks cover simulated host/client state transitions, delayed openings, repeated loads, reopening, same-path identity ambiguity, message ordering, host/scene changes and old/new save fields. Compatibility verification checks native game references, luggage/list/history APIs, the join hook, animator restoration and compiled coordinator integration. These checks do not launch Unity or Photon; real animation and multiplayer acceptance remain pending.
Links
CHANGELOG
1.2.5 - Shared map preparation
- Fix old-map multiplayer loads where the host prepared its resource bundle but Photon asked teammates to switch before that bundle was loaded on their machines.
- Check client support, preload the exact saved map on all current participants, and acknowledge the saved seed/ascent before starting the native networked scene load. Require destination-scene and initialized-character readiness from every participant before restoring world/player state.
- Abort on preparation errors, missing acknowledgements, timeouts, party membership changes or host migration. Cancel pending preparation, restore uncommitted ascent changes and clear seed overrides; isolate replies and native-process failures between attempts.
- Guard nested native scene processes against cancellation before their LoadLevel call. Remove local-only scene fallback in online rooms. An already-started native switch cannot be rolled back automatically.
- Use protocol 6 and version 1.2.5 on every peer. Keep existing format 6 saves and configuration. Fix the startup log to identify the actual continued version.
- Add behavior regressions for all-peer barriers, stale/duplicate replies, phase/retry isolation, errors, party changes, solo rooms and native-process cancellation/disposal; verify compiled gate ordering and game APIs. The user confirmed two-player Unity/Photon acceptance passed on the tested build and authorized release. Managed failure-path tests do not establish that every failure scenario was exercised in game.
1.2.4 — Stable landings for unsupported saved positions
- Keep safe grounded save positions; when current geometry no longer supports them, search for static, walkable ground within 8m horizontally, 8m vertically and 10m total. Check nine support points and body clearance, excluding steep slopes, conditional/bounce/damaging surfaces and trigger volumes. Fail explicitly if no safe nearby landing exists.
- Report each relocated player's offset in the load result and log, without rewriting the save. Leave airborne, climbing, dead and unconscious snapshots on their original restoration path.
- Require a continuously grounded, low-speed interval after owner teleport and equipment restoration before confirming success. Use player-owner protocol 5 so all room participants need 1.2.4.
- Share one 5-second luggage-readiness budget across the three restoration passes, instead of waiting up to 5 seconds per pass.
- Managed/API regressions pass; actual Unity/Photon gameplay has not been independently verified.
1.2.3 — Continue player restoration when historical luggage is missing
- Fix the 1.2.2 regression where a missing or ambiguous saved luggage object aborted loading after switching segments, leaving scouts at the segment entrance before their saved positions and inventories were restored.
- Wait for luggage objects to become ready, then skip unmatched objects and continue restoring every safe match and the saved players. Keep the type, name, distance and ambiguity checks; do not guess a distant replacement.
- Report skipped luggage in the log and show a yellow partial-load result instead of claiming complete world restoration. Clear and deduplicate warnings for each load.
- Retain synchronized luggage state, late-join handling, player-owner confirmation and format 6 compatibility. Every room participant should update to 1.2.3 and restart PEAK.
- Add regressions for missing first/all boxes, ambiguous matches, unavailable network views, offline matching and duplicate saved identities. Managed/IL checks do not replace in-game testing.
1.2.2 — Luggage restoration and multiplayer synchronization
- Restore luggage appearance, interaction state and the native available-luggage list together on the host and all current clients. Fix closed-looking boxes that could not be opened after loading.
- Restore closed snapshots in multiplayer, cancel pending native opening routines and reset stale loot history so the box can be opened normally again. Loading an open box never regenerates loot.
- Synchronize attached objects and respawn-chest skeleton state. Late joiners receive the current live state, with older pending messages prevented from overriding newer loads.
- Match same-path boxes by prefab type, name and nearby position. Missing or ambiguous boxes report a load failure instead of applying state to an arbitrary distant box.
- Require every player in the room to use 1.2.2, check support before restoring world objects and wait for client acknowledgements. World restoration errors now reach the load failure handler.
- Keep format 6 saves compatible; new saves retain attached-object activation explicitly. Add luggage behavior, identity, message-order and game API checks. Unity/Photon gameplay remains unverified.
1.2.1 — Saved maps and PEAK 3.0 compatibility
- Preload the resource bundle for the saved scene before checking scene availability. Explicit saved map names/numbers never fall back to a remapped daily index or the current scene.
- Report missing, failed or timed-out map resources instead of silently choosing another map.
- Capture the live saved biome and check it before restoring players/world state; legacy volcano codes also reject a volcano-to-temple mismatch. Same-named maps can still change between game versions.
- Support the PEAK 3.0 teleport status-lock property while retaining the previous private field fallback.
- Require the updated player-owner protocol so old clients cannot acknowledge this build's restoration requests.
- Add map-loading and native-lock regressions. Managed/IL verification does not replace in-game host/client testing.
- User confirmed that loading an existing volcano save enters the volcano again. Full multiplayer restoration remains unverified.
1.2.0 — Player load restoration
- Restore held items once through the character owner's native equip flow, including empty hands and legacy slot fallbacks, without assigning item templates to runtime state.
- Wait for owner-confirmed teleport completion and item attachment; report timeouts, missing owner support and disconnects as failures.
- Resume at rest with full-body motion cleared, keeping saved positions, view, inventory and existing save format.
- Restore saved living scouts through native network revival before inventory, without extra revival penalties; preserve saved dead/unconscious states.
- Match unique saved player names, wait for initialized characters and report skipped players as partial loads.
- Finalize saved life state, stamina and collision on the player's owner after teleport completion; keep dead saved scouts from regaining body collision during the native warp.
- Require the host and every restored teammate to install the same version; the host still controls loading.
- Add managed selection, ordering and failure regressions. Unity/Photon gameplay validation remains pending.
1.1.0 — Continued
- Fixed worn backpacks disappearing during inventory synchronization after loading a save.
- Report player restore failures instead of continuing to a successful load message.
- Restore ItemUses with the optional integer type expected by PEAK, preserving generic entries and unlimited-use state for inventory and ground items.
- Normalize wrongly typed integer use counts saved after an older restore.
- Preserve the original plugin GUID, configuration and save format for migration.
- Add managed restore regression checks and game assembly compatibility verification.
- Publish the community continuation under LeonYew, with original author attribution.
1.0.9
- Fixed saving on current PEAK builds after the run timer field became private.
- Updated backpack capture and restore for the current game API, including backpack type.
- Fixed the plugin's embedded version number to match the release version.
1.0.8
- Fixed multiplayer save loads stopping early when the full saved party was not matched before restore.
- Multiplayer loads now wait briefly for joiners, then continue with every matching player instead of cancelling the whole load.
- Added the source project and verification tool to the GitHub repo so contributors can build and submit fixes more easily.
1.0.7
- Fixed multiplayer load continuing with only the host matched instead of waiting for the full saved party.
- Improved multiplayer player matching during load from Airport into a saved run.
- Added clearer load failure messaging when saved players are missing or not ready yet.
1.0.6
- Fixed duplicate item data key restore failures during load, including the reported
CookedAmountcrash. - Prevented ground item restore errors from blocking the player position restore that happens later in the load flow.
- Improved reliability when loading host saves back from Airport into multiplayer runs.
1.0.5
- Fixed a load pipeline failure that could stop restore early during scout or other world object restore work.
- Prevented scout cannon restore mismatches from aborting the rest of the load.
- Improved load failure logging and UI error reporting.
- Added scout coverage to save verification tests.
1.0.4
- Fixed save creation failing on some installs when the game root save folder was not writable.
- Added automatic fallback to a writable save folder.
- Improved save failure messages so the UI shows the actual reason when possible.
1.0.3
- Added GitHub project link in
manifest.json. - Refreshed README content and added icon preview.
- Cleaned package metadata for release page quality.
1.0.2
- Packaged release as TAYNSM.dll.
- Clean Thunderstore export layout.
- Documented known bug for Shelf Fungus and Bounce Fungus restore behavior.