TTK Testing Wiki

TTK Testing is an early Roblox tactical FPS by Sable Digital. This wiki tracks controls, codes status, weapons, the new map, modes and official source links without inventing unverified stats.

Roblox tactical FPS field manualUpdated June 29, 2026
Current buildFFA testing
CodesNone verified
MapNEW MAP title
Source ruleOfficial first
Official titleTTK Testing [NEW MAP]
CreatorSable Digital
Universe ID10090256806
Place ID120189115846709
Current public modeFFA testing while mechanics are still changing
Planned directionco-op PVE squad AI, story scenarios/missions and team PVP
CompatibilityPC, mobile, Xbox and PS5 are listed by the official description
Codes statusNo verified code system or working codes found yet

Popular answers

Questions players are likely to search first

These short answers route readers into the deeper guide pages instead of leaving them on copied-code or rumor pages.

Wiki databases

Small databases now, expandable tables later

TTK Testing does not have enough verified stats for full tables yet, so the site exposes structured trackers that can mature without fake values.

Codes answer

No verified TTK Testing codes right now

This page exists because players already search for codes. It gives a clean status answer and avoids publishing copied code values as working rewards.

Working0
Expired0
Proof ruleOfficial or in-game
Read the codes policy

Controls answer

Fire, aim, crouch, lean and weapon swap

The official Roblox description lists the core combat keys and a Transparent Optics setting for better sight visibility.

FireM1
AimM2
CrouchC
Lean left / rightQ / E
Swap weaponNumber keys
Transparent OpticsSettings option
Open controls

Watchlist

Leads we are not treating as facts yet

Keeping leads visible but clearly labeled is what lets this site grow quickly without becoming a rumor wiki.

Needs in-game proofRedeem-code UI

Roblox page does not publish codes

Check only through normal game UI or official posts.
Not verifiedDiscord invite

No official public link recorded here

Do not send players to community invites until source-linked.
Testing framework onlyWeapon ranking

Early FFA build

Collect dated clips before publishing tier positions.
WatchlistNew map callouts

Roblox title says NEW MAP

Require screenshots or repeatable route observations.

Video leads

Community videos can guide research, not replace proof

Video result patterns are useful for search intent and future screenshots, but the wiki still separates them from official mechanics.

YouTube result from current SERPFull gameplay walkthrough lead

Useful for seeing first-session questions, not a final source for mechanics.

Google video/image resultsNew map gameplay clips

Useful to identify map-search intent and screenshots that still need manual verification.

YouTube result from current SERPGun update or gunsmith videos

Useful as a watch item for weapon-page expansion without copying claims.

Community leadRoblox FPS comparison videos

Useful for wording beginner tips around leaning, optics and early-build expectations.

Source workflow

Official facts stay separate from leads

This is the trust layer that keeps the site useful for players and clean enough for search: publish what is sourced, park the rest as watch items.

01Roblox page and linked DevForum first
02API metadata for IDs and public snapshots
03Community/video leads stay separated until checked

Source boundary

Evidence cards behind the wiki

Official facts, API snapshots, developer context and search-intent leads are labeled separately so readers can see what each page depends on.