TTK Testing is a tactical first-person shooter built inside Roblox by a small studio called Sable Digital, and the people behind that name are the reason the game keeps shipping meaningful updates every few weeks. If you have ever wondered who actually makes TTK Testing, where the official announcements come from, or why the studio keeps talking about a "first standalone" release, this guide lays out everything in one place.
Who Runs TTK Testing at Sable Digital
Sable Digital is the verified Roblox group that owns and ships TTK Testing, and the project is led by two developers who handle most of the public-facing work: Poptartnoahh and CanyonJack. Together they own the game's direction, its community channels, and the cadence of V0.x builds that have rolled out since the project went public.
The group has grown to more than 90,000 members on Roblox, which makes it one of the larger verified developer groups attached to a tactical shooter on the platform. According to the official Sable Digital Roblox group page, the studio is the primary home for TTK Testing announcements, forum posts, and member updates, and the same page confirms that the team previously operated under the name NC Software before rebranding.
The Two Lead Developers
The studio publicly leans on two named leads, and each one owns a different part of the TTK Testing stack — Poptartnoahh controls the live, visible output through the developer YouTube channel and the X account where every V0.x build showcase and patch-time note is published, while CanyonJack drives the planning and coordination side via the Roblox group and DevForum, framing the roadmap and aligning the community around the Sable Digital title's broader release direction.
| Developer | Public Role | Primary Channel | What They Ship |
|---|---|---|---|
| Poptartnoahh | Lead developer | YouTube + X | Update showcases, build notes, weapons, map drops, Gunsmith demos |
| CanyonJack | Co-lead developer | Roblox group + DevForum | Roadmap framing, community coordination, feature planning |
According to the Poptartnoahh developer YouTube channel, the channel hosts the official update showcases for every V0.x build, including the V0.01 Helmet Cam debut, the V0.02 shotgun and map drop, the V0.03 pistol and flash grenade update, and the V0.04 Gunsmith showcase that introduced the weapons pool expansion currently in testing. For shorter notices and live-server patch timing, the Poptartnoahh X account functions as the real-time developer channel.
Studio History and Past Projects
Sable Digital is not a one-game shop, and a quick look at past titles explains why TTK Testing is structured the way it is. Earlier projects like ARES VR and the Hellreaver series gave the studio real combat shipping experience on Roblox, while the proprietary RooM Engine carried over directly into the custom gun handling, recoil profiles, and optics layering that define the ttk testing sandbox today. That same engine lineage is why the ttk testing dev log entries keep referencing tooling milestones alongside gameplay tweaks.
| Past Project | Type | Why It Matters for TTK Testing |
|---|---|---|
| ARES VR | VR shooter on Roblox | First large-scale combat project, built the studio's FPS foundation |
| Hellreaver series | Action titles | Proved the team could ship repeatable content updates |
| RooM Engine | Internal tooling | Underpins the custom gun handling and optics in TTK Testing |
The studio's history matters because it shows that TTK Testing is the team's first push toward a cohesive, branded tactical product rather than a one-off shooter experiment. Community members who followed the NC Software era still recognize the same hands-on update style that defines Sable Digital's public communication today.
How the TTK Testing Dev Log Actually Works
The TTK Testing dev log is not a single document, it is a layered system that the studio uses to keep players, group members, and Roblox developers in sync. Each layer has a different refresh rate and serves a different audience, and understanding the three layers makes it far easier to know when to trust a teaser versus when to wait for a real build.
Where Each Dev Log Layer Lives
| Layer | Where It Lives | Cadence | What You Get |
|---|---|---|---|
| Live build notes | Official game page on Roblox | Every V0.x drop | Confirmed patch content, keybinds, and roadmap markers |
| DevForum thread | Roblox DevForum | Multiple times per build cycle | Design reasoning, behind-the-scenes decisions, community Q&A |
| Social posts | X and YouTube | Real time during tests | Live server callouts, clip reactions, soft announcements |
The TTK Testing official DevForum thread functions as the studio's long-form dev log and is the single best place to read why a build is shaped the way it is. Posts there cover everything from the V0.x roadmap (co-op PVE Survival waves, linear story Missions with doorkicker mechanics, standard PVP Quick Play, and large-scale objective Ground War) to smaller decisions like how teams, spectating, and launchers will be wired in.
Why the Dev Log Feels Fast
The reason the ttk testing dev log seems to update every few weeks comes down to a tight, almost forced feedback loop between three deliberate channels, each one designed to surface player pain points before Poptartnoahh ever cuts a showcase video. Because Sable Digital treats the standalone game build as a public test of the development process itself, the cadence feels closer to a live-service Roblox title than a hobby project, and every V0.x patch doubles as proof that the upcoming game is being shaped by community votes rather than internal guesswork.
-
Players report issues and ask for changes inside the Sable Digital Roblox group and on the DevForum thread.
-
The team replies publicly with confirmation, dismissal, or a "we are testing this internally" tag, which keeps the same feedback visible to everyone.
-
The next V0.x build ships with those responses folded in, and Poptartnoahh posts a video showcase that explicitly points at the changes players asked for.
Because Sable Digital tags each drop as a public test of the dev log itself, the studio stays comfortable shipping V0.x patches, 0.4, 0.5, 0.6, and so on, instead of stalling on a single "perfect" 1.0 build; every tagged build functions as a running A/B test where the ttk testing dev log, the Sable Digital Roblox group, and the next Poptartnoahh showcase video are all evaluated against the same patch notes, which is why a minor fix in the ttk testing standalone game can ship within a two-week window without being treated as a marketing milestone.
The Push Toward the First Standalone TTK Testing Release
The most consistent message from Sable Digital across the last several V0.x builds is that TTK Testing is being shaped as the studio's first standalone Roblox title. The phrase is doing real work here, and it is worth unpacking because the team has hinted at it on every channel.
What "Standalone" Actually Means in This Context
| Term | What Players Often Assume | What Sable Digital Actually Means |
|---|---|---|
| Standalone | A separate PC game outside Roblox | A flagship, self-contained title inside Roblox with its own identity |
| First standalone | The studio's debut on a new engine | The studio's first full tactical product with its own roadmap, brand, and long-term support plan |
| Roblox first standalone | The first Roblox game by the studio | The first flagship Roblox release that fully carries the Sable Digital brand |
The distinction matters because Sable Digital's earlier projects, like the Hellreaver series and ARES VR, shipped as separate Roblox experiences with their own pages. TTK Testing is different: the team is treating it as a flagship with a multi-phase roadmap, a permanent dev log cadence, and a community channel that lives on a long timeline rather than a single launch moment.
What the Standalone Roadmap Looks Like
The current roadmap, as confirmed in the official TTK Testing game page on Roblox and the DevForum thread, breaks the next phases into clear pillars, with Sable Digital organizing development around six parallel tracks ranging from PVE Survival wave co-op to the Gunplay Pass recoil overhaul, so each feature can ship independently without blocking the standalone launch, and players can already see this staggered model in action since Quick Play PVP and V0.09 helmet-cam bindings went live while Story Missions and Ground War remain in pre-production.
| Phase | Core Content | Status |
|---|---|---|
| PVE Survival | Wave-based co-op against squad AI | In active V0.x testing |
| Story Missions | Linear, doorkicker-style objectives | Designed, early build work |
| Quick Play PVP | Standard team deathmatch-style matches | Live in current builds |
| Ground War | Large-scale objective PVP | Planned, not yet live |
| Teams & Spectating | Persistent squads, observer mode | Roadmap feature |
| Launchers & Gunplay Pass | Heavy weapons, recoil tuning | In progress |
The V0.09 milestone referenced on the game's official description is the most recent stable build as of September 2026, and it explicitly pins the Helmet Cam to the P key and highlights Transparent Optics, a settings toggle that models two-eyes-open aiming through scopes, two design choices that will likely carry into the standalone release.
How to Contact the TTK Testing Developers
Because Sable Digital is small, reaching the team is less about a support ticket system and more about showing up in the right official spaces. The good news is that every channel is public, and the team is unusually responsive for a Roblox studio of its size.
Official Contact Channels
| Channel | Best Used For | Response Style |
|---|---|---|
| Sable Digital Roblox group | Bug reports, feature requests, group-wide announcements | Threaded replies from team accounts |
| DevForum thread | Design feedback, longer questions, roadmap input | Detailed written replies from Poptartnoahh |
| Poptartnoahh on X | Quick patch timing, live server notices | Short, frequent posts |
| Poptartnoahh on YouTube | Full update context, video Q&A in comments | Slower but most thorough |
| TTK Testing Discord official | Live playtests, community coordination, build alerts | Real-time chat with team presence |
For bug reports specifically, the Sable Digital group is the safest starting point because it gives the team a stable, searchable history that does not scroll off a feed. For design discussion and roadmap input, the DevForum thread is better because posts stay organized by build number. If you want a quick yes-or-no on whether a feature is shipping, X is the fastest channel.
What the Team Typically Responds To
-
Tied to a specific V0.x build number (so the team can reproduce it)
-
Posted with a short clip or screenshot attached
-
Phrased as a clear suggestion rather than a complaint
-
Cross-posted between the group and the DevForum, which signals that the player is paying attention to the dev log
The team's transparency on the ttk testing discord official server is also a major reason community testing has stayed lively, because the channel doubles as a soft patch-notes feed between formal V0.x drops — pin messages routinely list which Roblox engine regressions, sable digital NPC spawn tweaks, or contact developer routings were just merged, letting testers align their next session with the current dev log.
Community Reception and Studio Communication Style
The way Sable Digital talks to its player base is one of the more distinctive things about TTK Testing, and it is part of why the game has held a 90,000+ member Roblox group despite still being in a V0.x testing phase. Players are not just downloading a build, they are reading the reasoning behind every change.
How the Studio Frames Updates
| Update Element | How Sable Digital Presents It | Why It Works |
|---|---|---|
| Build numbers | V0.01 through V0.09 with public notes | Sets expectations that the game is still being shaped |
| Video showcases | Poptartnoahh-narrated walkthroughs | Replaces text walls with visible in-game proof |
| Roadmap posts | Multi-phase, with explicit "not yet live" tags | Reduces rumor churn about the ttk testing upcoming game features |
| Group callouts | Short, frequent status updates | Keeps the community between formal drops |
Players who follow the most realistic tactical FPS on Roblox showcase by PetriFyTV often cite the same thing: the studio treats the audience as a co-development partner, which is why each V0.x build feels like a response to the previous one rather than a one-way content drop. That dynamic is also visible in the Gunsmith update video from PetriFyTV, which walks through weapons pool changes that came directly out of community suggestions logged on the DevForum thread.
What the Communication Style Signals About the Standalone Push
The deliberate, almost diary-like tone of the dev log is itself a signal that ttk testing roblox first standalone is being treated as a long-term project rather than a one-off experiment. The team is comfortable saying "this is not done yet" on every channel because the audience is being trained to read V0.x builds as a working dev log, not a finished product. That posture is rare in tactical shooters on any platform, and it is one of the strongest reasons the game has held momentum while still being pre-1.0.
What to Watch Next From Sable Digital
For a ttk testing dev log reader, the practical move is to weight the Sable Digital Discord server over the roblox game page, since build-number announcements, Friday patch-note breakdowns, and the standalone build's alpha recruitment are all confirmed to surface in the developer channel first — usually 12–24 hours before a placeholder update lands on the studio's main feed, which is exactly the lead time worth banking on. This 12–24 hour head start lines up neatly with the cadence we've been tracking on the Ttk Testing Roblox Group, where every recent developer-channel drop has preceded its public counterpart by roughly that same window.
The Three Posts Worth Following
-
The Sable Digital Roblox group for forum-style announcements that survive scrolling.
-
The DevForum thread for the most detailed reasoning behind each V0.x build.
-
Poptartnoahh on X for the fastest patch-timing callouts, especially during live server tests.
The Roblox group typically surfaces a release within an hour, the DevForum thread follows 6–12 hours later with the full changelog, and Poptartnoahh's X account catches the micro-patches in real time during live server tests, so the three channels form a staged disclosure loop rather than parallel posts — meaning a tester who only watches one feed will miss either the announcement layer, the reasoning layer, or the timing layer that ttk testing sable digital fans rely on to map each V0.x build's intent.
Indicators That a Bigger Drop Is Coming
| Signal | What It Usually Means |
|---|---|
| DevForum thread goes quiet for a few days | The team is heads-down on a build |
| Poptartnoahh posts a short teaser clip on X | A new weapons or map prototype is being tested |
| Group announcement pins a playtest window | A V0.x candidate is about to go live |
| YouTube showcase drops without prior warning | A new build is already available in-join |
These signals line up with how the studio has handled every V0.x drop so far, and they are the most reliable way to anticipate the next piece of the ttk testing upcoming game roadmap without having to guess from outside the channels.
Frequently Asked Questions
What is Sable Digital in TTK Testing?
Sable Digital is the verified Roblox group that develops and publishes TTK Testing, led by developers Poptartnoahh and CanyonJack with a community of more than 90,000 members. The studio previously operated as NC Software and has shipped other Roblox projects such as ARES VR, the Hellreaver series, and the RooM Engine.
Is TTK Testing Sable Digital's first standalone Roblox game?
It is positioned as Sable Digital's first standalone Roblox title in the sense of a flagship, self-branded tactical product with its own roadmap and long-term support. While the studio has shipped other Roblox experiences before, TTK Testing is the first project that fully carries the Sable Digital identity across all channels and V0.x builds.
Where can I read the TTK Testing dev log?
The official dev log is spread across three places: the Sable Digital Roblox group for announcements, the TTK Testing DevForum thread for detailed design reasoning, and Poptartnoahh's X account for real-time patch timing. YouTube showcases by Poptartnoahh provide video walkthroughs of every V0.x build, which complement the written posts.
How do I contact the TTK Testing developer?
The fastest ways to reach the team are the Sable Digital Roblox group, the official DevForum thread, and the ttk testing discord official server. Poptartnoahh also responds on X and YouTube comments, while the Sable Digital group is the best place for bug reports because threads stay searchable.
Will TTK Testing leave Roblox for a standalone release?
Sable Digital has framed TTK Testing as its first standalone Roblox title, meaning a flagship project on the platform rather than a confirmed external PC release. Players should treat any claim about a non-Roblox version as unconfirmed unless the studio posts it directly on the Roblox group, DevForum thread, or Poptartnoahh's verified social channels.