Grave/Digger Guides

Use this guide hub to move from first spawn to a controlled first round. It prioritizes the objective, readable inputs, a legal loadout, and official sources before advanced class or map decisions.

Grave/Digger rewards deliberate movement, readable communication, and familiarity with the menu before speed. The official experience description recommends keyboard and mouse because console support is incomplete.

Choose the right starting page

Use this hub as a routing page, not as a substitute for the focused guides. Begin with the question you need to solve, then return here when the mode, map, class, or resource state changes. Developer documentation and the live Roblox listing were checked on 2026-09-01.

• Beginner guide. A first-session route from joining the official experience through reviewing the result of one complete round.
• Controls. Keyboard, mouse, interaction, camera, menu, grenade, objective, and console-support notes.
• Trello. How to use the official developer board without treating every historical number as current.
• Discord. Verified community and Trello-server invitation paths, with basic account and link safety checks.

A reliable workflow for this section

The following routine keeps grave/digger guides advice tied to the current round and avoids spending resources on an assumption that can be checked first.

1. Start with Beginner guide. A first-session route from joining the official experience through reviewing the result of one complete round. Use that answer to name the immediate grave/digger guides decision before opening another branch. Player action: Follow /guides/beginner/ and apply one recommendation.
2. Compare Controls. Keyboard, mouse, interaction, camera, menu, grenade, objective, and console-support notes. Check how it changes the first answer instead of treating both pages as unrelated reading. Player action: Use /guides/controls/ when the current round exposes that condition.
3. Add Trello context. How to use the official developer board without treating every historical number as current. Translate the relevant detail into one route, responsibility, resource, or fallback the squad can act on. Player action: Open /guides/trello/ before committing a limited kit or irreversible purchase.
4. Verify objective. Identify the mode, current capture or defense task, ticket state, and any visible overtime or escape condition. Confirm it through the live interface or environment before relying on a dated number. Player action: Change only one variable during a controlled check.
5. Review source freshness. Attach changing numbers to the live menu or a dated developer card rather than a community summary with no version context. After the round, retain confirmed observations and revisit any claim contradicted by the current server. Player action: Attach changing values to the check date and source.

Decisions that change your route

The right branch depends on information visible in the current match. These checks tell you when to remain on the chosen page and when another part of the wiki should take priority.

• Objective comes first. Identify the mode, current capture or defense task, ticket state, and any visible overtime or escape condition. If it is unknown, delay the high-risk grave/digger guides choice and gather that information.
• Inputs changes the branch. Confirm movement, aiming, objective panel, menu, grenade, camera, communication, and class-specific controls before combat. Use the focused page or live prompt that resolves this condition before copying a route from another round.
• Legal loadout changes the resource plan. Check inventory weight, class equipment, selected perk, and whether the chosen weapon or modification is actually owned. Coordinate the adjustment so one player’s solution does not remove a capability the squad still needs.
• Source freshness controls confidence. Attach changing numbers to the live menu or a dated developer card rather than a community summary with no version context. Present unconfirmed edge cases as observations and keep the source date attached to changing values.

What to check during a match

Keep a short mental checklist rather than memorizing every dated value. The interface and developer documentation should answer these questions before a high-risk action.

• Objective. Identify the mode, current capture or defense task, ticket state, and any visible overtime or escape condition.
• Inputs. Confirm movement, aiming, objective panel, menu, grenade, camera, communication, and class-specific controls before combat.
• Legal loadout. Check inventory weight, class equipment, selected perk, and whether the chosen weapon or modification is actually owned.
• Source freshness. Attach changing numbers to the live menu or a dated developer card rather than a community summary with no version context.

What may change between versions

Grave/Digger is actively documented and revised. These parts deserve a fresh check whenever the Roblox listing or developer board announces a version change.

• Numbers. Health, damage, weight, ranges, ticket values, spawn timers, costs, and unlock thresholds may be rebalanced even when the named system remains.
• Availability. Classes, kits, maps, modifiers, and interactions may be restricted, replaced, or temporarily disabled. Confirm what the current menu exposes.
• Terrain and inputs. Map reworks and control updates can invalidate an old route or keybind. Follow current prompts and use old recordings only as historical context.

Continue through the wiki

These nearby sections supply the context that a focused hub cannot repeat in full. Use them when the current decision crosses from this topic into another system.

• Classes. Choose a battlefield responsibility after the basic control loop is comfortable.
• Modes. Read the win condition and ticket rules before optimizing kills.
• Maps. Turn the current compound into a route, cover, and resupply plan.

Sources checked

• Official Grave/Digger Roblox experience
• Official Grave/Digger Trello