What is this site for?
Use it when you need the controls, current code or Discord status, an explanation of planned modes, or a reliable way to confirm that you found the real Sable Digital experience. It is not an official Sable Digital publication.
How answers are built
The site begins with what a player is trying to do, not with a long history of the project. A controls question should lead to the controls. A codes question should say immediately that no verified codes are available. A Discord question should not bury the missing official invite beneath community links.
Facts about the current game come from the official Roblox surface. Planned mode detail comes from the developer discussion. When those sources describe different time frames, the wording preserves that difference.
- Identify the exact player question.
- Check the official Sable Digital Roblox identity first.
- Use developer discussion only for context it actually provides.
- Label planned features as plans.
- Remove claims that cannot be traced to the permitted sources.
What the wiki can state clearly
The current official identity is TTK Testing [MAP VOTING] by Sable Digital, universe ID 10090256806 and place ID 120189115846709. The public build is an eight-player FFA test with a compatibility focus that names PC, mobile, Xbox, and PS5.
The confirmed controls are M1 to fire, M2 to aim, C to crouch, Q and E to lean, number keys to swap weapons, and P for helmetcam. Transparent Optics is a named setting for sight visibility.
The official direction includes planned co-op PVE with squad AI, story scenarios or missions, and team PVP. The developer discussion describes Survival, Missions, Quick Play, and Ground War. None of that wording should be shortened into a claim that all four modes are live.
| Type | Example | Editorial treatment |
|---|---|---|
| Current | Public FFA test and confirmed controls | State directly |
| Planned | Co-op PVE, story missions, team PVP | Keep future-facing language |
| Unverified | Codes or an official Discord invite | Say that no official confirmation was found |
How to judge a correction
A useful correction needs more than a confident message. It should identify the affected page, state what is wrong, and point to the official surface that supports the replacement. Screenshots can help locate a change, but the current public source remains the deciding reference when it is available.
This standard is intentionally simple. It lets the wiki change quickly when the game changes without turning rumors into facts. It also means an honest short answer can be better than a long page filled with copied claims.
- Name the page and the exact sentence that needs attention.
- Provide the official source or enough detail to locate it.
- Explain whether the change is live, planned, or still uncertain.
- Do not submit account credentials, private messages, or unsafe invite links.
Independent, with a narrow purpose
This wiki is not affiliated with Roblox, Sable Digital, or the TTK Testing developers. Independence does not mean guessing. It means the site can organize public information around player needs while keeping ownership and source labels clear.
The best next step depends on the question in front of you: open the codes page for reward claims, the Discord page for invite status, the updates page for live-versus-planned features, or the official links page when you need to verify the source itself.