Garrett route
Gothic 1 Remake Pickpocketing Guide
Track 20 successful pickpockets for Garrett while keeping important NPCs, saves, and route consequences under control.
How cleanup works
Garrett is a count goal, but the risk comes from who you test it on.
Count success only
Mark a slot only after the pickpocket succeeds and you keep that save. Attempts you reload away should not stay in the tracker.
Pick targets by route cost
A lower-risk target is easier to recover from than a trainer, trader, quest lead, or faction-sensitive character.
Stop when the goal is done
After the 20-success check is clear, extra theft belongs on a separate save unless you need the loot for your route.
Before you start
Prepare the cluster before you touch anyone's pockets.
Target risk matrix
Pick targets by the cost of a bad outcome.
| Target type | Try now? | Risk | Safer action |
|---|---|---|---|
| Low-pressure camp targets | Good first picks | Usually lower route cost if the attempt is not worth keeping. | Use these to build the early count after a pre-cluster save. |
| Traders and trainers | Delay or save first | A bad outcome can interrupt services you may still need. | Try only from a rollback save and keep the clean version until the route is stable. |
| Quest leads and faction-sensitive NPCs | Avoid early | The cost of a mistake is harder to judge without route context. | Use safer targets first; come back only if you still need the count. |
| Targets after a long unsaved route | No | A single bad attempt can make you choose between progress and cleanup. | Save first, then try the pickpocketing cluster. |
| Extra targets after 20 successes | Only for loot | The achievement reason is gone, so only the theft risk remains. | Branch the save if you want to keep testing pockets. |
20-pickpocket tracker
Record each successful pickpocket for Garrett.
Use the note field for a target, area, or camp reminder. The goal is to rebuild the count later, not to write a perfect NPC catalog.
| Pickpocket | Success? | Target or area note | Checkpoint |
|---|---|---|---|
| Pickpocket 1 | Start cluster save | ||
| Pickpocket 2 | Low-risk target | ||
| Pickpocket 3 | Update after success | ||
| Pickpocket 4 | Do not count attempts | ||
| Pickpocket 5 | Five-success save | ||
| Pickpocket 6 | Check current prompts | ||
| Pickpocket 7 | Keep notes short | ||
| Pickpocket 8 | Save before risky target | ||
| Pickpocket 9 | Avoid quest pressure | ||
| Pickpocket 10 | Halfway save | ||
| Pickpocket 11 | Second cluster save | ||
| Pickpocket 12 | Keep rollback save | ||
| Pickpocket 13 | Important NPC caution | ||
| Pickpocket 14 | Do not rush count | ||
| Pickpocket 15 | Fifteen-success save | ||
| Pickpocket 16 | Use safe remaining targets | ||
| Pickpocket 17 | Avoid late route pressure | ||
| Pickpocket 18 | Check count carefully | ||
| Pickpocket 19 | Save before final target | ||
| Pickpocket 20 | Check achievement state |
Save checkpoints
Name saves for the pickpocketing mistake they prevent.
| Moment | Save name idea | Protects you from |
|---|---|---|
| Before a camp cluster | pickpocket-cluster-base | Losing route progress because several attempts are mixed together. |
| Before an important NPC | before-risky-pocket | Keeping a clean rollback if the result is not worth carrying forward. |
| After five or ten successes | garrett-five / garrett-ten | Rebuilding the count when the second half gets messy. |
| Before the final batch | garrett-final-pockets | Finishing the 20-success goal without a fallback. |
| After Garrett is done | garrett-complete | Separating achievement cleanup from optional extra theft. |
Troubleshooting
Fix the route state before adding more attempts.
An attempt hurts your route
Reload the pre-cluster save, choose lower-risk targets, or leave that NPC for a separate branch.
The tracker does not match your save
Check whether you counted a result that was reloaded away, then rebuild from the last named checkpoint.
A target has no useful pickpocket option
Do not force the route on that target. Move to another low-risk option or revisit after more route progress.
Garrett still looks incomplete
Confirm you have 20 successes in the save you kept, not 20 attempts across several reloaded files.
Common mistakes
Most pickpocketing problems come from counting too loosely.
Counting attempts as successes
The tracker is for successful pickpockets only. Cancelled, failed, or reloaded attempts should not stay checked.
Starting with important NPCs
Use lower-risk targets for the early count, then decide whether important characters are worth touching.
Overwriting the clean save
Keep the pre-cluster save until the results, count, and route state all look worth keeping.
Spreading the count across sessions
If you stop mid-route, write down the last safe count and keep a checkpoint save with the same number.
Continuing after the goal is complete
Extra theft can be useful for loot, but it no longer belongs to the Garrett cleanup route.
Ignoring current game text
If the prompt, requirement, or achievement wording differs in your save, follow the current game text first.
Version note
Use your current achievement list and pickpocket prompts as the final check.
Pickpocket availability, requirements, and achievement wording can vary by build or save state. If your game shows different wording, keep the manual save and follow the current in-game text before committing the result.
FAQ
Pickpocketing questions
What unlocks Garrett?
Use this page to track 20 successful pickpockets toward Garrett. Count only successes that remain in your current save.
Do failed pickpocket attempts count?
No. Mark only successful pickpockets, not failed attempts, cancelled attempts, or results you reloaded away.
Should I pickpocket important NPCs first?
No. Start with lower-risk targets and use a rollback save before important NPCs or route-sensitive characters.
What should I do if a pickpocket attempt goes badly?
Reload the pre-cluster save if the result damages your route, then choose safer targets or leave that NPC for later.
Do the tracker fields save after reload?
No. The checkboxes and note fields are lightweight on-page helpers and reset when the page is reloaded.