The Dreadnought is a conditional Control comeback unit, not a guaranteed reward for losing. Eligibility combines ticket state, lobby size, and player performance, and all exact thresholds require a current-server check.
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.
- Mode scope. The official card presents Dreadnought as a Control mechanic. Do not promise it in Assault, Territory Push, or Final Stand.
- Ticket deficit. Current documentation uses a severe deficit: the losing side at or below 75 tickets while the opponent remains above 300. These are dated thresholds.
- Lobby requirement. The checked card requires at least 20 players, so a small server may never enable the system even with the correct score.
- Performance selection. The unit is assigned to a strong performer using current kill-rate and playtime criteria described by the board. Exact figures can change and are not a manual spawn command.
- Warning phase. The system provides a warning around deployment. Use it to regroup and identify the route rather than crowding the spawn area.
- Ticket effect. While active, the losing team receives the documented infinite-ticket effect until the opponent is reduced to the specified range. Keep contesting the point.
- Health and decay. The current card lists 11,000 health that decays across roughly ten minutes. Treat both as balance values and protect the limited window.
- Team support. Clear close threats, cover flanks, report anti-unit pressure, and continue capturing. A Dreadnought unsupported off-point can still fail to reverse the round.
A practical way to use this information
Use this sequence when grave/digger dreadnought guide matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm mode scope. The official card presents Dreadnought as a Control mechanic. Do not promise it in Assault, Territory Push, or Final Stand. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger dreadnought guide plan. Player action: State what the current server confirms about mode scope.
- Connect ticket deficit to lobby requirement. Current documentation uses a severe deficit: the losing side at or below 75 tickets while the opponent remains above 300. These are dated thresholds. Then account for this related rule: The checked card requires at least 20 players, so a small server may never enable the system even with the correct score. 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 performance selection safely. The unit is assigned to a strong performer using current kill-rate and playtime criteria described by the board. Exact figures can change and are not a manual spawn command. 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 performance selection.
- Build around warning phase. The system provides a warning around deployment. Use it to regroup and identify the route rather than crowding the spawn area. 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 warning phase changes the plan.
- Review health and decay and team support. The current card lists 11,000 health that decays across roughly ten minutes. Treat both as balance values and protect the limited window. Compare the round result with the final caution: Clear close threats, cover flanks, report anti-unit pressure, and continue capturing. A Dreadnought unsupported off-point can still fail to reverse the round. 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 dreadnought guide rules to the round in front of you.
- Mode scope or Ticket deficit. The official card presents Dreadnought as a Control mechanic. Do not promise it in Assault, Territory Push, or Final Stand. Compare that with ticket deficit: Current documentation uses a severe deficit: the losing side at or below 75 tickets while the opponent remains above 300. These are dated thresholds. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- Lobby requirement changes the setup. The checked card requires at least 20 players, so a small server may never enable the system even with the correct score. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger dreadnought guide plan toward performance selection instead.
- Warning phase changes the timing. The system provides a warning around deployment. Use it to regroup and identify the route rather than crowding the spawn area. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Ticket effect sets the limit. While active, the losing team receives the documented infinite-ticket effect until the opponent is reduced to the specified range. Keep contesting the point. Keep team support in view as well: Clear close threats, cover flanks, report anti-unit pressure, and continue capturing. A Dreadnought unsupported off-point can still fail to reverse the round. 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 ticket deficit. Current documentation uses a severe deficit: the losing side at or below 75 tickets while the opponent remains above 300. These are dated thresholds. Correct the mistake by checking that condition before attempting mode scope or committing a limited resource.
- Overgeneralizing performance selection. The unit is assigned to a strong performer using current kill-rate and playtime criteria described by the board. Exact figures can change and are not a manual spawn command. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting ticket effect. While active, the losing team receives the documented infinite-ticket effect until the opponent is reduced to the specified range. Keep contesting the point. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing team support in time. Clear close threats, cover flanks, report anti-unit pressure, and continue capturing. A Dreadnought unsupported off-point can still fail to reverse the round. 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 Dreadnought Guide, join through the official Roblox page and first locate evidence for mode scope, performance selection, and team support. 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.