Editorial Policy

Last updated: October 15, 2026. TTK Testing Wiki is an independent fan guide for the Roblox experience TTK Testing. We are not the game developer and not Roblox. This page is the rulebook for money and mid hubs — especially codes, beginner, weapons, and controls/loadouts.

Mission

Help players join a real server, learn controls, and evaluate weapons without fake “working codes” padding or studio-sounding DPS sheets we cannot verify.

Publishable claims

We prefer facts on primary surfaces we can re-check: the live Roblox experience listing (title strings such as SERVERBROWSER, maxPlayers, update wording), in-game UI a writer can see in a session, and dated public code lists when they exist. When the official surface shows no redeemable codes, codes says Active: none instead of inventing rumor strings.

What we will not invent

• Working code lists when none are verified on a check date
• Damage tables, TTK spreadsheets, or “meta” loadouts presented as studio data
• Discord invite links we have not confirmed
• Paid placement disguised as a controls tip

Evidence labels

• Official listing — Roblox experience metadata checked on a named date.
• In-session — observed in play.
• Reported — third-party claim kept contested until a primary surface agrees.
• Open — unanswered, listed as such.

Title and honesty rules

We do not put “ALL CODES WORKING” in titles when Active is none. Weapons pages may say “evaluate” instead of “best loadout” when numbers are unverified. Checked dates appear on money pages when refreshed (for example October 15, 2026).

Ads boundary

AdSense does not decide Active labels or weapon grades. See Advertising disclosure.

Corrections

Email hello@ttktesting.com with the URL, the wrong sentence, and what you checked. Related: Source methodology, About, Privacy.

Mid-hub rules (weapons, loadouts, controls)

Weapons and loadouts pages may teach evaluation methods (feel, recoil readability, situational roles) without publishing fabricated damage tables. If a community sheet floats numbers we cannot re-check on a primary surface, we label them reported or omit them. Controls pages stick to in-session UI labels.

Review cadence

Money pages aim for same-week freshness when the Roblox listing or code landscape moves. The October 15, 2026 pass kept Active: none on codes and refreshed trust substance on this page set.

Languages and mirrors

English is canonical. Mirrors that invent working codes while our codes page is empty are not our editorial voice.

Evidence depth toward the 100days bar

Sister gold-bar sites keep editorial pages near ~800–1000 words so reviewers and players can see real rules, not a stub. This October 15, 2026 expansion spells out mid-hub law, rejection samples, and cadence without inventing Discord links or DPS sheets.

Sample rejection notes

• Rejected: “working codes” title while Active is none.
• Rejected: damage table copied from an undated Discord screenshot.
• Accepted: SERVERBROWSER / maxPlayers notes from the live Roblox listing on a named date.
• Accepted: loadout evaluation methods that teach feel/recoil readability without studio DPS.

Who publishes

Only operators with deploy access change money and trust HTML. Community mail to hello@ttktesting.com proposes fixes; it does not push production alone.

Soft-404 ban

Editorial and source pages must not clone About or redirect to Home. That regression was fixed in an earlier October 15 audit deploy and must not return.

Priority when time is short

1. Codes honesty (Active: none when true).
2. Beginner and controls still match UI labels.
3. Weapons/loadouts keep evaluate language.
4. Trust pages remain real and substantive.
5. Helmet cam / optics polish.

Screenshots

Crop to UI labels. Do not publish other players’ usernames or ban-evasion tips. Watermarked “meta sheets” without a primary surface stay Reported or omitted.

Languages and canonical host

English on www.ttktesting.com is canonical. Mirrors that invent working codes while our codes page correctly shows Active: none are not our editorial voice. Locale copies, if added later, must not diverge on Active status.

Review cadence detail

Weekly Roblox listing re-checks look at title strings, maxPlayers, and whether any redeem surface appeared. Material listing changes should move the Checked date on codes and, when relevant, home hub notes. Cosmetic typos do not deserve a fake “codes audit” stamp.

Conflict of interest

AdSense authorization does not buy weapon grades. Operator play sessions are not “verified influencer drops.” If a future affiliate exists, it will be labeled on that page — never as a silent codes row.

October 25, 2026 — what this pass will and will not print

