The TTK Testing verified badge is the small but reliable signal that the tactical FPS you are loading inside Roblox is genuinely shipped by Sable Digital, the studio led by developers Poptartnoahh and CanyonJack. Knowing what that badge represents matters because early tactical shooters live or die on trust, and the verified mark is how the community separates first-party builds from copycats, reskins, or impersonator experiences. This guide unpacks who runs the game, what the badge actually verifies, and how the developer team ships every V0.x patch.
What the TTK Testing Verified Badge Confirms
The verified badge attached to TTK Testing is not a marketing sticker; it is a Roblox-side verification that ties the experience directly back to the Sable Digital official Roblox group, the studio account, and the two named creators who own the project. When players see the badge, they are looking at confirmation that the build originates from the same team that wrote the original DevForum roadmap, runs the official YouTube update showcases, and posts live patch notes from the developer account.
The Three Layers of Verification
The badge is really a stack of three independent signals that the studio maintains in parallel, which is why impersonation attempts have been rare and easy to flag inside the community.
| Layer | What It Confirms | Where To Check It |
|---|---|---|
| Studio Group Badge | Group is owned by Poptartnoahh and CanyonJack | Sable Digital Roblox group page |
| Game Page Attribution | TTK Testing is published by the verified studio account | Official Roblox game page |
| Developer Channel Sync | Patch notes match the public dev log | DevForum thread + Poptartnoahh YouTube |
Each layer is updated by the team directly, so the moment a new V0.x build goes live, the badge reflects that the build is genuine, current, and supported. Community testers typically cross-check the badge against the dev log before reporting bugs, which keeps the feedback channel clean and helps the developers triage issues faster during a live patch window.
Why Verification Matters for a Tactical Shooter
Verification matters more in a realistic, time-to-kill-driven game than in a casual Roblox experience because trust affects how players interpret the build. A single fake server listing, a reskinned clone, or an impersonator studio page can spread misinformation about gun balance, armor values, or new content, which then pollutes the official community feedback that the developers actually need to read. The verified badge closes that loop by giving players a one-glance confirmation that the build is reading from the same source of truth as the dev log, the YouTube channel, and the Sable Digital group announcements.
Sable Digital: From NC Software to TTK Testing
Sable Digital is the TTK Testing studio, and the studio previously operated under the name NC Software before re-branding. The rebrand is visible across older group pages, older social handles, and earlier in-engine splash screens, which is why long-time community members sometimes still refer to the team as NC Software in legacy threads. The studio is small, focused, and ships one flagship project at a time, which is why every public V0.x update is tied directly to the same two leads rather than a rotating roster of contributors.
Studio Profile at a Glance
| Attribute | Detail | Source |
|---|---|---|
| Studio Name | Sable Digital (formerly NC Software) | Roblox group page |
| Group ID | 7358272 | Roblox group URL |
| Community Size | 90,000+ members | Roblox group member count |
| Flagship Project | TTK Testing | Roblox game page |
| Prior Projects | ARES VR, Hellreaver series, RooM Engine | Studio history on group page |
The studio is best understood as a focused tactical-FPS team rather than a content factory, which is why every public-facing communication channel maps back to the same two creators and the same DevForum thread. If you are looking for the single page that ties the studio identity together, the Sable Digital official Roblox group is the canonical anchor.
Studio History in Brief
Sable Digital's earlier work includes ARES VR, the Hellreaver series, and the RooM Engine, and each of those projects contributed reusable systems that now appear inside TTK Testing. The RooM Engine, for example, feeds the lighting and interior rendering of the doorkicker mission maps, while the ARES VR handling code shaped how weapon weight and reloading animations feel in first person. The Hellreaver series is where the studio first iterated on punishing damage values, which is the same philosophy that drives TTK's tight time-to-kill tuning. Knowing that lineage is useful because it explains why TTK Testing does not feel like a generic Roblox shooter; the studio has been iterating on tactical handling for years.
The Two Creators: Poptartnoahh and CanyonJack
The TTK Testing creators Poptartnoahh and CanyonJack are the only two named developers who own the project, run the public communications, and sign off on each V0.x build. The pair splits responsibilities in a way that shows up clearly in the public output, with one lead owning systems, weapons, and the dev log, while the other focuses on community channels, content cadence, and the studio's broader Roblox presence.
Poptartnoahh: Lead Developer and Public Voice
Poptartnoahh is the lead developer of TTK Testing and the public face of the project across YouTube, X, and the Roblox DevForum. The PoptartNoahh YouTube channel hosts every official update showcase, from the V0.01 Helmet Cam debut and the V0.02 shotgun and map drop, through the V0.03 pistol and flash grenade update, and into the V0.04 Gunsmith Showcase and weapons pool expansions. The channel is the primary video source for verifying what is actually live in each V0.x build, because every showcase is recorded from a clean server and is timestamped against the matching DevForum patch entry.
Poptartnoahh also posts short build notes, live server announcements, and community callouts on X under the same handle, which is where fast-moving patch timing usually shows up first during a V0.x test phase. Players who want to track when a server restart is happening, when a new optics preset is enabled, or when a hotfix is rolling out tend to follow the X account in parallel with the YouTube channel, because the two feeds are complementary rather than redundant.
CanyonJack: Co-Owner and Studio Operator
CanyonJack is the second named creator of TTK Testing and the co-owner of the Sable Digital group, sharing ownership with Poptartnoahh on the official Roblox group page. CanyonJack's role is less visible on the video side and more visible on the operational side, which is why his name appears in group administration, member management, and the historical NC Software-to-Sable Digital transition. Co-ownership of the group is what allows both developers to push group-only announcements, manage community roles, and post verified status updates that the rest of the community can trust.
The split between a public lead developer and an operational co-owner is a deliberate studio structure, and it shows in how patch cycles are run. Poptartnoahh ships the in-engine changes and records the showcase video, while CanyonJack keeps the community channels, group roles, and studio metadata aligned so the verified badge stays accurate.
How Patches Are Shipped: The Dev Log, YouTube, and Group Loop
The TTK Testing developer team ships every patch through a closed feedback loop, and understanding that loop is the most useful piece of developer knowledge a player can have. The loop starts with the public dev log, expands into a YouTube showcase, and lands in a verified group announcement, with each step acting as a cross-check for the others.
The V0.x Roadmap and Dev Log
The team's public roadmap is documented inside the official DevForum thread titled "TTK: our very early tactical FPS", which acts as the canonical dev log for the project. The thread breaks the early-access phase into a sequence of V0.x builds, each adding or refining a specific pillar of the design.
| V0.x Build | Focus Area | What Players Should Watch For |
|---|---|---|
| V0.01 | Helmet Cam debut | First-person POV verification, P-key helmet cam |
| V0.02 | Shotgun and map drop | New close-range weapon, fresh interior map |
| V0.03 | Pistol and flash grenade | Sidearm balance, non-lethal utility |
| V0.04 | Gunsmith Showcase | Attachment system, weapons pool expansion |
| V0.09 | Live build as of Sept 2026 | Current verified patch players load into |
The same thread also frames TTK Testing as an early community test focused on time-to-kill tuning and realistic weapon handling, which is why the verified badge matters so much. When a build is current, the dev log entry is current, the YouTube showcase is current, and the group status is current, all in the same week.
The YouTube Showcase Pipeline
The second leg of the loop is the PoptartNoahh YouTube channel, which is where each V0.x build gets a recorded showcase. Showcases are not trailer content; they are clean walkthroughs of new features, recorded on a live server, with timestamps that match the dev log entry. Community members often use showcase videos to verify that an attachment, a setting, or a weapon behaves the way the dev log describes, which is especially useful for time-to-kill discussions where one extra frame of animation can change a balance conclusion.
The showcase format is also what catches the rare cases where a build goes out with an unintended regression, because players will pause the video, compare to the patch notes, and report the discrepancy back through the verified feedback channels. That player-driven QA loop is part of why the studio has been able to ship meaningful content patches inside the V0.x cycle.
The Group Announcement and Verified Feedback Path
The third leg is the Sable Digital group, where each V0.x build is mirrored as a group announcement alongside the public dev log and showcase. The group is also where the studio runs the verified feedback channel, which is why a bug report, a balance suggestion, or a creator exchange is most likely to be read when it is posted through the official group rather than scattered across random third-party servers. For more detail on how that feedback path works, the TTK Testing feedback guide walks through the studio's published-by history and how to route suggestions into the verified pipeline.
Trust Signals Players Can Verify in 60 Seconds
The verified badge is the headline signal, but the studio gives players several layered trust checks that take about a minute to confirm. Running through these once after every major patch is a good habit, because it keeps the community aligned on what is actually live.
| Signal | What To Check | Why It Matters |
|---|---|---|
| Verified Roblox Group | Sable Digital group badge is present | Confirms studio ownership |
| DevForum Thread Activity | New posts match the latest build | Confirms dev log is current |
| YouTube Showcase | New video covers the same patch content | Confirms video source of truth |
| In-Game Settings Match | P key helmet cam, Transparent Optics default | Confirms official build behavior |
| X Account Posts | Patch timing matches DevForum entry | Confirms live server window |
That last row is worth a special mention, because the Poptartnoahh X account is the fastest place to catch a live patch window. When the studio opens a stress test, rolls out a hotfix, or restarts a regional server cluster, the X post usually lands before the group announcement is fully formatted, which is helpful for testers who want to be online during a known patch boundary.
Using Verified Channels to Contact the Studio
Players who want to reach the developers directly should use the verified channels rather than random DMs or third-party Discords, because the verified channels route into the studio inbox that the developers actually read. The studio has not published a public Discord, which is intentional; every official channel is mirrored on a platform the studio controls.
| Purpose | Best Channel | Link / Reference |
|---|---|---|
| Bug Report | Sable Digital group wall | Official Roblox group page |
| Patch Question | DevForum thread reply | TTK: our very early tactical FPS |
| Creator Exchange | Group DM after joining | Sable Digital group |
| Press / Creator Outreach | PoptartNoahh X DMs | x.com/poptartnoahh |
| Video Verification | YouTube community tab | PoptartNoahh channel |
The intentional absence of a public Discord is part of the studio's trust posture. Rather than splitting attention across half a dozen unmoderated servers, the team funnels everything through the verified channels listed above, which keeps the source of truth clean. If you want a deeper walkthrough of how the support pipeline is structured, the TTK Testing support guide maps out which channel fits which kind of player question.
The Studio's Road Ahead
What makes the verified badge meaningful in the long run is that the studio treats it as a covenant: every build the community loads is genuinely tied to the same two creators, the same dev log, the same YouTube channel, and the same group page. As the project moves toward its first standalone build, that covenant is what players will be able to point to when they want to know which version is real. For a wider look at how the Sable Digital history ties into that standalone push, the TTK Testing Sable Digital history guide is the best companion read.
Frequently Asked Questions
What does the TTK Testing verified badge actually verify?
The verified badge confirms the experience is published by Sable Digital and is tied to the studio's official Roblox group, not a copycat or impersonator. It is the easiest one-glance signal that the build lines up with the DevForum dev log and the Poptartnoahh YouTube showcase for the same patch.
Who are the TTK Testing creators?
The TTK Testing creators are Poptartnoahh, the lead developer and public voice, and CanyonJack, the co-owner and studio operator. Both names appear on the Sable Digital Roblox group ownership, and they are the only two developers who ship the V0.x builds.
Is Sable Digital the same studio as NC Software?
Yes, Sable Digital previously operated as NC Software, and the rebrand is visible on older social handles, older splash screens, and a few legacy group references. The studio's flagship project under the new name is TTK Testing, and the rebrand is what gives the verified badge its current shape.
How can I tell if a TTK Testing build is genuine?
Cross-check the in-game version against the DevForum dev log, the latest PoptartNoahh YouTube showcase, and the Sable Digital group announcements. If all three line up, the build is genuine; if a third-party server is running a different build, it is not an official TTK Testing deployment.
Where should I send a bug report or balance suggestion?
The best place is the Sable Digital Roblox group wall or the official DevForum thread, because both feed the verified feedback path the developers actually read. Avoid posting only on third-party Discords, because the studio has not published an official Discord and does not monitor those servers directly.