The Gorge carries the official completion wording Survive the Gorge and the gold award Valour Under Fire. “Survive” does not mean searching for a conventional health bar—the developer FAQ says the Nest has no conventional health system. Survival comes from following the mission’s active states under pressure.
2950790, Windows public 1.0, checked 2026-08-09. Failure triggers, target positions, and medal thresholds remain live-operation evidence.Create a pressure-proof ledger
Number dispatches, active targets, requested effects, restrictions, and completed responses. Under pressure, this short list prevents returning to an old objective or overlooking a new page.
Read the full message before moving the gun. A few seconds of clarity can save a whole reload.
Maintain clean map states
Use separate marks for observers, enemies, friendlies, impacts, and final firing lines. Label new intelligence instead of erasing old. If a target moves, treat the old point as history.
Only measure from the Nest after resolving the current target. A pressure event near the bunker is not automatically a valid source-to-target line.
Keep one ready plan and one contingency
Prepare the active barrel exactly: shell, powder, elevation, bearing, arming. A second barrel can support a known next effect, but do not guess a future order and lock scarce ammunition into it.
Use the Requisition Console deliberately. The official evidence does not provide a universal resource budget, and gold conditions may care about expenditure.
Respond to impact before reloading
Wait for observer or teleprinter feedback. Classify the shot and update the ledger. If it was correct, determine whether another target appeared. If it missed, change the one proven variable.
Rushed repeated shots can cross gun states. Name left/right, load, elevation, and arming side before every firing action.
What “stuck” can mean here
Check for unread dispatch, unmet effect, active second target, newspaper, or transition interaction. Inspect mechanical prerequisites when a lever is locked. If the map appears contradictory, review origins instead of averaging lines.
After a crash, update to PATCH 1.0 (1558) before judging save or mission-entry behavior. Preserve Cloud data and verify files.
Valour Under Fire research
The achievement confirms gold on all The Gorge medals but does not say whether valour measures time, accuracy, resource use, assistance, or another behavior. Capture live medal hints on a baseline completion.
Test one variable per replay and record the full state. A gold result on an older patch should be labeled rather than merged into a current threshold.
Finish cleanly
Do not force-close after the last impact. Read the newspaper, record medals, and complete the normal transition. This protects progress and gives a clear endpoint for any report.
Next use Rock of Gibraltar or review Loading if pressure caused crossed barrel states.
Reduce workload under pressure
Prepare blank card rows and a dispatch ledger before starting. Keep the map tools selected deliberately and return every physical control to a known focus state. These habits reduce walking and memory demand without guessing future objectives.
If the operation accelerates, prioritize correctness in this order: identify active objective, confirm target, confirm effect, confirm live gun. A medal attempt can be abandoned while the completion remains recoverable. After the run, compare where attention broke down—message reading, geometry, requisition, loading, or transition—and practice that station in a lower-pressure Challenge context. Do not interpret every dramatic event as damage to a hidden health pool. Use only the mission’s explicit state and result, and document any reproducible failure trigger with the full dispatch sequence.
Use the after-action newspaper as the final status check. Compare it with the last dispatch and the targets you marked resolved. If an event felt threatening but never appeared in the objective or result, keep it as atmosphere or uncertain behavior instead of constructing a hidden failure rule. Reproduce on a clean replay before adding it to a walkthrough. This protects new operators from unnecessary steps while retaining a lead for testing.