Which TTK Testing links are official?
The official Roblox identity is the Sable Digital experience titled TTK Testing [SERVERBROWSER], universe ID 10090256806 and place ID 120189115846709. The developer discussion is useful for the team's stated direction. No official Discord invite is currently linked from the official Roblox surface.
Use sources in this order
Not every source answers the same question. The live Roblox surface is best for what players can identify and access now. The developer discussion is best for understanding planned modes and the broader direction described by the developers.
| Source | Use it for | Do not assume |
|---|---|---|
| Official Roblox listing | Title, creator, IDs, public test description, controls, platforms | That every planned feature is live |
| Developer discussion | Planned Survival, Missions, Quick Play, and Ground War concepts | A release date or current availability |
| Community posts and videos | Finding questions or possible leads | Official ownership, codes, or final mechanics |
Confirm you have the right game
Search results can shorten titles or surface reposts. Check the creator and numeric IDs before treating a page as the official game. The current official title includes [SERVERBROWSER], so an older plain-title reference may still point to the same universe, but the IDs settle the question.
- Confirm the creator name is Sable Digital.
- Match universe ID 10090256806.
- Match place ID 120189115846709.
- Read the current description before relying on a cached search snippet.
A simple rule for codes, Discord, and updates
A claim becomes dependable when the official source supports the same claim. That is why this wiki can state the controls and current FFA format clearly, while leaving codes and Discord unverified.
The same distinction protects update coverage. Co-op PVE, squad AI, story scenarios or missions, and team PVP are named plans. Survival, Missions, Quick Play, and Ground War are described mode directions. They should remain in the planned column until the live game and listing move them into the current one.
- Current fact: supported by the live official description.
- Plan: described by an official source but not confirmed as live.
- Lead: useful for checking, but not yet official evidence.
- Unknown: leave it unanswered rather than filling the gap.
What each official link is for
This section was added on October 25, 2026. The short table above still stands. Below, each destination we treat as official gets a job description: what you open it for, what a careful reader copies down, and what the link is not allowed to prove. Fan pages, including this one, are not on the official list. We are a guide that points at the official list. A site that calls itself official still has to survive the checks below.
The Roblox game page
The game page is roblox.com/games/120189115846709/TTK-Testing. Open it to confirm you have Sable Digital's experience. The place id 120189115846709 is the check that matters when a search result shortens the title. The creator line should read Sable Digital. The universe id published for this experience is 10090256806. Use the page for the current title string, the public description, the platform line, and the control lines the description actually prints: fire on M1, aim on M2, crouch on C, lean on Q and E, weapon swap on the number keys, helmetcam on P, and Transparent Optics in settings.
Use it also for the sentences the description chooses to put in public: the in-game report system in testing, the note that a 3D replay can be used to check cheating, the warning that the XP/IC economy may be wiped, the update cadence, and the stated intent to build co-op PVE with squad AI, story breach missions, and team PVP. Those intent lines are plans. The game page is the right source for them. It is not a source for a release calendar, because the page does not give those features a date.
Do not use the game page as proof of a redemption code unless the description itself prints the string, the reward, and how to redeem it. Do not use a comment under a video, or a "codes" module on a fan site, as if it were this page. On the October 25, 2026 read, the description still did not publish a code. The October 15 read on this wiki did not either. Two empty reads are the current official position until the page changes.
The games API record
The public games endpoint we use is games.roblox.com/v1/games?universeIds=10090256806. Open it when you need fields the prose page can obscure: the name, maxPlayers, created, updated, visits, favorites, playing, and genre, as Roblox returns them for universe 10090256806. Our game stats page freezes one read, taken at 09:15 UTC+8 on October 25, 2026. Your read is a new observation. If name or updated disagrees with our table, your later read wins, and the right next step is a correction to us with the time you looked.
The API record is official data about the experience's catalog entry. It is not a weapon spreadsheet. It does not list attachments, maps, or codes. A playing count is a sample at the moment of the request. It is not a promise about the next hour, and it is not the population of one server. maxPlayers on that read was 12. Use the field. Do not replace it with a number from a thumbnail or from an older caption.
The June 2, 2026 DevForum post
The developer post is TTK: Our very early tactical FPS on devforum.roblox.com, dated June 2, 2026. Open it for the team's own wording on that day: PVP with multiple modes, character and weapon customization, callouts, stances, lasers, flashlights, leaning, door kicking, and lockpicking. Open it for the design line that the game is meant to be easy to pick up and lightly realistic, not a hardcore milsim. Open it for the core mode names in that post: CQB PVP described as in the game then, co-op missions and hostage rescues, and Big PVP with vehicle transport and long-range shooting. Open it for the credits printed there.
Do not open it as a live patch note for October. A June sentence stays a June sentence. Replies under the thread are not the original post. A reply that offers a code, a Discord invite, or a damage number is a lead, even when it sits on the official forum domain. The post we cite is the developer write-up, not every later comment. The planned modes page and the roadmap page repeat this dating rule so the link cannot be stretched.
What is deliberately not on this list
We do not have an official Discord invite to publish. The Roblox surface we checked does not link one. A busy server with the game's name is not promoted onto this page by popularity. We do not link code blogs, "working codes" videos, or tier-list wikis as official sources. They can be leads. Leads live in the method pages, not in the official column. We do not link a Roblox profile just because it shares a developer name, unless the game page or the DevForum post is what established the connection. When the game page names Sable Digital and the lead developers, that naming is the connection. A search result is not a second official site.
Our own URLs, including www.ttktesting.com, are documentation. They are not official game links. If someone tells you this wiki "is the devs," they are wrong. The about page states the non-affiliation in full: not Roblox Corporation, and not Sable Digital.
How to spot a look-alike, a fake code site, or a fake invite
Start with the host name before you read the headline. The game page should be on roblox.com, on the path above, with place id 120189115846709. The API host we use is games.roblox.com. The developer post should be on devforum.roblox.com, in the thread id above. A domain that merely contains the letters "roblox", or that adds a gift, code, or free-item word to a look-alike host, is not those pages. A shortened link that hides the host is a reason to stop, expand the link somewhere safe, and check the host again. Bookmark the real game page once. Use the bookmark the next time a search result looks slightly off.
Confirm the creator. Sable Digital is the creator on the official experience. A page that cannot show that name and the place id is not a source of codes, bans, or refunds. Confirm the title only after the id matches. Titles move. The October 15 writing on this wiki recorded TTK Testing [SERVERBROWSER]. The October 25 API read recorded a name field with a pumpkin mark and [NEW AR15]. Both observations can be this same place id at different hours. An id match survives a title change. A title match without an id does not.
Fake code pages share a shape. They list many strings, they name generic rewards, they show a countdown, and they never quote a sentence from the Sable Digital description. They may tell you to complete a human-check, to disable an ad blocker, to log in, or to "verify" a Roblox account on a site that is not roblox.com. They may mix codes from unrelated experiences onto a page that uses this game's name. None of that is an official publication. Because we have no verified code at all, any page that urges you to type a specific string is ahead of the official record. Treat the string as untrusted. Do not pay. Do not send a password. Do not install a "code unlocker."
A fake expired-code page is the same problem one column over. Expired is a status we can print only after a code was official and then ended. A site that shows a long expired table, while the Roblox description has never shown a code, has invented the history. Our expired-codes page explains that test. Use it when a friend sends you a "these just expired" list.
Fake support is a third shape. A direct message that offers to restore IC, to lift a ban, or to hand over a staff code is not Sable Digital and not this wiki. We cannot do those things, and we say so on the contact page. The studio's public writing is the game page and the DevForum post. Anything that asks you to move the conversation onto a random chat handle, a form that wants your cookie, or a payment for a refund is outside both. Leave, and if you already shared a secret, rotate it on Roblox.
When you are unsure, do the checks in order. Host name. Place id 120189115846709. Creator Sable Digital. Universe 10090256806 if you are on the API record. Then read the description before you trust a snippet. Then, and only then, decide whether our guide agrees. If the official page and this guide disagree, the official page wins, and we want the correction. The method for that mail is on the contact page. The grade that mail has to meet is on source methodology and how we verify.
Last checked for the destinations named in this section: October 25, 2026. Re-open the three URLs when a decision depends on them. A bookmark from an older month can still be the right place id and the wrong assumption about codes or modes.