Grave/Digger Loadouts

A good loadout is legal, understandable, and matched to a job. Start with inventory weight and class tools, then choose range, ammunition behavior, a perk, and any owned modification that helps the current compound and mode.

Every weapon, perk, and modification spends part of a limited loadout budget. Handling, ammunition, cramped tunnels, class tools, and the current objective matter more than a universal damage ranking.

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.

• Weapons. Current documented primary and secondary weapon names, weight classes, handling inputs, and selection questions.
• Weapon modifications. Ownership requirements, menu toggles, documented map pickups, and version-sensitive locations.
• Perks. The current perk roster, Medal cost, class restrictions, elite behavior, and role-based selection.
• Loadout guide. A step-by-step method for combining class, weight, weapon, perk, terrain, and fallback.

A reliable workflow for this section

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

1. Start with Weapons. Current documented primary and secondary weapon names, weight classes, handling inputs, and selection questions. Use that answer to name the immediate grave/digger loadouts decision before opening another branch. Player action: Follow /loadouts/weapons/ and apply one recommendation.
2. Compare Weapon modifications. Ownership requirements, menu toggles, documented map pickups, and version-sensitive locations. Check how it changes the first answer instead of treating both pages as unrelated reading. Player action: Use /loadouts/weapon-modifications/ when the current round exposes that condition.
3. Add Perks context. The current perk roster, Medal cost, class restrictions, elite behavior, and role-based selection. Translate the relevant detail into one route, responsibility, resource, or fallback the squad can act on. Player action: Open /loadouts/perks/ before committing a limited kit or irreversible purchase.
4. Verify inventory weight. Confirm the class budget and the weight of every selected weapon before designing around a combination. 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 squad resources. Account for ammunition support, treatment, construction, reconnaissance, and who can safely cover a reload or weapon swap. 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.

• Inventory weight comes first. Confirm the class budget and the weight of every selected weapon before designing around a combination. If it is unknown, delay the high-risk grave/digger loadouts choice and gather that information.
• Owned base weapon changes the branch. A modification requires its base weapon under the documented system; seeing a pickup does not grant permanent ownership. Use the focused page or live prompt that resolves this condition before copying a route from another round.
• Expected distance changes the resource plan. Choose for the compound’s doors, halls, windows, vertical angles, and open crossings rather than a universal ranking. Coordinate the adjustment so one player’s solution does not remove a capability the squad still needs.
• Squad resources controls confidence. Account for ammunition support, treatment, construction, reconnaissance, and who can safely cover a reload or weapon swap. 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.

• Inventory weight. Confirm the class budget and the weight of every selected weapon before designing around a combination.
• Owned base weapon. A modification requires its base weapon under the documented system; seeing a pickup does not grant permanent ownership.
• Expected distance. Choose for the compound’s doors, halls, windows, vertical angles, and open crossings rather than a universal ranking.
• Squad resources. Account for ammunition support, treatment, construction, reconnaissance, and who can safely cover a reload or weapon swap.

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. Begin with the specialist responsibility and its fixed equipment.
• Modes. Build for the actual capture, defense, push, or survival condition.
• Maps. Use compound geometry to choose range and a fallback route.

Sources checked

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