Chest-focused planner
Gothic Remake Chest Solver
Enter the plates you see on a Gothic Remake chest, map how they react, and get a legal A/D route without losing your place.
Discover one plate at a time
Capture the current state, make exactly one in-game move, update the holes above, then record the reaction.
Capture a baseline before changing the plate positions.
Plate relationship matrix
Rows are moved plates; columns are affected plates.
Use this Gothic Remake chest solver while the lock is open
Pause at the lock view and number the plates from 1 at the back to the highest number at the front. Each vertical track contains seven holes; hole 1 is the far-left position and hole 7 is the far-right position. Click the matching starting hole above before testing a movement. The target is hole 4, the center, for every plate.
How to map an unknown chest safely
- Record every initial plate position before touching A or D.
- Select a test plate and press one direction exactly once.
- Enter the new observed positions in Guided mode and record the test.
- Return to a known state, then test another active plate.
- Solve only after the current positions and directional links match the chest.
A relationship is directional. If moving plate 4 drags plate 2, the reverse does not follow unless your own test confirms it. This is the most common reason a route looks correct on the site but diverges in-game.
Why a chest may show “no route”
The solver rejects any move that would push an affected plate outside holes 1–7. A no-route result can therefore be real, but input mistakes are more common. Check whether left and right were reversed, whether a linked plate moved oppositely, and whether your start state includes changes made during testing. Clear links and remap the lock when observations came from different reset states.
Privacy and saved work
The calculation runs locally in your browser. This page does not upload lock layouts, save names, or game files. Copy the resulting keyboard chain if you want to keep it. Changing any position or relationship immediately invalidates the displayed route so an old answer cannot be mistaken for a current one.
Chest solver FAQ
Can this solve every Gothic Remake chest?
It can solve any four-to-seven plate mechanism that follows the entered Same, Opposite, and None relationships and has a reachable center state.
Which hole is the target?
Hole 4, the center of each seven-hole track, is the default target.
Should I reset the chest before mapping?
A known baseline makes observations easier. If you cannot reset, enter the complete current state before each clean one-move test.
Can I save a named chest?
The current release favors explicit copy and example actions; it does not silently upload or auto-save chest layouts.
Gothic Remake Chest Solver Setup
Use the Gothic Remake Chest Solver while the chest view is still open and every current hole is visible. The Gothic Remake Chest Solver calculates from the live state, so testing a key after data entry requires a position update before solving.
Gothic Remake Chest Solver Inputs
The Gothic Remake Chest Solver accepts four to seven plates and directional Same, Opposite, or None links. A Gothic Remake Chest Solver observation should compare states separated by exactly one legal A or D movement.
Gothic Remake Chest Solver Results
Each Gothic Remake Chest Solver route includes expected plate positions after every step. Follow the Gothic Remake Chest Solver route only while those checkpoints match the game; stop and remap the active row at the first difference.
Before You Follow a Chest Route
- Use the Gothic Remake Chest Solver with the chest's current plate positions.
- Use the Gothic Remake Chest Solver after checking every active relationship row.
- Use the Gothic Remake Chest Solver again when a predicted checkpoint differs.
Reading plate reactions accurately
Use the visible direction of travel, not the direction you expect from the key. After an A test, the active plate should shift one hole toward the left side of your numbering. A coupled plate that also decreases by one is Same. A coupled plate that increases by one is Opposite. Record None only if the attempted movement was legal and the plate had room to move. An edge can hide a relationship by blocking the complete action.
Keep the active plate separate from affected plates in your notes. The active plate always follows its own key, so its diagonal matrix entry is fixed to Same. Every off-diagonal entry needs an observation. The interface does not mirror a relationship automatically because mechanisms can be directional.
Following a long chest route
Long solutions are easier when treated as checkpoints. The numbered list shows the active plate, direction, and expected complete state. Perform one group, compare all tracks, then continue. The keyboard chain is convenient for uninterrupted play, but the expanded list is better for diagnosing a mismatch. R begins the chain by returning selection to the front plate; W walks toward lower plate numbers and S toward higher numbers.
If your control bindings differ, use the semantic direction and plate number rather than copying letters blindly. A and D on this page mean left and right plate movement. W and S describe plate selection according to the front-to-back convention.
Example troubleshooting scenarios
The first move is blocked
Verify that every linked plate has space in the required direction. A move that helps the active plate may be illegal because another affected plate is already at hole 1 or hole 7.
The route reaches the center except for one plate
Check relationships used near the end. An omitted link can make the simulated state look more favorable than the chest. Repeat a controlled test on the plate active when states first diverged.
The same chest gives a different route
A shortest route depends on its complete starting state. If testing moved even one track, a new route can be different. Multiple shortest routes can also exist; the solver returns the first one found.
Related resources
The main Gothic lockpick solver explains the algorithm. The lockpicking guide covers clean experiments. The solutions page teaches matrix notation.
Accuracy checklist before using a route
Confirm four facts before pressing the first key: the plate count matches the lock, plates are numbered in the same back-to-front order used by the site, every selected hole matches the live screen, and each relationship belongs to the row of the plate that caused it. A single reversed row can produce a route that looks plausible for several steps. The expected-state line is therefore part of the answer, not optional decoration.
Pause after each movement when testing a newly mapped chest. Compare the full vector rather than watching only the active plate. If the vector differs, do not continue hoping the later steps will correct it. The solver's next state assumes the earlier state was exact. Update the visible holes, repeat the uncertain controlled test, and calculate from the new baseline.
Limits of a fan-made planning model
This site implements the documented seven-hole linked-plate model derived from visible play observations and the supplied reference implementation. It cannot verify changes in an unreleased or newly patched game build, detect a mod, or know whether an input was blocked by a different in-game rule. Results are calculations under the entries shown on the page, not guarantees about a particular chest.
That limitation is also useful: every assumption is visible. You can change one connection, calculate again, and compare the predicted states. When sharing feedback, include the plate count, starting vector, relationship row, and first mismatching state. Those details make a correction testable and help keep the solver accurate as the game evolves.
One final verification
Before acting on any calculated sequence, compare its first predicted movement with the chest. This small check confirms the plate order, direction convention, and active relationship row at once. Stop at the first disagreement, correct the visible inputs, and generate a new route. Continuing from a mismatched state makes every later checkpoint unreliable.