Campaign turns individual skirmishes into a series. Read the vote, current score, modifier, and next branch so the squad prepares for the round that was selected rather than the one it expected.
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.
- Voting structure. The official card describes Campaign as a voting system in which the previous winner influences the next skirmish choice. Read the current vote interface for available branches.
- Mode icons. The documentation identifies Control, Assault, and Push choices through their Campaign icons. Confirm the text rather than relying only on color or memory.
- Series target. The current Campaign card says the first side to four skirmish victories proceeds to the concluding state. Treat the exact target as version-sensitive.
- Final Stand. A winning series leads into Final Stand, where the losing faction faces a different one-life defense and evacuation problem.
- Truce. At the documented 3–3 state a Truce option can appear. The current vote, not an assumed automatic result, determines the branch.
- Elite Reinforcement. Elite Reinforcement is a documented Campaign modifier. Check how the current round describes access before planning around extra elite kits.
- Environmental modifiers. Cave Fog, Hard Rocks, and Lantern Shortage are documented modifiers that can change visibility, mining, and navigation decisions.
- Preparation across rounds. Carry lessons about the opposing squad’s routes and roles forward, but rebuild the plan when the mode, compound, or modifier changes.
A practical way to use this information
Use this sequence when grave/digger campaign guide matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm voting structure. The official card describes Campaign as a voting system in which the previous winner influences the next skirmish choice. Read the current vote interface for available branches. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger campaign guide plan. Player action: State what the current server confirms about voting structure.
- Connect mode icons to series target. The documentation identifies Control, Assault, and Push choices through their Campaign icons. Confirm the text rather than relying only on color or memory. Then account for this related rule: The current Campaign card says the first side to four skirmish victories proceeds to the concluding state. Treat the exact target as version-sensitive. 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 final stand safely. A winning series leads into Final Stand, where the losing faction faces a different one-life defense and evacuation problem. 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 final stand.
- Build around truce. At the documented 3–3 state a Truce option can appear. The current vote, not an assumed automatic result, determines the branch. 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 truce changes the plan.
- Review environmental modifiers and preparation across rounds. Cave Fog, Hard Rocks, and Lantern Shortage are documented modifiers that can change visibility, mining, and navigation decisions. Compare the round result with the final caution: Carry lessons about the opposing squad’s routes and roles forward, but rebuild the plan when the mode, compound, or modifier changes. 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 campaign guide rules to the round in front of you.
- Voting structure or Mode icons. The official card describes Campaign as a voting system in which the previous winner influences the next skirmish choice. Read the current vote interface for available branches. Compare that with mode icons: The documentation identifies Control, Assault, and Push choices through their Campaign icons. Confirm the text rather than relying only on color or memory. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- Series target changes the setup. The current Campaign card says the first side to four skirmish victories proceeds to the concluding state. Treat the exact target as version-sensitive. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger campaign guide plan toward final stand instead.
- Truce changes the timing. At the documented 3–3 state a Truce option can appear. The current vote, not an assumed automatic result, determines the branch. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Elite Reinforcement sets the limit. Elite Reinforcement is a documented Campaign modifier. Check how the current round describes access before planning around extra elite kits. Keep preparation across rounds in view as well: Carry lessons about the opposing squad’s routes and roles forward, but rebuild the plan when the mode, compound, or modifier changes. 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 mode icons. The documentation identifies Control, Assault, and Push choices through their Campaign icons. Confirm the text rather than relying only on color or memory. Correct the mistake by checking that condition before attempting voting structure or committing a limited resource.
- Overgeneralizing final stand. A winning series leads into Final Stand, where the losing faction faces a different one-life defense and evacuation problem. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting elite reinforcement. Elite Reinforcement is a documented Campaign modifier. Check how the current round describes access before planning around extra elite kits. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing preparation across rounds in time. Carry lessons about the opposing squad’s routes and roles forward, but rebuild the plan when the mode, compound, or modifier changes. 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 Campaign Guide, join through the official Roblox page and first locate evidence for voting structure, final stand, and preparation across rounds. 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.