The short answer
TTK Testing's public record and its plans use different clocks, and this page keeps the clocks apart. What you can queue is the live column: a deathmatch-style Roblox test by Sable Digital, 12-player cap, confirmed PC controls, named platforms, helmetcam, Transparent Optics, a report tool described as in testing, and an XP/IC economy the description says may be wiped. What you should not queue yet is the plan column: co-op PVE with squad AI, story breach missions, and team PVP from the official description, plus hostage rescue and Big PVP with vehicle transport and long-range shooting from the June 2, 2026 DevForum post.
There is no release order and no ship date in those sources. A roadmap here is a comparison, not a calendar. The longer split between the June wording and the mode names already on this wiki is the planned modes page. Last checked: October 25, 2026.
What is live in the sources we can re-read
Live means the official Roblox description or the games API record supports it as a property of the current experience, or the client you are in actually offers the button. On October 25, 2026 at 09:15 UTC+8 the API record for universe 10090256806 still pointed at place 120189115846709, creator side Sable Digital on the game page, genre Shooter / Deathmatch Shooter, and maxPlayers 12. The name field that morning was "TTK Testing 🎃 [NEW AR15]". The updated field was 2026-10-23 UTC. Created was 2026-04-27. Those fields are catalog facts. They are not a patch essay. The game stats page shows how to reload them yourself.
The description, as this wiki's October checks record it, supports a public tactical test rather than a finished mode lineup. It names PC, mobile, Xbox, and PS5. It names the PC inputs: M1 fire, M2 aim, C crouch, Q and E lean, number keys to swap, P for helmetcam, and Transparent Optics in Settings. It says updates can be weekly and sometimes daily. It says an in-game report system is in testing and that a 3D replay can be used to check cheating. It warns that XP and IC may be wiped. It states an intent to build further modes. Intent is quoted in the next section. It is not moved into this one.
The October 15 pages on this wiki also record the title wording TTK Testing [SERVERBROWSER] from that earlier read. The October 25 name field is a later observation of the same place id. A server browser signal and a seasonal weapon bracket can both be true as dated title notes. Neither one is a new game. The server browser page and the Halloween marker page hold those title notes so this roadmap does not inflate them into features we have not seen.
[NEW AR15] belongs in the live column only as a title fact: the name presented AR15 as a newly added weapon. It does not belong here as a balance patch, a recoil change, or a required unlock. The AR15 page is the boundary. The Innovation in Tech mention from the 2026 Innovation Awards is likewise a listing fact when the description states it. An award is not a mode, and it does not date the plans below.
What June 2 said was already in the game then
The DevForum post of June 2, 2026 is primary for that day and only that day, unless a later source repeats it. The post says the project at that time had PVP with multiple modes, plus character and weapon customization. It names callouts, stances, lasers, flashlights, leaning, door kicking, and lockpicking. It says CQB PVP was in the game. It says the goal was easy to pick up and lightly realistic, not a hardcore milsim.
This roadmap does not silently renew those sentences for October. CQB PVP might overlap the deathmatch test you play tonight. The sources do not say "CQB was renamed to the current menu." Play the label the client shows, and keep June's label on June's row. Customization, lasers, and flashlights are handled as names on the attachments page, with the loadout screen as the check for what is still visible. Leaning is renewed by the official control list, which is why Q and E are in the live column without needing the June post. Door kicking and lockpicking are not renewed by that control list. They stay feature names from June until a prompt in your client or a new official sentence says more.
What is still a plan
Plans are sentences an official source said on purpose, which a later live check has not moved into the menu. They are worth reading. They are not worth building a loadout around, and they are not worth a fake date. The updates page is where a newly live sentence should gain a row after someone re-reads the listing.
| Item | Where it was said | How this wiki files it |
|---|---|---|
| Co-op PVE with squad AI | Official game description, as intent | Plan. Not a queue we tell you to select. No AI count is published, so none is printed. |
| Story breach missions | Official game description, as intent | Plan. Door kicking from the June post is a related feature name, not proof these missions are the current doors. |
| Team PVP | Official game description, as intent | Plan. The live public record remains a deathmatch-style test. Do not assume teammates. |
| Co-op missions and hostage rescue | DevForum, June 2, 2026, named as a core mode | Plan, dated June 2. Not merged into the description's breach line, and not given a map. |
| Big PVP with vehicle transport and long-range shooting | DevForum, June 2, 2026, named as a core mode | Plan. No vehicle list, no extra player count, no distance value. The experience cap we can cite is still 12. |
| CQB PVP | DevForum, June 2, 2026, described as in the game then | A June live-claim. Not automatically the October mode name. See planned modes before you equate it with today's queue. |
The modes page on this wiki also carries four direction names from the developer discussion already summarized there: Survival, Missions, Quick Play, and Ground War. Those names are plans in that earlier write-up. This roadmap does not rename them into the June list, and it does not rename the June list into them. Survival is not hereby the same sentence as squad AI. Ground War is not hereby the same sentence as Big PVP. They might someday describe one design. The sources we have do not say they do. The modes page keeps the short split. Planned modes keeps the June wording. You need both pages if you are about to argue that two similar phrases are one mode.
Co-op, squad AI, breach, and hostages
Read these as four phrases, not one mission. Co-op PVE and squad AI arrive together in the official description's intent. Story breach missions arrive in that same intent line, which is about getting through a scenario. Hostage rescue arrives in the June 2 core-mode sentence beside co-op missions. Door kicking and lockpicking arrive as feature names in that post, not as the mission list. A careful summary is: the team has said it wants cooperative play against AI, scenario play that involves breach, and hostage rescue as a core direction, and it has said the project used door kicking and lockpicking as features in June. A careless summary is: "the hostage breach mission is live and here is the route." We do not have the route. We do not have a map name. We do not have a hostage count. The careless summary stays off the site.
What you can practice now is still the live control list. M2 and M1 are how you would shoot in a later mission. Q and E are how you would take a corner. C is how you would change height at a door. None of that practice requires the mission to be queued. The advanced controls page is the drill. It is not a walkthrough of an unreleased level.
Big PVP, vehicles, and long range
Big PVP, in the June post, is the large PVP idea that includes vehicle transport and shooting at longer range. Big is the team's adjective. It is not a headcount. The only player maximum this wiki will cite for the experience is 12, from the API field, and that field describes the experience cap we read. It does not describe a future Big PVP lobby, and it does not deny one. It simply is not that lobby's number. Ground War, on the modes page, also has no published headcount. Do not borrow a number from the word big, and do not borrow one from the current cap and pretend it is the future mode.
Vehicle transport has no model list, no seat count, and no key. Long-range shooting has no meter value. The builds page already tells you to name a far band with a landmark in the match you are in, rather than with a distance figure. That method is for the current test. It does not preview Big PVP's lanes, because those lanes are not published. When a vehicle exists in a client you can sit in, the roadmap gains a dated sentence that the client showed a vehicle prompt. Until then the row stays a plan.
Side by side, without a calendar
Use this comparison when a video says "the new mode dropped." Ask which column the claim needs. If the claim needs the plan column, ask whether the official description has started speaking in the present tense, or whether the client shows the button. A DevForum sentence from June is not a drop in October. An updated field of 2026-10-23 means the catalog entry changed on that date. It does not itemize the change. Weekly or daily cadence means the entry can change again. It does not mean every plan shipped on the quiet days.
| Question | Live column | Plan column |
|---|---|---|
| What do I select tonight? | The public test the client offers, inside a 12-player cap. | Nothing, until a button exists. Co-op, hostage rescue, and Big PVP are not assumed queues. |
| Who is on my side? | Do not assume teammates in the deathmatch-style test. | Team PVP and co-op are intent. They are not tonight's roster rule. |
| What do I press? | M1, M2, C, Q, E, number keys, P. Transparent Optics is a setting. | No extra binds for vehicles, AI orders, or hostage actions. |
| What might be wiped? | XP and IC, per the description. See XP and IC. | A future unlock tied to a plan mode is even less safe to grind. Prices are unpublished either way. |
| What does the report tool cover? | In-game reports are described as in testing, with 3D replay for cheat checks. See report system. | The June post does not document that tool. Do not file the tool under the June roadmap. |
Codes are not a roadmap item. The description did not publish one on the checks we record. Expired codes are not a hidden patch history. Both facts live on the codes and expired codes pages so a seasonal title cannot be misread as a drop.
What this roadmap will not grow
- A quarter, a version number, or a "coming next" order. The sources do not sort the plans.
- Vehicle names, seat counts, AI squad sizes, hostage counts, or a Big PVP player cap.
- Map names for breach or rescue. The maps page refuses a roster for the current test already. Future missions do not get a roster first.
- A claim that the 2026-10-23 update field was the co-op patch, the AR15 balance patch, or a Halloween event. The field is a timestamp. The name field that morning included a pumpkin and [NEW AR15]. That is all those two fields say.
- Developer biographies beyond the credits already on the dev team page. A roadmap is not a studio profile.
When you re-check, open the game page and the API record, then re-read the June post only to keep its date straight. If the description starts saying a plan is playable, or your client shows the mode, mail hello@ttktesting.com with the time and the sentence. The page should gain a row. It should not be rewritten so the old plan looks as if it had always been live. The verify page is the grade that mail has to meet.
Common mistakes
- Reading "core mode" in a June post as "installed in October." Core was the team's word for direction. The menu is a later check.
- Merging story breach and hostage rescue into one mission with a route. They are separate phrases from separate sentences.
- Giving Big PVP the current 12-player cap, or giving it any other cap. No Big PVP headcount is published.
- Treating SERVERBROWSER, the pumpkin, and [NEW AR15] as three roadmap releases. They are dated observations of the title on one place id.
- Using a competitor roadmap that lists dates. Their dates are leads. Our table has sources and no dates of arrival.
- Skipping planned modes and deciding this page replaced it. This page summarizes. That page argues the clocks. Keep the link.
FAQ
Is co-op playable?
Not as a mode this wiki will tell you to queue. Squad AI and co-op PVE are intent in the official description. Hostage rescue is a June 2 core direction. Play them when the client shows them. Until then you are in the public test.
Did Big PVP add vehicles already?
The June 2 post describes Big PVP with vehicle transport. That is a plan sentence. No later source we use lists a vehicle you can spawn in the October test. If your client shows one, that sighting needs a date before anyone calls it shipped.
Is CQB the same as the current free-for-all?
Not proven. CQB PVP was called in-game on June 2. The October record is a 12-player deathmatch-style test. Overlap is possible. A rename is not stated. The planned modes page keeps both labels.
When is the next mode coming?
No date is published. Weekly or daily updates describe cadence, not a promise that the next update is co-op, breach, or Big PVP. Re-read the description instead of trusting a countdown on another site.
Which page is the short version?
Planned modes is the argument. Modes is the live-versus-named-directions split used earlier on this wiki. This roadmap is the comparison you can scan. None of the three is a calendar.
Sources
- Roblox game page, place 120189115846709: live description, including co-op PVE, squad AI, story breach missions, and team PVP as intent.
- Games API, universe 10090256806, October 25, 2026, 09:15 UTC+8: name, updated 2026-10-23 UTC, created 2026-04-27, maxPlayers 12, genre. See game stats.
- DevForum, June 2, 2026: CQB PVP, hostage rescue, Big PVP, vehicles, long-range shooting.
Last checked: October 25, 2026.