The documented stat tracker is a manual Google Sheets template. Copy it to your own account, enter observations deliberately, and do not expect it to read or update Roblox data automatically.
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.
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.
- Manual template. The tracker is provided as a spreadsheet format for player-maintained records rather than an in-game progression screen.
- Copy first. Make an owned copy before editing so the template remains intact and your records stay under the account you control.
- No automatic sync. The official description says information must be filled individually. It does not automatically import kills, Medals, rank hours, or match results.
- Record source. For each entry, note whether the value came from the live menu, end-of-round screen, manual count, or a dated developer card.
- Version column. Add the observed date and visible version clue so a balance change does not make an old value look current.
- Separate systems. Keep playtime rank, Medal currency, cosmetic ownership, and weapon-specific kills in distinct fields to avoid false totals.
- Privacy. Do not place passwords, cookies, recovery information, private Discord content, or unnecessary personal identifiers in a shared sheet.
- Error correction. When a row conflicts with the game, correct the manual record; the spreadsheet does not override the current server.
A practical way to use this information
Use this sequence when grave/digger stat tracker matters in a live round. It starts with information the interface can confirm and leaves version-sensitive experiments until they are safe.
- Confirm manual template. The tracker is provided as a spreadsheet format for player-maintained records rather than an in-game progression screen. Locate the corresponding live prompt, objective state, class description, item panel, or environment clue before committing the grave/digger stat tracker plan. Player action: State what the current server confirms about manual template.
- Connect copy first to no automatic sync. Make an owned copy before editing so the template remains intact and your records stay under the account you control. Then account for this related rule: The official description says information must be filled individually. It does not automatically import kills, Medals, rank hours, or match results. 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 record source safely. For each entry, note whether the value came from the live menu, end-of-round screen, manual count, or a dated developer card. 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 record source.
- Build around version column. Add the observed date and visible version clue so a balance change does not make an old value look current. 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 version column changes the plan.
- Review privacy and error correction. Do not place passwords, cookies, recovery information, private Discord content, or unnecessary personal identifiers in a shared sheet. Compare the round result with the final caution: When a row conflicts with the game, correct the manual record; the spreadsheet does not override the current server. 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 stat tracker rules to the round in front of you.
- Manual template or Copy first. The tracker is provided as a spreadsheet format for player-maintained records rather than an in-game progression screen. Compare that with copy first: Make an owned copy before editing so the template remains intact and your records stay under the account you control. Prioritize the condition tied most directly to the active objective and preserve a fallback for the other.
- No automatic sync changes the setup. The official description says information must be filled individually. It does not automatically import kills, Medals, rank hours, or match results. If that condition is absent, unavailable, or already covered by a teammate, redirect the grave/digger stat tracker plan toward record source instead.
- Version column changes the timing. Add the observed date and visible version clue so a balance change does not make an old value look current. Delay the action when the squad cannot exploit the resulting opening, resource, information, or position.
- Separate systems sets the limit. Keep playtime rank, Medal currency, cosmetic ownership, and weapon-specific kills in distinct fields to avoid false totals. Keep error correction in view as well: When a row conflicts with the game, correct the manual record; the spreadsheet does not override the current server. 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 copy first. Make an owned copy before editing so the template remains intact and your records stay under the account you control. Correct the mistake by checking that condition before attempting manual template or committing a limited resource.
- Overgeneralizing record source. For each entry, note whether the value came from the live menu, end-of-round screen, manual count, or a dated developer card. Correct this by naming the mode, map, class, item, target, and server state in which the behavior was actually observed.
- Forgetting separate systems. Keep playtime rank, Medal currency, cosmetic ownership, and weapon-specific kills in distinct fields to avoid false totals. Correct this by assigning a teammate, route, fallback, or verification check to cover the limitation before contact.
- Freezing error correction in time. When a row conflicts with the game, correct the manual record; the spreadsheet does not override the current server. 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 Stat Tracker, join through the official Roblox page and first locate evidence for manual template, record source, and error correction. 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.
- Progression hub. Separate time rank, currency, appearance, kills, and manual records.
- Perks. Review one current Medal purchase category.
- Updates. Check whether a documented progression rule was revised.