Completion safety
Gothic 1 Remake Save Checkpoints Guide
Use named manual saves before camp joins, LP spending, story pushes, Gomez outcomes, Sleeper Temple entry, and challenge attempts.
Quick answer
Do not save constantly. Save before choices that change routes, spend resources, or restrict cleanup.
The safest pattern is simple: name the save by the risk it protects, keep it until the achievement or route check is handled, then delete only when a newer save covers the same purpose.
Branch saves
Use these before faction joins, named outcomes, and story gates that may change what you can clean up later.
Hold saves
Use these before LP, ore, lockpick, crafting, magic, or language spending that could strain your build.
Challenge saves
Keep no-sleep and permadeath attempts away from relaxed cleanup saves.
Save slot system
The save names worth keeping
Use short names that describe the decision, not the location. You should know exactly why a file exists when you return to it hours later.
| Save name | Make it before | Protects | Keep until | Next guide |
|---|---|---|---|---|
| Pre-Camp Branch | Joining Old Camp, New Camp, or Swamp Camp | Gomez' Paperboy, Lowlife, Cult Loon, and faction route testing. | All camp join checks are done or you no longer need branch access. | Factions |
| LP Hold | Large training, guild-rank, magic, Orcish, or mastery spending | Overachiever, weapon mastery, magic circles, language, and thief utility. | Your build still works after the spend and the achievement state is clear. | LP Planner |
| Story Push | Chapter movement or a major quest hand-in | Books, maps, transformations, camp business, and open quest cleanup. | The next chapter starts cleanly and your open lists are updated. | Missables |
| Gomez Outcome | Resolving Gomez-related choices | Mercy Over Madness and the story state you prefer afterward. | The outcome branch is handled and you know which file continues. | Story Choices |
| Temple Hold | Entering the Sleeper Temple or final late-story route | The Sleeper is with you, late cleanup, maps, books, magic, and story choices. | Your final-route checklist is clear. | Achievements |
| Challenge Start | No-sleep or permadeath attempts | Insomnia Champion and No time to die without risking relaxed cleanup. | The challenge attempt succeeds or you restart the attempt. | Challenge Runs |
Checkpoint timeline
When to add, keep, and retire saves
This is the practical route order. It keeps you from creating dozens of files while still protecting the decisions that matter.
-
01
Early route: one clean manual save
Use it before your run has a faction identity. Do not rely on a rolling autosave for long-term routing.
-
02
Faction route: split from Pre-Camp Branch
Join each camp on a copied branch, check the join achievement, then return or continue from the route you prefer.
-
03
Build route: save before LP spending
Use this before weapons, magic, Orcish, thief tools, crafting, or broad lesson cleanup.
-
04
Story route: save before chapter pressure
Review maps, books, transformations, open quests, and story choices before pushing deeper.
-
05
Final route: keep Temple Hold
Use a late-route save before Sleeper Temple entry and final cleanup pressure.
-
06
Challenge route: start a separate file
No-sleep and permadeath attempts are cleaner when they are not mixed with relaxed completion cleanup.
Decision matrix
Should you save, overwrite, or start a separate file?
| You are about to... | Risk level | Use this action | Why |
|---|---|---|---|
| Join a camp | High | New branch from Pre-Camp Branch | Old Camp, New Camp, and Swamp Camp have separate join checks. |
| Spend a large LP block | Medium to high | Create LP Hold | Training can strain weapon mastery, magic, Orcish, and lesson cleanup. |
| Resolve a named story outcome | High | Create a dedicated outcome save | You may prefer one outcome for the main route and another for a branch check. |
| Push a chapter or final area | Medium to high | Create Story Push or Temple Hold | Late cleanup is cheaper before the route narrows. |
| Batch locks, pickpockets, crafting, or maps | Medium | Create a short-term cleanup hold | Count goals are easier when you can roll back mistakes. |
| Attempt no-sleep or permadeath | Very high | Start a separate challenge file | Challenge routing should not damage relaxed achievement cleanup. |
Save checklist
Check before you commit
Recovery flow
What to do when a save is already messy
A bad save trail is annoying, not always fatal. Work from the least destructive option first.
Check the achievement list
Before reloading, check whether the goal is already reflected on your platform list.
Look for the newest safe hold
Use the most recent file that still protects the decision, not the oldest file by habit.
Create a repair save
If you must continue from a messy file, name the next save clearly before attempting cleanup.
Split challenge attempts
If no-sleep or permadeath goes wrong, restart that challenge file instead of damaging the main route.
Challenge file policy
Keep strict runs away from relaxed cleanup
| Challenge | Save file | Do not mix with | Safe rule |
|---|---|---|---|
| Insomnia Champion | Challenge Start - No Sleep | Relaxed exploration, crafting, map, book, or faction cleanup. | Treat every rest decision as route-critical. |
| No time to die | Challenge Start - Permadeath | Risky combat experiments or blind late-game pushes. | Keep this attempt separate from the completion save trail. |
| Colonyholic | Main completion file plus branches | Untracked experiments that blur what remains. | Compare with your platform achievement list before deleting branches. |
Common mistakes
Save habits that cost hours later
Using one rolling manual save
A single file feels clean until it silently overwrites your only faction or story branch.
Deleting Pre-Camp Branch too early
Keep it until Old Camp, New Camp, and Swamp Camp join checks are handled.
Training without LP Hold
A build can feel fine now and still starve magic, Orcish, mastery, or utility later.
Pushing chapters with open cleanup
Check maps, books, transformations, quests, and open achievements before major story movement.
Mixing challenge and cleanup files
Strict runs reward discipline; relaxed cleanup rewards patience. They ask for different save trails.
Trusting memory for branch status
Before deleting a file, check the achievement list and the related route page.
Version notes
Use your platform list as the final branch check
Achievement names, hidden descriptions, and platform display can differ. Before deleting a branch save, compare your current save state with the achievement list shown on the platform you are playing.
FAQ
Save questions
How many permanent saves do I need?
Most routes can stay manageable with Pre-Camp Branch, LP Hold, Story Push, Temple Hold, and separate challenge files.
Do I need separate saves for all three camps?
Use one clean Pre-Camp Branch, then copy from it to check Old Camp, New Camp, and Swamp Camp routes.
When can I overwrite a branch?
Overwrite only after the achievement or route check it protects is handled and another save covers the route you want to continue.
Where should my late-game save be?
Keep a Temple Hold before Sleeper Temple entry or final late-story pressure so you can finish cleanup first.
Can I combine challenge runs with cleanup?
It is safer not to. Keep no-sleep and permadeath attempts on dedicated files.