The official sources checked do not present one perfectly aligned version label. The Roblox experience description displays V1.38, while the developer Trello contains a later-numbered v1.39 patch card dated February 15, 2026. This page preserves that disagreement instead of declaring an unsupported current build.
Version labels can disagree between the Roblox description, developer update cards, and community recordings. A reliable status page keeps each dated claim attached to its source.
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 update tracker. It records the public Roblox listing and dated developer notes, then explains how to test visible changes in the live experience. It does not create child pages for every patch, repeat an unverified community version number, or turn an “upcoming” card into a release schedule. A higher patch number on a developer board can be newer documentation, a staged build, or a label the public description has not adopted; the sources alone do not establish which label every current server displays.
A reliable workflow for this section
The following routine keeps grave/digger updates 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 updates 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 roblox description label. The official experience description showed V1.38 when checked on September 1, 2026. Record it as listing evidence, not proof of every server mechanic. 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 live confirmation. Check the current objective, command behavior, audio, map geometry, menus, and item descriptions before calling a noted change active everywhere. 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.
- Roblox description label comes first. The official experience description showed V1.38 when checked on September 1, 2026. Record it as listing evidence, not proof of every server mechanic. If it is unknown, delay the high-risk grave/digger updates choice and gather that information.
- Developer patch card changes the branch. The official Trello includes a v1.39 patch card dated February 15, 2026. Keep the number, date, and source together. Use the focused page or live prompt that resolves this condition before copying a route from another round.
- Visible changes changes the resource plan. That patch card documents an Estate rework and optimization, public vote-kick command and keybind work, music, and a Shock Trooper pickup jingle. Coordinate the adjustment so one player’s solution does not remove a capability the squad still needs.
- Live confirmation controls confidence. Check the current objective, command behavior, audio, map geometry, menus, and item descriptions before calling a noted change active everywhere. 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.
- Roblox description label. The official experience description showed V1.38 when checked on September 1, 2026. Record it as listing evidence, not proof of every server mechanic.
- Developer patch card. The official Trello includes a v1.39 patch card dated February 15, 2026. Keep the number, date, and source together.
- Visible changes. That patch card documents an Estate rework and optimization, public vote-kick command and keybind work, music, and a Shock Trooper pickup jingle.
- Live confirmation. Check the current objective, command behavior, audio, map geometry, menus, and item descriptions before calling a noted change active everywhere.
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.
- Listing text. The developer may update the Roblox description independently of the Trello board, so the displayed public version can lag or use a different convention.
- Patch-card status. A dated card can document released, staged, or historical work. Use its wording and visible server behavior rather than the number alone.
- Community recordings. A video title or community message can provide a test lead but is not used here as the authority for the current public version.
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.
- Trello guide. Read board lists, dates, current manuals, historical reworks, and future-looking cards carefully.
- Official Discord links. Find original announcements while keeping community statements distinct from developer evidence.
- Beginner guide. Verify visible mechanics through a controlled first-round workflow.