TRENCH: DECAY missions are best understood through the four verbs the developer publishes: push the line, survive the gas, extract with your squad, and move the LIVE WAR MAP through victories. Those facts establish a deployment loop and a shared campaign layer. They do not establish a fixed list of objective names, maps, difficulties, timers, victory thresholds, or reward formulas.
This hub gives you a reliable way to read a current deployment without pretending that an older screenshot is a permanent mission script. Use the live objective display for the exact task, keep the squad connected during the push, reserve a return route before gas changes the situation, and treat extraction as a required phase. After the result, inspect the live war map and record what the current build actually shows.
The confirmed deployment loop
The phase names in this table are descriptive labels for the confirmed loop, not claims about menu wording. If the current client uses different labels, follow the client. The value of the model is that it keeps the entire deployment in view: advancing is only one part of a successful run.
Before deployment: establish the current task
Complete the Commissar onboarding if it is still presented to your account. The official description identifies the Commissar as the new-player guide, but the static page does not publish the tutorial sequence. Use the current prompt to learn how this build communicates objectives and interaction.
Open Preferences and confirm controls before joining a mission. Interaction, movement, stance, inventory, and map access must come from the current menu. A mission plan fails quickly if a player relies on a key list from another build and cannot operate the live objective.
At the deployment screen or starting area, read every visible condition: the task, any status indicator, the squad’s route, and any extraction or failure language. This hub does not publish specific objective names because none passed the evidence gate. The operation is still concrete: identify what the current game says must change before the group moves.
Choose an initial anchor. That can be a visible teammate, a trench junction, or another clear position behind the lead. The anchor gives you a way to recognize overextension even when the battlefield is visually busy.
Push the line without losing the mission
The developer explicitly tells players to “push the line.” A useful push moves the squad from one position it can support to another; it is not continuous forward motion. Before crossing a gap, check whether teammates are close enough to cover the same route and whether the live objective still points forward.
Move in short commitments. Reach cover, re-check the objective, re-establish the squad, and then decide on the next move. This rhythm makes it easier to react if gas, a new task, or an extraction instruction changes the priority.
Avoid chasing an isolated contact away from the route unless the current objective requires it. The public evidence does not establish named enemy behaviors, wave rules, or kill quotas. Let the current task decide whether an engagement advances the mission.
If the group splits, communicate the visible route and objective rather than inventing a strategy name. Select the branch with readable mission information, connected teammates, and a known way back. The Tactics hub offers more squad and cover decisions.
Survive gas as an information problem
Gas is officially named, but the exact hazard model is not public enough for a dedicated canonical child page. That means your first responsibility is observation: identify the warning supplied by this build, where the squad moves, and which route remains usable.
Keep a retreat or lateral route in mind before entering an exposed area. A known route is valuable even if the beta changes timing or protection equipment, because it reduces the number of decisions made after the hazard arrives.
Do not publish or repeat a countdown from memory as though it is universal. Server versions, mission conditions, or future updates may differ. If the interface shows a timer or equipment state, use it for the current run and record its build context before sharing.
Gas-mask names, acquisition, immunity, damage, and durability remain in-game verification items. A cosmetic-looking item should not be assumed to provide protection, and a historically plausible object should not be assumed to exist.
Treat extraction as the mission’s final objective
The official description includes extraction with the squad. When the live objective changes toward extraction, stop measuring success only by ground gained or enemies engaged. Reorient the group toward the exit information supplied by the current build.
Regroup before the final movement when possible. Check the last known position of nearby teammates and communicate the route. Preserve enough time and space to correct one wrong turn instead of committing every player to the first guessed direction.
The extraction trigger, countdown, squad requirement, and reward condition are not established here. Follow the current prompt exactly. If one player reaches a marker and nothing happens, re-read the task before deciding that the game is broken.
After extraction, capture the result screen and any visible reward or campaign change separately. A successful departure does not automatically prove a particular Medals amount, crate grant, or live-map contribution.
Read the LIVE WAR MAP carefully
The map is first-party confirmed as shared on every server, and the developer says victories move it. This makes an individual mission part of a community-wide front. It does not tell us how many victories are needed, whether defeats move the map, which direction a result applies, or when the state resets.
Use the map for orientation and current context. Record the date, displayed build, visible front state, and what your result screen called the outcome. If the map changes, describe what you observed without assigning the entire movement to your squad.
The [MAJOR ORDER] title visible at the 2026-07-30 checkpoint suggests an update theme, but the public description does not define Major Order mechanics. Do not create requirements, objectives, timers, or rewards from the title alone.
A dedicated live-war-map child page remains deferred because the exact UI and contribution rules did not have enough current evidence to meet the article-depth gate. This hub keeps the verified concept accessible while avoiding a thin page dominated by unknowns.
Mission review after every run
Write down the live objective language, the moment the squad began pushing, the gas warning you actually saw, the extraction instruction, and the result label. These observations turn a vague loss into a useful next-session adjustment.
Separate route failure from combat failure. If the squad lost contact, missed an objective change, or had no return path, a different weapon may not solve the problem. If the live interface showed a specific equipment or interaction requirement, then the Arsenal or controls check becomes relevant.
Compare the result with the live war map, but do not calculate a contribution formula from one observation. Repeatable measurements across the same build would be needed before a numeric claim could be published.
Check Updates before treating your notes as current after a major title or build change. TRENCH: DECAY is officially in active beta and search caches can lag behind the live page.
Mission FAQ
What are the missions in TRENCH: DECAY?
The official public description confirms a squad PvE loop of pushing the line, surviving gas, extracting, and contributing victories to a shared live war map. A complete named mission list was not verified.
How do victories move the war map?
The developer states that every victory moves the shared map. Exact contribution values, direction, reset timing, and front rules require current creator or in-game evidence.
What is a Major Order?
[MAJOR ORDER] was the official page-title prefix at the checkpoint. No detailed Major Order mechanic is claimed from that title alone.
How do I survive gas?
Follow the current warning and objective UI, stay connected to the squad, and preserve a known route. Exact equipment, timing, and damage rules remain build-specific.
How do I extract?
Read the live objective when the priority changes, regroup, and follow the current marker or instruction. Trigger and countdown details were not reliably established.
Where are difficulty and objective guides?
They are deferred until current names, rules, and operations can support substantial pages. Publishing thin pages would be less useful than keeping the verified loop in this hub.