Guildrun Save and Resume

How Mid-Run Saving Works

Saving captures your entire run state: current map position, gold, roster heroes with specializations and items, owned relics, active difficulty modifiers, and encounter history. Open the pause menu during any non-combat phase — map screen, shop, or relic draft — and select Save Run. You cannot save during active combat resolution; wait until the fight ends and rewards appear.

Each manual save overwrites the previous mid-run checkpoint for that attempt. There is typically one active saved run per profile slot. Starting a new run while a save exists prompts you to abandon the old run or resume it. Abandoning is irreversible, so confirm before clicking New Run if you intend to continue a saved session.

Resuming a Saved Run

From the main menu, select Continue or Resume Run if a save exists. The game loads your checkpoint at the last safe non-combat state — usually the map node where you saved, not mid-fight. Verify your relic inventory and gold total match expectations before choosing the next encounter.

If Continue is grayed out, check that you are logged into the same Steam account and that cloud sync completed. Offline launches may miss cloud saves synced from another device. After resuming, gameplay proceeds normally including access to shops, pivots, and endless mode if already unlocked.

Steam Cloud Sync

Steam Cloud can synchronize save data between PCs linked to the same account. Enable Steam Cloud for Guildrun in the game properties panel on Steam. After saving mid-run, allow Steam to finish syncing before shutting down — the cloud icon in Steam stops animating when complete. Launching on a second machine pulls the latest cloud save on first menu load.

Cloud conflicts occur if you save different runs on two devices without syncing. Steam prompts you to choose which save to keep. Pick the timestamp that matches your intended progress. Mac and Windows saves may sync cross-platform within the same Steam account, but verify system requirements on both machines before relying on cross-platform resume.

What Saves Do and Do Not Include

Mid-run saves include everything inside the current attempt: heroes, items, relics, map progress, and active modifiers. They do not include meta-unlocks such as difficulty tier progression or hero collection unlocks unless those were earned before the save point and stored separately in profile data — which persists automatically regardless of mid-run saves.

Leaderboard submissions for endless mode typically require a completed uninterrupted segment from a checkpoint defined by the game rules. Saving mid-endless-run may affect eligibility depending on active season rules. Check in-game leaderboard tooltips for the current demo policy.

• Saved: roster, items, relics, gold, map node, active modifiers.
• Saved: difficulty tier selection for the current attempt.
• Persistent separately: account unlocks and difficulty progression.
• Not saved across runs: relic and item inventories after run ends.
• Varies: endless leaderboard eligibility after mid-run save.

Save Strategies for Learning

Experienced players save before difficult boss nodes to replay decisions without restarting from difficulty one. This is especially useful when testing relic combinations documented on the best relics page or practicing pivots from the pivot mid-run guide. Save before a relic shrine when you want to compare two draft paths — note that abuse policies for leaderboard runs may restrict reload practices.

New players should still finish runs without reload scumming to learn loss states. Saving for real-life interruptions is the intended use case. Combine saves with the difficulty tracker to log progress across sessions without relying on memory alone.