Use this index when the round loads: name the mode, read its objective and resource model, then open the detailed page before treating an elimination, capture, or retreat as valuable.
A useful mode plan begins with the win condition, ticket state, active objective, spawn direction, and current Campaign branch. A good firefight in the wrong place can still lose the round.
What the current documentation establishes
Developer documentation and the live Roblox listing were checked on 2026-09-01. The points below distinguish documented behavior from a suggested player response. Read exact figures as a dated reference, not a promise that future servers will retain the same balance.
- Campaign layer. Campaign is the voting and series structure that links skirmish results and can lead to Final Stand. It is broader than a single capture mode.
- Control. Control uses shared point pressure and ticket comparison. The current documentation begins both teams symmetrically and allows a conditional Dreadnought comeback.
- Assault. Assault gives attackers limited, draining tickets against defenders with different reinforcement behavior across three sequential objectives.
- Territory Push. Territory Push uses five linked points and passive ticket loss, creating a moving front and a strong reason to regroup before the next line.
- Final Stand. Final Stand makes defender lives scarce while attackers repeatedly pressure a gate and later an evacuation condition. Survival and time become core resources.
- Dreadnought. Dreadnought is a conditional Control comeback mechanic, not a normal mode selected from the opening vote.
- Elite conditions. Shock Trooper access varies by mode and round state. Follow the live conversion prompt instead of applying one threshold everywhere.
- Version-sensitive numbers. Tickets, timers, gates, spawn delays, and eligibility values are useful dated references but should be verified against current objective text.
A practical way to use this information
Use this sequence when grave/digger game modes matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm campaign layer. Campaign is the voting and series structure that links skirmish results and can lead to Final Stand. It is broader than a single capture mode. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger game modes plan. Player action: State what the current server confirms about campaign layer.
- Connect control to assault. Control uses shared point pressure and ticket comparison. The current documentation begins both teams symmetrically and allows a conditional Dreadnought comeback. Then account for this related rule: Assault gives attackers limited, draining tickets against defenders with different reinforcement behavior across three sequential objectives. The useful plan must satisfy both conditions rather than optimizing one while ignoring the other. Player action: Change one choice if the two documented conditions conflict in the current round.
- Test territory push safely. Territory Push uses five linked points and passive ticket loss, creating a moving front and a strong reason to regroup before the next line. Reproduce that behavior with one controlled input, position, purchase, or objective action while keeping the other variables stable. Player action: Use the result to confirm or revise the working rule for territory push.
- Build around final stand. Final Stand makes defender lives scarce while attackers repeatedly pressure a gate and later an evacuation condition. Survival and time become core resources. Tell nearby teammates which route, resource, target, or timing this changes so their actions support the same decision. Player action: Do not assume the squad knows how final stand changes the plan.
- Review elite conditions and version-sensitive numbers. Shock Trooper access varies by mode and round state. Follow the live conversion prompt instead of applying one threshold everywhere. Compare the round result with the final caution: Tickets, timers, gates, spawn delays, and eligibility values are useful dated references but should be verified against current objective text. Preserve observations confirmed by the live server and discard the parts it contradicted. Player action: Attach changing values to the checked date instead of presenting them as permanent.
Decisions that change the plan
There is no single correct choice for every lobby. Use these decision points to adapt the documented grave/digger game modes rules to the round in front of you.
- Campaign layer or Control. Campaign is the voting and series structure that links skirmish results and can lead to Final Stand. It is broader than a single capture mode. Compare that with control: Control uses shared point pressure and ticket comparison. The current documentation begins both teams symmetrically and allows a conditional Dreadnought comeback. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- Assault changes the setup. Assault gives attackers limited, draining tickets against defenders with different reinforcement behavior across three sequential objectives. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger game modes plan toward territory push instead.
- Final Stand changes the timing. Final Stand makes defender lives scarce while attackers repeatedly pressure a gate and later an evacuation condition. Survival and time become core resources. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Dreadnought sets the limit. Dreadnought is a conditional Control comeback mechanic, not a normal mode selected from the opening vote. Keep version-sensitive numbers in view as well: Tickets, timers, gates, spawn delays, and eligibility values are useful dated references but should be verified against current objective text. This boundary is more reliable than a context-free best choice.
Common mistakes and safer corrections
Most avoidable failures come from applying a real rule in the wrong context or treating a dated number as timeless. These corrections keep the page useful without hiding uncertainty.
- Ignoring control. Control uses shared point pressure and ticket comparison. The current documentation begins both teams symmetrically and allows a conditional Dreadnought comeback. Correct the mistake by checking that condition before attempting campaign layer or committing a limited resource.
- Overgeneralizing territory push. Territory Push uses five linked points and passive ticket loss, creating a moving front and a strong reason to regroup before the next line. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting dreadnought. Dreadnought is a conditional Control comeback mechanic, not a normal mode selected from the opening vote. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing version-sensitive numbers in time. Tickets, timers, gates, spawn delays, and eligibility values are useful dated references but should be verified against current objective text. Correct this by comparing the checked developer card with the current interface and labelling any unconfirmed edge case as an observation.
How to verify the current server
Developer documentation and the live Roblox listing were checked on 2026-09-01. To verify Grave/Digger Game Modes, join through the official Roblox page and first locate evidence for campaign layer, territory push, and version-sensitive numbers. Compare the visible objective, menu, item description, prompt, or map geometry with the relevant developer Trello card. When they differ, preserve what the current server displays and keep the older value as dated history. If neither source confirms the edge case, change one variable in a controlled match test and label the result as an observation rather than a permanent rule.
Current-documentation note: Checked 2026-09-01. Exact balance, timers, availability, map rotation, inputs, and unlock thresholds can change. Confirm the current server UI before spending Medals or relying on a numeric breakpoint.
Continue from here
Use the related pages to turn this focused answer into a complete round plan. Each link stays inside the same source-language guide and addresses a different decision layer.
- Modes hub. Compare the current rule set with the other Campaign branches.
- Class index. Fill the responsibility the objective and reinforcement pattern require.
- Compound index. Turn the active point sequence into a route and fallback.