The short answer
TTK Testing Wiki verifies a claim by naming the surface, the check date, and the label that surface can support. The highest surfaces are the official Roblox game page, the official Roblox games API for universe 10090256806, and the June 2, 2026 DevForum post by the developers. In-session interface labels can confirm a control or a menu a writer can see. Undated videos, copied code lists, and unofficial Discord invites stay leads until a higher surface agrees. When the higher surface is silent, the published result is an honest empty state, not a guessed fill.
This page is the player-facing version of that rule. The standing policy pages are the editorial policy and the source methodology. Those pages still describe the October 15, 2026 pass. This page adds the October 25, 2026 checks for the player cap, the title string, codes, Discord, controls, and update claims, and it links the new topic pages that use the same ladder.
Source grades
Grades stop a strong sentence from being built out of a weak link. A claim can use only the grade it actually has. Mixing grades without a label is how an 8-player caption survived next to a 12-player body.
| Grade | Surfaces | What it may support | What it may not support |
|---|---|---|---|
| Primary, live | Roblox game page for place 120189115846709. Games API for universe 10090256806. | Title string, creator, ids, maxPlayers, created, updated, visits, favorites, a playing sample, genre, description text. | Weapon damage, map names, a code string the description does not contain. |
| Primary, dated post | DevForum thread TTK: Our very early tactical FPS, June 2, 2026. | What the team said was in the game then, and what they named as core direction. Team credits in that post. | A claim that June 2 wording is still the live menu on October 25, unless a later primary surface agrees. |
| In-session | A writer looking at the current client, with a date. | A visible label: a key prompt, a settings name, a code field if one is on screen. | Hidden formulas, other players' inventories, anything off-screen. |
| Lead | Video, comment, fan wiki, poll, mail to hello@ttktesting.com. | A reason to re-check a primary surface. | An Active code, an official Discord, a tier, a map canon. |
| Refuse | No surface, or a surface about a different place ID. | Nothing. | Everything. The sentence stays unpublished. |
The October 15 methodology already used a shorter ladder: live listing, in-session UI, then public code lists as cross-check only. This October 25 page does not replace that ladder. It names the API read as part of the live listing grade, because that is how maxPlayers, visits, favorites, created, and updated were confirmed, and it names the DevForum post as its own dated grade so planned modes are not smuggled in as current features.
Labels we actually print
Official listing means the Roblox page or the API field, with a date. In-session means someone saw the label in the client. Reported means a third party said it and a primary surface has not agreed. Open means we do not know. Active: none means we checked the code surfaces and found no verified string. Plan means an official source described it as intent or as a core direction without a later live confirmation. Current means the live description or the current client exposes it.
The check, claim by claim
Codes
Open the official description and look for a published string. Open the game only far enough to see whether a redemption field exists. If the description has no string and the client has no field, the result is Active: none. Do not promote a string from a compilation site to fill the empty box. Do not mark a string expired unless a primary surface once listed it. The codes page holds that empty result. The how to redeem page explains how to recognize a real path if a field appears later. Checked October 25, 2026: still no verified active code.
- Confirm place ID 120189115846709 so the description you read is this experience.
- Search the description for a code, a reward, and an expiry. All three must come from that surface.
- If you are in game, look for a redemption field. Absence is a finding. Write it down.
- If a video shows a string, leave it as a lead. It enters Active only after step 2 or a visible field accepts it on a dated check.
- Stamp the date. The October 15 page and the October 25 re-check can both say none. That is two checks, not a weaker claim.
Discord
An official invite is one the Roblox listing links, or one that a clearly official Sable Digital surface links. A busy server with the game's name is not that link. The Discord page records that no official invite was on the Roblox surface. October 25, 2026 did not add one in the API description fields we used. Until it does, we do not print an invite URL.
Controls
The official description lists PC inputs: Fire M1, Aim M2, Crouch C, Lean Q/E, weapon swap on the number keys. Helmetcam is P. Transparent Optics is a setting described as simulating both eyes open. Those lines are primary. Mobile and console are named as platforms, not as button charts. The controls page keeps the PC list. The mobile and console pages say what is confirmed and what you must read off your own client. We do not invent a bumper layout to look complete.
Player cap
Read maxPlayers on the games API, and do not trust a prose caption that disagrees with it. On October 25, 2026 the field was 12. A sample of 10 public servers each showed a 12-player maximum. An older meta description on the homepage said 8-player. That caption was wrong. It has been corrected to 12-player without rewriting the rest of the sentence. The FAQ table had a leftover "Up to eight" cell beside an introduction that already said 12. Later passes must not reintroduce 8. The stats page is the table. The server browser page explains what the cap means in a match.
Updates and the title string
Record the updated field and the name field together, with the clock time. On this check, updated was 2026-10-23 UTC and the name was "TTK Testing 🎃 [NEW AR15]". The pumpkin is not an event guide. [NEW AR15] is not a damage row. Weekly or daily update wording in the description is cadence, not a changelog of weapons. The DevForum line that a missed week usually means a large update is a June 2 statement. Put it in the changelog with that date. Do not merge it into the October 23 field. The updates page carries the dated rows. The Halloween page refuses invented event content.
Modes
Split three clocks. The live October description, as captured on the October 15 pass and not contradicted by the genre labels on October 25, presents a public deathmatch-style test and lists co-op PVE, squad AI, story breach missions, and team PVP as intent. The June 2 post says that, at that time, the game had PVP multi-mode and customization, names CQB PVP as in-game, and names co-op missions and hostage rescues plus Big PVP as core modes. Survival, Missions, Quick Play, and Ground War are the named directions already on the modes page. A verifier writes the clock next to the mode. "In the game on June 2" is not "in the menu on October 25" unless you looked.
Worked rejects from this check
These are the kinds of sentences this ladder throws out. They are illustrations of the rule, not a gallery of real codes or real map names. No example below is a redeemable string.
- Reject: "Working codes for the Halloween update." The October 25 description check did not publish a code, and the pumpkin in the title is not a code drop. Inventing a festive string would manufacture both an event and a reward.
- Reject: "AR15 is S tier after the October 23 update." The updated field and the [NEW AR15] label do not contain a grade. See tier lists.
- Reject: "Xbox fire is the right trigger." PS5 and Xbox are supported platforms. The published input list is PC. A controller guess is a lead at best, and we are not printing it as the map.
- Reject: "The official Discord is this invite." No invite was on the official Roblox surface. Activity in a fan server does not promote it.
- Reject: a damage table copied from an undated screenshot. The editorial policy already names that reject. October 25 did not create an exception.
A negative result is publishable. Active: none, no official Discord, no weapon table, and no map roster are findings. They are more useful than a page that looks complete and cannot be re-checked. Another editor should be able to open the game page, open the universe endpoint, and agree with the label on the same day.
Common mistakes
- Using one official sentence to prove three claims. "Weekly updates" proves cadence. It does not prove the contents of this week's patch.
- Letting a newer fan page outrank an older official post without a date. June 2 can still be the best source for team credits. It is a poor source for today's title string. Pick the surface that matches the question.
- Calling a lead "confirmed" because two fan pages agree. Agreement among pages that copy each other is one source.
- Hiding the check date because the answer is empty. The date is what makes "none" believable next month.
- Smoothing the 8-versus-12 contradiction by splitting the difference. Caps are not averaged. The field said 12.
FAQ
How is this different from the source methodology page?
The source methodology is the standing ladder, last expanded on October 15, 2026, with Active: none as a first-class result. This page applies that ladder to the October 25 API read and points at the topic pages. If the two ever disagree, the later dated primary surface wins, and both pages should be updated rather than quietly diverging.
Do you redeem codes in the game?
We do not need a private redemption to classify a string as unverified. If the official description does not publish it, it is not Active. A later in-session check can confirm a field. It still cannot invent the string that field expects.
Can players help verify?
Yes, as leads. Mail hello@ttktesting.com with the page URL, the sentence you think is wrong, the time you looked, and the official URL. Do not send account cookies, passwords, or an invite you cannot tie to Sable Digital.
Why keep the October 15 SERVERBROWSER wording at all?
Because it was the title observed on that date for this place ID. Deleting it would pretend we only ever saw one string. Dating both strings is the verification, not a contradiction we are embarrassed about.
What did the October 25 pass refuse to add?
Weapon numbers, tier letters, redeemable codes, a Discord invite, map names, controller button charts presented as official, Halloween event rewards, and any rank of players or guns. The new pages describe methods and sourced facts instead.
Sources
Last checked: October 25, 2026.
- Roblox game page, place 120189115846709: official listing.
- Roblox games API, universe 10090256806, read 09:15 UTC+8 on October 25, 2026: official games record.
- DevForum, June 2, 2026: TTK: Our very early tactical FPS.
- Editorial policy and source methodology.