Assault is an asymmetric race through three objectives. Attackers spend a limited, draining ticket resource; defenders trade time and space to stop the sequence.
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.
- Defender preparation. The current card gives defenders 50 seconds to set routes and firing positions. Use the time to plan a fallback, not only the first doorway.
- Attacker resource. Attackers currently begin with 150 tickets and lose one every five seconds in addition to combat losses. Exact values are version-sensitive.
- Attacker respawn. The checked documentation lists a 25-second attacker respawn, allowing pressure to return faster when routes remain organized.
- Defender reinforcement. Defenders are documented with unlimited tickets but a 45-second respawn. Local defender losses can still open a long capture window.
- Sequential objectives. Three objectives must be taken in order. Advancing too far before the current capture finishes can leave the valid point understaffed.
- Capture reward. A captured objective currently returns 50 tickets to attackers. Preserve enough players on the point to earn the resource.
- Overtime. Overtime can continue while an attacker remains on the active objective. Clearing the actual boundary matters more than nearby eliminations.
- Elite access. Shock Trooper conditions differ by side and state. Read the current conversion prompt before relying on an elite defense or push.
A practical way to use this information
Use this sequence when grave/digger assault mode matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm defender preparation. The current card gives defenders 50 seconds to set routes and firing positions. Use the time to plan a fallback, not only the first doorway. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger assault mode plan. Player action: State what the current server confirms about defender preparation.
- Connect attacker resource to attacker respawn. Attackers currently begin with 150 tickets and lose one every five seconds in addition to combat losses. Exact values are version-sensitive. Then account for this related rule: The checked documentation lists a 25-second attacker respawn, allowing pressure to return faster when routes remain organized. 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 defender reinforcement safely. Defenders are documented with unlimited tickets but a 45-second respawn. Local defender losses can still open a long capture window. 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 defender reinforcement.
- Build around sequential objectives. Three objectives must be taken in order. Advancing too far before the current capture finishes can leave the valid point understaffed. 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 sequential objectives changes the plan.
- Review overtime and elite access. Overtime can continue while an attacker remains on the active objective. Clearing the actual boundary matters more than nearby eliminations. Compare the round result with the final caution: Shock Trooper conditions differ by side and state. Read the current conversion prompt before relying on an elite defense or push. 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 assault mode rules to the round in front of you.
- Defender preparation or Attacker resource. The current card gives defenders 50 seconds to set routes and firing positions. Use the time to plan a fallback, not only the first doorway. Compare that with attacker resource: Attackers currently begin with 150 tickets and lose one every five seconds in addition to combat losses. Exact values are version-sensitive. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- Attacker respawn changes the setup. The checked documentation lists a 25-second attacker respawn, allowing pressure to return faster when routes remain organized. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger assault mode plan toward defender reinforcement instead.
- Sequential objectives changes the timing. Three objectives must be taken in order. Advancing too far before the current capture finishes can leave the valid point understaffed. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Capture reward sets the limit. A captured objective currently returns 50 tickets to attackers. Preserve enough players on the point to earn the resource. Keep elite access in view as well: Shock Trooper conditions differ by side and state. Read the current conversion prompt before relying on an elite defense or push. 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 attacker resource. Attackers currently begin with 150 tickets and lose one every five seconds in addition to combat losses. Exact values are version-sensitive. Correct the mistake by checking that condition before attempting defender preparation or committing a limited resource.
- Overgeneralizing defender reinforcement. Defenders are documented with unlimited tickets but a 45-second respawn. Local defender losses can still open a long capture window. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting capture reward. A captured objective currently returns 50 tickets to attackers. Preserve enough players on the point to earn the resource. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing elite access in time. Shock Trooper conditions differ by side and state. Read the current conversion prompt before relying on an elite defense or push. 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 Assault Mode, join through the official Roblox page and first locate evidence for defender preparation, defender reinforcement, and elite access. 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.