No developer-confirmed promo-code entry or reward-code system was documented in the official Grave/Digger sources checked on September 1, 2026. This page explains exactly what was checked and how to recognize a real system if one appears.
A codes page is useful only when it separates an actual developer-confirmed redemption system from vote-kick commands, data-restoration commands, puzzle passwords, and ordinary promotional language.
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.
This is intentionally a single-page section. The official Roblox description documents a public vote-kick command and a data-restoration command, but neither is a promotional reward code. The developer Trello documents controls, weapons, perks, modes, maps, progression, lore, and updates without providing a redemption menu or active code list. Puzzle passwords and private-server commands also belong to their own systems. Until the developer publishes a redemption path, there are no child code-list pages to browse.
A reliable workflow for this section
The following routine keeps grave/digger codes advice tied to the current round and avoids spending resources on an assumption that can be checked first.
- Start with this overview. Use the single-page status and its source checks. Use that answer to name the immediate grave/digger codes decision before opening another branch. Player action: Follow / and apply one recommendation.
- Compare this overview. Use the single-page status and its source checks. Check how it changes the first answer instead of treating both pages as unrelated reading. Player action: Use / when the current round exposes that condition.
- Add this overview context. Use the single-page status and its source checks. Translate the relevant detail into one route, responsibility, resource, or fallback the squad can act on. Player action: Open / before committing a limited kit or irreversible purchase.
- Verify a visible redemption path. A real code feature should expose a current in-game menu, button, prompt, or developer instruction explaining where the player enters a code. Confirm it through the live interface or environment before relying on a dated number. Player action: Change only one variable during a controlled check.
- Review a live confirmation. A successful redemption should produce an unambiguous server response. A chat message, puzzle reaction, or moderation command is not equivalent. 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.
- A visible redemption path comes first. A real code feature should expose a current in-game menu, button, prompt, or developer instruction explaining where the player enters a code. If it is unknown, delay the high-risk grave/digger codes choice and gather that information.
- A developer-origin value changes the branch. Accept a claimed code only when it can be traced to the official experience description, developer board, or an announcement linked by the developer. Use the focused page or live prompt that resolves this condition before copying a route from another round.
- A stated reward and limit changes the resource plan. Check what the code grants, whether it is account-limited, and whether an expiration is stated before spending time reproducing it. Coordinate the adjustment so one player’s solution does not remove a capability the squad still needs.
- A live confirmation controls confidence. A successful redemption should produce an unambiguous server response. A chat message, puzzle reaction, or moderation command is not equivalent. 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.
- A visible redemption path. A real code feature should expose a current in-game menu, button, prompt, or developer instruction explaining where the player enters a code.
- A developer-origin value. Accept a claimed code only when it can be traced to the official experience description, developer board, or an announcement linked by the developer.
- A stated reward and limit. Check what the code grants, whether it is account-limited, and whether an expiration is stated before spending time reproducing it.
- A live confirmation. A successful redemption should produce an unambiguous server response. A chat message, puzzle reaction, or moderation command is not equivalent.
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.
- A new menu. If a future update adds a Codes, Redeem, Gifts, or Promotions control, verify it in the live interface before listing values.
- A developer announcement. Record the exact announcement date and destination. Do not copy untraceable lists from generic code aggregators.
- Command changes. The documented vote-kick and data-restoration commands may change, but they remain administrative or recovery features rather than reward codes.
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.
- Official links. Use the Trello guide to reach the developer-maintained board and confirm whether a system was added.
- Update status. Compare the live Roblox version label with dated developer patch notes before accepting a new feature claim.
- Medals. Learn how the documented progression currency is earned and spent without relying on invented codes.