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 [SERVERBROWSER] by Sable Digital, universe ID 10090256806 and place ID 120189115846709. The public build is an 12-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.
Who writes this, and which method page to open
Last checked: October 25, 2026. This guide is written by the independent operators of ttktesting.com. It is not written by Sable Digital, not by PoptartNoahh or CanyonJack, and not by the June 2 credits (Altron, GustikSound, Aikawa, Chaotic, A. Nathan Scott). Those names belong to the game. Ours do not appear on the Roblox listing, and theirs do not operate this host. The dev team page is the closed list of credits we will print. Contact for a wrong sentence on this site is hello@ttktesting.com. That address cannot restore an account, reverse a report, or pay out IC.
Method, in order: the editorial policy says what we refuse to invent. The source methodology is the standing ladder from the October 15 pass, including Active: none as a real result. The how we verify page applies that ladder to the October 25 API read: codes, Discord, the 12-player cap, controls, and update claims. When a page on this site and a later official field disagree, the field wins and the page should be corrected in public, with the date kept. The homepage meta that said 8-player was that kind of error. The API maxPlayers value is 12. The correction changed the number. It did not invent a new sentence around it.
The October 25 pass added guides rather than quietly rewriting older titles and H1s. Older pages still quote TTK Testing [SERVERBROWSER] because that was the October 15 title. The later name "TTK Testing 🎃 [NEW AR15]" is quoted on game stats, the Halloween marker, and AR15. Both quotations stay, with dates. That is the method. A single undated title would be easier and less true.
Use official links when you only need the Roblox page and the DevForum thread. Use the glossary when a word on an older article is doing too much work. Use the FAQ when you want the short answer before the long one. Advertising does not choose these labels. The ads disclosure stays the boundary. Nothing in the October 25 numbers — visits, favorites, or the playing sample — was gathered for an ad pitch. They are the public Roblox record, cited so players can reload them.
What the October 25 pass refused to add
Readers can judge the method by the absences. No weapon damage, fire rate, or recoil. No tier letters. No map names and no spawn tables. No redeemable code and no fake expired column. No Discord invite. No controller or touch chart presented as official. No expansion of the letters IC. No Halloween shop, mode, or end date. No headcount for Big PVP beyond the experience cap of 12. No claim that CQB PVP, FFA, and Ground War are the same button. No staff biography beyond the listing's lead devs and the June 2 credits. Those refusals are the product. A longer page that broke one of them would be a worse page.
The guides that explain each refusal are linked from the homepage All guides list and from the footer on each article. If you are checking our work, reload place 120189115846709 and the universe API record, then open the June 2 DevForum post. You should be able to find every positive claim on those surfaces or on an older dated page of this wiki. If you cannot, the sentence should change. That is the correction standard already stated above, applied to this pass in particular.
How a reader can audit one page
Pick a factual sentence. Find the date next to it. Open the surface that date points at: the Roblox game page, the games API for universe 10090256806, or the June 2 DevForum thread. If the sentence is editorial, it should say so, the way the FFA and training pages label habits. If you cannot find the surface, mail hello@ttktesting.com with the URL and the sentence. Do not send a replacement number for damage or a code to try. The editorial policy and how we verify are the two method pages. Source methodology is the October 15 ladder they sit on. The dev team page is who we are not.
The independence line, in one place
We can be wrong, and the correction path is public. We cannot be the developer. Place 120189115846709 is theirs. The host ttktesting.com is ours. Ads on this site do not buy a code row or a weapon grade, which the editorial policy already says and the October 25 pass did not relax. If you want the shortest proof, open game stats and reload the API. The numbers there are theirs. The decision to print no tier list beside those numbers is ours. Both should stay visible.
Two dated titles, one place ID
Quoting both TTK Testing [SERVERBROWSER] and "TTK Testing 🎃 [NEW AR15]" is not indecision. The first is the October 15, 2026 listing pass. The second is the October 25 API name. Place 120189115846709 ties them. A future title gets a third quotation and a new date. It does not erase the earlier ones. That habit is the whole editorial method in miniature, and it is why older H1s on this site were left in place while new pages carried the later string.
Dates stay on the sentence they belong to
October 15, 2026 marks our listing pass. October 25, 2026 marks the API read. June 2, 2026 marks the DevForum post. Moving a fact onto a cleaner date would make the site easier to skim and worse to audit. The verification page is where that rule is written for codes, the cap, and title strings. About is where we admit the rule applies to us too.
Who runs this guide, why it exists, and how a correction moves
This section was added on October 25, 2026 so the operator questions sit in one place. TTK Testing Wiki is an independent fan publication at www.ttktesting.com. The byline on every page is the publication, not a Sable Digital employee and not a Roblox staff account. The people who build the experience are named on the dev team page only because the official listing and the June 2, 2026 DevForum post name them. Those credits are not a masthead for this website. Mail for this website goes to hello@ttktesting.com. Mail to that address does not reach the studio.
We are not affiliated with Roblox Corporation. We are not affiliated with Sable Digital. We do not speak for either of them. We do not sell items, we do not run the official Discord, and we do not hold a private patch channel. A sentence on this host is true only when a public source supports it. The game's name, the place id, and the creator name are used so a reader can find the right experience. Using a name to point at a public page is not a claim of partnership.
Why the site exists
Players search for controls, codes, modes, and weapon ranks. Much of what ranks highly on those searches is a copied list: a code that was never on the Roblox description, a damage table the studio did not publish, a map atlas made of names we cannot tie to a source, or a letter grade. This guide exists to answer the same searches with a smaller set of sentences. If the official surface supports the sentence, we write it and date it. If the official surface is silent, we write the silence. Active codes: none is an answer. A missing damage table is an answer. A plan that is still a plan is an answer.
The practical reason is the same. A new player can learn the confirmed PC inputs, see that servers are a 12-player public test, and avoid typing a string from a look-alike site. A returning player can see which mode names are live descriptions and which names are still intent. We would rather publish a short page that holds up than a long page that invents the rest.
How we verify
Verification is a ladder, not a vibe. The highest surfaces are the official Roblox game page for place 120189115846709, the official games API record for universe 10090256806, and the DevForum post from June 2, 2026. An in-session label can confirm a control or a menu a writer can see, and it has to carry a date. A video, a comment, a fan ranking, or an email is a lead. A lead is a reason to re-check. It is not a source we promote into the Active column or into a tier row.
The player-facing write-up of the October 25, 2026 pass is how we verify. The standing rules are the editorial policy and the source methodology. Those three pages link to each other on purpose. If they ever disagree, the disagreement is a bug, and the fix is a dated correction, not a quiet blend. The methodology page records how often we re-check. We do not pretend a fixed crawl interval that we do not run.
What we will not verify into existence: a redemption code, an expired-code archive, a weapon statistic, a best loadout, a map name, a controller diagram the official description does not draw, or a release date for co-op, hostage rescue, or Big PVP. The new method pages under builds, attachments, advanced controls, expired codes, and the roadmap say how to test and how to read plans. They do not fill those gaps with fiction.
How a correction moves
Anyone can ask for a correction. The request has to carry evidence. Send the exact URL, quote the sentence you think is wrong, and point at what the Roblox listing, the API record, the DevForum post, or your dated in-session view actually shows. A screenshot of another wiki is not evidence about the game. A memory of a code, with no official sentence, is not evidence. Time zone helps when the dispute is about a checked stamp. Asia/Shanghai is the zone we already use when a stamp is the issue. English is the language of the pages.
We read correction mail on a best-effort basis. We do not promise that a reply will land inside a stated number of hours or days. A successful correction looks like a changed sentence with the date still honest, or a note that the evidence was not enough to move the page. Both outcomes are real. We will not "correct" a page by adding a damage number, a map roster, or a code string that the evidence does not contain. If the evidence shows we over-claimed, we cut the claim. Cutting is the correction we prefer when the alternative is a guess.
Some mail is out of scope even when it is polite. We do not unban players, refund purchases, restore wiped XP or IC, or recover accounts. Those requests need Roblox or the experience creators. The contact page lists the categories the inbox does accept. The official links page is where a reader confirms they are looking at Sable Digital's experience before they decide our sentence is the one that failed.
If you are checking us rather than correcting us, open the game page and the API record yourself, then open the June 2 DevForum post. Every positive claim on a guide should be findable on one of those surfaces or on an older dated paragraph of this wiki. If you cannot find it, that is the correction. Write in. That standard applies to this about page as much as it applies to a codes page.