Patch notes guide
Gothic 1 Remake Patch Notes: What Changes in 1.0.4
These Gothic 1 Remake patch notes separate the verified 1.0.4 changes from assumptions about lockpicking, chest rewards, and fixed sequences.
Quick answer: 1.0.4 changes feedback and reward context, not a published universal lock code
The official changelog checked for these Gothic 1 Remake patch notes identifies version 1.0.4 as CL 171261. The clearest lock-related change is a new voice distinction between not having a key and not having a lockpick. The same notes describe moved rewards, including changes around the mages area and the Old Mine.
The changelog does not publish a new rule for the linked lock plates or a fixed chest sequence. That means a Gothic Remake lockpicking route still has to match the visible plate state in your save. A patch note can explain why a reward or message looks different; it cannot replace a live observation when the lock itself disagrees.
Use the page as a change-impact checklist: confirm the build in Settings, identify the chest and room, record the current plates, and test one controlled movement. If the first checkpoint differs from an older guide, stop and calculate the current mechanism in the Gothic Lockpick Solver instead of forcing an old answer.
The version and changelog facts below are source-checked as of August 8, 2026. Recheck the official announcement after a later update; this page is an independent fan guide, not an official publication by Alkimia Interactive or THQ Nordic.
Open the chest solverWhat the Gothic 1 Remake patch notes verify for version 1.0.4
Treat the official note as a changelog, not as a complete walkthrough. The checked release identifier is version 1.0.4 with CL 171261. The official Steam announcement points readers to the G1R_Patch_1.0.4.txt changelog, while the official game site and Steam store page provide the surrounding game and publisher context.
The practical result is a short list of facts that can be separated from player inference. The voice line now communicates two different resource problems more clearly. Several rewards have moved, so a chest guide that names only a room or a reward may need a fresh identity check. The notes do not claim that every old lock state was regenerated or that all community routes became invalid.
Patch notes are most useful when they answer what changed between builds. They are not proof that a particular chest has one permanent combination. Keep the exact version beside any saved route, because a route is a calculation from a starting state and a relationship matrix, not a universal password.
| Verified note | What it changes for players | What it does not prove |
|---|---|---|
| Version 1.0.4 / CL 171261 | Record the build before comparing a guide or save | That every older chest state was replaced |
| New key-versus-lockpick voice distinction | Read the message as a resource hint before retrying | A new plate movement rule |
| Rewards moved in named areas | Recheck chest identity, room, and reward context | That a nearby lock has a new fixed code |
| Official changelog linked from Steam | Use the primary note for future update checks | That community routes are official data |
Did patch 1.0.4 change Gothic Remake lockpicking?
The cautious answer is: it changed lock-related feedback that helps you understand which resource is missing, but the checked changelog does not describe a new linked-plate algorithm. Do not turn a clearer voice line into a claim that every lock now uses a different pattern. The distinction matters because a failed attempt can be caused by a missing key, a missing lockpick, an incorrect chest assumption, or an observed plate state that no longer matches a saved route.
A live lock is still the strongest evidence for the next input. Count the plates, record each current hole using the site's back-to-front convention, and keep the direction convention consistent. Test only one legal A or D movement when mapping an uncertain relationship. Compare every plate after the movement, not only the plate you selected.
If an old solution fails immediately after the update, the failure is evidence that your starting state or source context differs. It is not evidence that you should repeat the same sequence faster. Reload when possible, write down the first mismatch, and calculate again from the state currently visible in the game.
| Observed situation | Best interpretation | Next safe action |
|---|---|---|
| The voice says a key is missing | This is a resource or access problem | Check the quest, door, or key context before picking |
| The voice says a lockpick is missing | The chest may be reachable but cannot be picked yet | Get or preserve lockpicks before testing a route |
| The first plate response differs | The copied source does not match this live state | Stop, record the current vector, and use the solver |
| The response matches but a later state differs | A row, direction, or input count may be wrong | Reload or remap the first divergent relationship |
What the patch note does not let you assume
It does not let you assume a fixed left-right code works for every chest, save, skill tier, or later build. It does not show that a named chest page and a nearby chest page describe the same container. It also does not make a community video an official source. Keep facts, tested observations, and guesses in separate notes.
The solver is useful here because it exposes its inputs. If the route is wrong, you can inspect the plate count, start positions, and Same, Opposite, or None relationships rather than treating a failed string as a mystery. This is a planning model for the live state, not a replacement for reading the screen.
Chest rewards, the mages area, and the Old Mine after the update
The reward changes deserve their own check because a player may reach the correct room and still conclude that the guide is wrong when the expected item is no longer in the same container. The official notes mention moved rewards in named areas, including the mages area and the Old Mine. That is a content-location fact, not a promise that every chest in those areas has the same lock.
When a reward is missing, verify the area name, room landmarks, chest appearance, quest state, and whether the container has already been opened. A reward move can change what you use to identify a chest. It does not justify copying a combination from the nearest chest with a similar model. Record the container first, then inspect the lock.
For Old Mine searches, keep route, access, chest identity, and lock solving as four separate jobs. The Old Mine guide can help with context, while the chest solver handles a visible mechanism. If a reward note and a lock route disagree, preserve the source date and build number and trust the live state for the next movement.
| Check after 1.0.4 | Record this | Link to use |
|---|---|---|
| Mages area reward | Room, landmark, chest identity, and actual reward | Chest locations guide |
| Old Mine reward | Mine route, access gate, container, and build | Old Mine chests guide |
| Named chest route | Plate count and first movement, not just item name | Live chest solver |
| Missing expected item | Whether the chest was opened or the quest advanced | Official patch note, then a fresh save check |
Why reward movement and lock movement are different facts
A reward table answers where an item is expected. A lock route answers how a particular mechanism reaches its center from a particular starting vector. One can change without the other. This distinction prevents a patch note about loot from becoming an unsupported claim about plate behavior.
Use a reward page for discovery and a lockpicking page for experiments. If you are already looking at the lock, the most useful evidence is the visible plate state plus one controlled response. If you are still looking for the chest, start with the area and route clues instead of spending lockpicks on an unidentified container.
A reliable post-patch workflow for lockpicking and chest guides
Use this order whenever a saved combination or chest guide was written before version 1.0.4. It is intentionally short: the goal is to catch a mismatch before several extra inputs create a new unknown state. A route that worked in another save is a hypothesis until its first checkpoint matches.
Keep a screenshot or written note of the starting vector if you are testing a source. If the first movement is blocked, do not mark the route as a failed algorithm. A linked plate at an edge can make a legal-looking input impossible, and a direction label may describe pin movement rather than plate movement.
Check the build and resource message
Open Settings and compare the displayed version with the official note you are using. Read the key-versus-lockpick message as context, not as a lock solution. If the build is different, mark the older route as unverified for this save.
Identify the exact chest
Confirm the area, room, landmarks, owner or quest context, and reward expectation. A named chest is not identified by a similar model alone. Reward movement makes this step more important after the patch.
Observe the live plate state
Count the plates, number holes consistently, and record the full starting vector. If you test a relationship, make one controlled movement and note every resulting plate position. Do not mix rows from a video using a different direction convention.
Solve and verify checkpoints
Enter the current state into the solver and follow the first group only. Compare the expected vector after each group. Stop at the first mismatch and remap the current state rather than continuing a route from the past.
Version checks, dates, and evidence limits
Patch information ages quickly. This page records the source check date so the reader can distinguish a verified historical note from a claim that a build is still the latest. When a later official announcement appears, update the version, changelog identifier, affected reward examples, FAQ answers, and image captions together. Do not update only the headline and leave an older build in the body.
The official source is strongest for release facts and explicit change descriptions. The Steam store page is useful for official game context, while community posts and videos can help explain what a player sees but cannot establish a universal mechanic by themselves. If two reports disagree, preserve the build number, source date, chest identity, and first observed movement before deciding which one is usable.
This is an independent guide. It uses the official game and release-note pages as references, but it does not speak for the developer or publisher. The visual assets on this page are explanatory illustrations. They are not evidence of a real UI state, a reward location, or an official screenshot.
| Evidence type | Good use | Limit |
|---|---|---|
| Official changelog | Version, CL number, and explicit changes | Only says what the note records |
| Official Steam or game page | Game identity and publisher context | Not a chest-by-chest lock database |
| Player video or forum post | Room clues and reproducible observations | May use another build or direction convention |
| Solver result | A route from the entered live state | Depends on correct inputs and observed relationships |
How to update this page after another patch
First verify the new official announcement and its linked changelog. Then compare the version, date, CL number, lock-related wording, reward examples, and any affected internal guides. Update the sitemap lastmod for all eight locale URLs only when their visible copy has actually been refreshed.
If the later note says nothing about linked plates, keep the lock explanation cautious. Say that the official note does not document a plate-rule change, and continue directing readers to the visible state and solver. That is more useful than inventing a balance change from a different community report.
Media checked for this guide
The official Gothic site, official Steam store page, and official Steam news area were checked first for game context and release-note evidence. The SteamDB patch-notes result was considered during keyword research but returned 403 in this environment, so it is not used as evidence here. No official screenshot was found that safely and clearly demonstrates all linked-plate states or the exact moved reward examples.
Because the page is about interpreting a patch rather than presenting a single official screenshot, it uses three labeled AI-generated editorial illustrations: the version checkpoint, the Old Mine reward-identity problem, and the post-patch lock-check flow. They are distributed beside the relevant sections and are never used to carry the factual conclusion.
Gothic 1 Remake patch notes FAQ
Which Gothic 1 Remake version do these patch notes cover?
The official changelog checked on August 8, 2026 identifies version 1.0.4 as CL 171261. Check the number in Settings again after a future update.
Did patch 1.0.4 change the Gothic Remake lockpicking system?
The explicit lock-related change is a voice distinction between a missing key and a missing lockpick. The checked changelog does not describe a new linked-plate rule, so the solver still needs the current visible state.
Why are chest rewards different after the Gothic Remake update?
The official notes describe moved rewards, including examples in the mages area and the Old Mine. Recheck the chest identity and room context separately from the lock route.
Can I use a fixed chest code after patch 1.0.4?
Only when the chest identity, first movement, plate count, and every affected relationship match the source. If a checkpoint differs, reload and map the live lock instead of forcing a route from another build.
Are these official Gothic 1 Remake patch notes?
The release facts are summarized from the official changelog and official Steam announcement. This page remains an independent fan guide and is not published by Alkimia Interactive or THQ Nordic.
Where can I solve a Gothic Remake chest after the patch?
Open the Gothic Lockpick Solver when the chest lock is visible and you can record the plates. The solver handles the live mechanism; patch and location pages provide the surrounding context.
Bottom line for Gothic 1 Remake patch 1.0.4
Use the official note to update your expectations about voice feedback and reward placement. Use the visible chest to establish the current lock state. The reliable bridge between those two facts is a version-aware checklist, not an unlabelled fixed sequence.
If the first movement of an older route still matches, continue with checkpoint checks. If it does not, stop early and use the solver from the state in front of you. Keep the date, build, chest identity, and source URL with any route you share so another player can reproduce the test.
Official sources and verification notes
- Official Gothic 1 Remake Steam newsThe official announcement area and its linked G1R_Patch_1.0.4.txt changelog were used for the version and change summary.
- Official Gothic 1 Remake Steam pageUsed for official game context and source identity, checked August 8, 2026.
- Official Gothic game siteUsed for official game and publisher context; this guide does not claim affiliation.