Grave/Digger Progression

Grave/Digger progression mixes time markers, currency purchases, class appearance, weapon-specific kill milestones, and a manual record sheet. Keep those systems separate: rank does not automatically grant combat power, and the tracker does not sync itself.

Progress in Grave/Digger includes time-based titles, Medals, class-by-class cosmetics, weapon-specific kill skins, and an optional manual spreadsheet. These systems do not all grant combat power.

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.

• Ranks. Faction title ladders based on shared playtime, with no documented combat or cosmetic reward.
• Medals. The documented currency, current XP conversion, earning activities, costs, and safe spending checks.
• Cosmetics. Class-specific appearance, faction sharing, Officer headwear exception, voice and accessory choices.
• Weapon skins. Weapon-specific kill milestones, current tier thresholds, restrictions, and verification.
• Stat tracker. How to copy and maintain the optional community spreadsheet without expecting automatic sync.

A reliable workflow for this section

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

1. Start with Ranks. Faction title ladders based on shared playtime, with no documented combat or cosmetic reward. Use that answer to name the immediate grave/digger progression decision before opening another branch. Player action: Follow /progression/ranks/ and apply one recommendation.
2. Compare Medals. The documented currency, current XP conversion, earning activities, costs, and safe spending checks. Check how it changes the first answer instead of treating both pages as unrelated reading. Player action: Use /progression/medals/ when the current round exposes that condition.
3. Add Cosmetics context. Class-specific appearance, faction sharing, Officer headwear exception, voice and accessory choices. Translate the relevant detail into one route, responsibility, resource, or fallback the squad can act on. Player action: Open /progression/cosmetics/ before committing a limited kit or irreversible purchase.
4. Verify system type. Decide whether the value is time rank, Medal currency, appearance ownership, a weapon kill milestone, or a manual spreadsheet entry. 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 account record. Keep manual records clearly separate from data the Roblox experience actually stores and displays. 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.

• System type comes first. Decide whether the value is time rank, Medal currency, appearance ownership, a weapon kill milestone, or a manual spreadsheet entry. If it is unknown, delay the high-risk grave/digger progression choice and gather that information.
• Current requirement changes the branch. Read the live purchase or unlock description before grinding toward a dated threshold. Use the focused page or live prompt that resolves this condition before copying a route from another round.
• Gameplay effect changes the resource plan. Do not infer power from a title or cosmetic when the documentation says it is visual or has no benefit. Coordinate the adjustment so one player’s solution does not remove a capability the squad still needs.
• Account record controls confidence. Keep manual records clearly separate from data the Roblox experience actually stores and displays. 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.

• System type. Decide whether the value is time rank, Medal currency, appearance ownership, a weapon kill milestone, or a manual spreadsheet entry.
• Current requirement. Read the live purchase or unlock description before grinding toward a dated threshold.
• Gameplay effect. Do not infer power from a title or cosmetic when the documentation says it is visual or has no benefit.
• Account record. Keep manual records clearly separate from data the Roblox experience actually stores and displays.

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.

• Perks. Review one current use for Medal currency.
• Weapons. Identify the base weapon before tracking its skin milestone.
• Updates. Check whether a progression value changed in a dated patch.

Sources checked

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