This section was added on October 25, 2026. It records the editorial line used for the pages shipped that day, and it points at the method pages that competitors fill with rankings. The October 15, 2026 policy above still stands. Where this section is more specific, it is an addition. The player-facing checklist for the same pass is how we verify. The source ladder in longer form is source methodology. Those two pages and this one are supposed to agree. A reader who finds a disagreement should mail hello@ttktesting.com with the URLs. That mail is a correction, and the contact page says what evidence it needs.

The publication test

A sentence can ship when three things are true. The surface is named. The date of the check is named. The sentence does not claim more than that surface can support. The surfaces we treat as primary are the Roblox game page for place 120189115846709, the games API for universe 10090256806, and the DevForum post dated June 2, 2026. An in-session label can support a menu name the writer saw, if the date is on the sentence. Anything else is a lead or a refusal. Leads are allowed in a notebook. They are not allowed to wear the voice of a finished fact.

We label plans as plans. Co-op PVE with squad AI, story breach missions, and team PVP are intent in the official description. Hostage rescue and Big PVP, including vehicle transport and long-range shooting, are core directions in the June 2 post. CQB PVP is a June 2 statement about what was in the game then. The October public record we rely on is a 12-player deathmatch-style test. We do not collapse those clocks into one "current mode" sentence. The planned modes page and the modes page keep the split. The roadmap page, when you are reading the site after October 25, is the comparison written for people who searched for a schedule.

Refusals that are part of the policy, not gaps

We do not publish redemption codes. The October 25 check still found none on the official description. We also do not publish an expired-code archive. A code can be called expired only after a primary surface has published it and a later primary surface has ended it. We have no such pair of sources. An empty expired list is the honest page. Filling it with strings from other wikis would launder a rumor.

We do not publish weapon damage, rate of fire, magazine size, reload time, recoil, or a time-to-kill table. The official sources we use do not print those figures. The title bracket [NEW AR15] on the October 25 name field names a newly added weapon in that string. It does not rank the weapon. We do not publish S-tier, A-tier, or a "best close-range" list. A self-test a player runs for themselves can stay a private note. The tier-list page explains why the public page refuses the grade.

We do not publish map names. The official sources we use do not give this wiki a roster. A player can write down the label their own client shows during a vote. That label does not become our canon. We do not publish attachment catalogs beyond what a source names. The June 2 post names lasers and flashlights. Transparent Optics is a setting in the official description, described as simulating both eyes open. Other parts and optics are a loadout-screen check for the player, not a list we invent. We do not publish controller or touch diagrams that go past the official PC lines: M1 fire, M2 aim, C crouch, Q and E lean, number keys to swap, P for helmetcam. Platforms named by the description are PC, mobile, Xbox, and PS5. Named is not the same thing as a drawn button chart.

We do not add screenshots we do not have. We do not draw a fake UI to illustrate a code box. We do not estimate a player count for Big PVP, a price for IC, or a date for a mode that the sources do not date. The game's award mention, the visit counts, and the player cap belong on the pages that cite the API read. They are not sprinkled into a weapon paragraph to make it look measured.

Voice, ads, and corrections

Practice advice is labeled as a method. A method tells a player how to compare two choices in one session. It does not announce a winner for every reader. "Try Transparent Optics and keep the sight picture you can read" is a method. "This optic is mandatory" is a rank, and it does not ship. The same split covers lean, crouch, weapon swap, and helmetcam. Combinations of the official keys are allowed as practice. New keys are not.

Ads do not edit this policy. The advertising disclosure states the publisher id and the refusal of paid ranks. A creative that shows a code is still not our Active list. Children may read the site. We do not collect accounts, and we do not write guides that ask a minor to hand over a login.

Corrections are best effort. We do not promise a numbered turnaround. Evidence has to point at a primary surface or a dated in-session label. If the evidence shows we said too much, we cut the sentence and leave the date visible. If the evidence is a request to invent a number, we leave the page alone and say so. The about page states who operates the guide and repeats the non-affiliation line: not Roblox Corporation, and not Sable Digital.

Checked dates on this pass use October 25, 2026, with the API read noted at 09:15 UTC+8 where the number came from that read. Older paragraphs that say October 15, 2026 stay October 15. We do not backdate a new fact into an old paragraph. A reader should be able to see which morning a claim belongs to.