DREADMOOR Opening the Gate: The Throat Demo Route

Treat The Throat as a sequence of prerequisites

The Throat gate is not opened by starting the generator alone. The recorded walkthrough describes a chain in which power enables an initial attempt at the controls, followed by additional repair objectives. Keeping those states separate explains why a running generator can coexist with a closed passage.

Follow the active journal objective as you move through the complex. The names of the outstanding tasks distinguish missing power, unfinished repairs and water that has not reached both wheels. Repeating a completed interaction is less useful than identifying which stage the objective still describes.

The walkthrough places this puzzle after the settlement, Dry Dock and engine progression. That context matters if you are comparing your route to a later demo screenshot. Reaching similar machinery earlier in the game is not proof that every prerequisite for the gate has already been completed.

Establish generator power

The generator is part of the gate complex reached on foot after docking at The Throat. The recorded interaction uses a local Fuel Can to fill its tank and a separate action to start it. A filled generator is not the same state as a running one.

Do not substitute the earlier boat-pump task for this interaction. The fuel guide distinguishes production, vessel transfer and the generator's carried-can sequence. The generator location page provides the supported area-level guidance without inventing an exact stair or compass route.

After startup, continue to the gate controls rather than assuming that supplying fuel has finished the complex. The recorded route includes an initial Gate Control attempt before the further repair work. That attempt belongs to the sequence and should be interpreted alongside the journal's resulting objectives.

Work through the documented repairs

The source walkthroughs agree on a repair stage involving several different components. Their checklist identifies the electrical component, the gear-and-axle assembly, two buckets and the water pump. These are distinct tasks, not alternate names for one repair interaction.

Use the installed build's objective wording for the actual repair interaction and requirements. The research does not establish a complete release-build material table for every component in this puzzle. Adding ingredient quantities or hidden repair locations would go beyond the supplied evidence.

Route water to both wheels

After repairs, the recorded demo uses water-channel controls and hook-gun-operated pivots to direct the flow. The required state is water reaching both wheels so that both rotate. One wheel moving is not the documented completion condition for the stage.

Check each side after changing the routing. The waterwheel guide explains the difference between a repair objective and a flow objective. It does not give a numbered switch combination because the research did not cross-verify that layout.

The developer's preview material confirms generator and water-flow systems, while the detailed order comes from demo walkthrough coverage. Those sources support the staged puzzle described here. They do not justify an extra timer, hidden lever or additional activation rule that the recorded sequence never established.

Return to Gate Control and pass through

The final gate-control interaction comes after the waterwheel requirement. Completing the flow arrangement does not replace returning to the controls. Once the passage is open, the documented route returns to the boat and continues through it.

Keep that final action separate from the earlier control attempt. The first attempt reveals or advances the repair work, while the later interaction follows completion of the machinery state. A walkthrough that mentions Gate Control twice is therefore describing two stages rather than accidentally duplicating one instruction.

The demo's completion screen is not evidence that the Early Access campaign ends at the same point. This guide follows the documented demo route and does not claim a complete campaign ending. Use the version label when comparing the passage with footage from a different playtest or release build.

Recognize a possible version-specific problem

If the journal remains unresponsive despite the documented work being complete, record the exact outstanding objective. The source notes distinguish reported bucket-quest softlocks from the ordinary flow-routing task. That behavior should not automatically be treated as proof that another hidden interaction exists.

Preserve the affected save before trying a reset or replacing progress. The saving guide explains the supported backup information and the limits of save-control evidence. A report that includes the build, completed repairs and visible wheel state is more useful than a claim that the entire gate is simply broken.

Related guides