The Sable Digital Roblox group is the official community hub for TTK Testing, the tactical shooter that has spent the better part of 2026 in an open V0.x testing cycle. If you have ever wondered where the dev logs live, who actually builds the gunsmith system, or what else the studio has shipped besides this flagship FPS, the Sable Digital Roblox group is the single most reliable starting point. This article breaks down the studio's roster, its dev cadence, and the sibling projects that quietly shape the engine under the hood.
Who Runs the Sable Digital Roblox Group
The Sable Digital Roblox group is anchored by two developers who are consistently visible across every official channel: PoptartNoahh and CanyonJack. According to the verified Roblox group page, Sable Digital previously operated as NC Software, and the studio now oversees TTK Testing along with several earlier experiments. The group's membership has crossed 90,000 players, which gives a useful sense of how broad the audience for a single tactical FPS has become on the platform.
| Channel | Handle / URL | Primary Use | Verified Status |
|---|---|---|---|
| Roblox Group | Sable Digital (ID 7358272) | Announcements, role flair, member count | L1 verified 2026-09-13 |
| DevForum Thread | ttk-our-very-early-tactical-fps | Long-form dev log and roadmap | L1 verified 2026-09-13 |
| X / Twitter | @poptartnoahh | Short build notes, patch timing | L1 verified 2026-09-13 |
| YouTube | @poptartnoahh | Patch showcase videos (V0.01 → V0.09) | L1 verified 2026-09-13 |
| Official Game Page | TTK Testing on Roblox | Live build version, platform support | L1 verified 2026-09-13 |
Meet the Studio's Two Named Leads
PoptartNoahh is the more public-facing of the two, posting short patch notes on X and recording the official V0.x update showcases on YouTube. CanyonJack operates more behind the scenes, surfacing primarily through the DevForum thread replies and the in-game credits. Together they form a small two-person core team, with community contractors contributing map art, weapon sound design, and QA across each V0.x test pass.
Why the Group Matters for Players
A verified Roblox group is not just a badge on your profile. It is the only place where official role ranks get assigned for beta access, and the group wall surfaces bug-report replies that are usually faster than the DevForum. New players who want to influence time-to-kill tuning or push a specific weapon request should join the group before they start posting elsewhere, because the developers sort their inbox by group membership first.
The DevForum Thread and What It Logs
The TTK Testing DevForum thread titled "TTK: our very early tactical FPS" functions as the studio's primary long-form development log. The thread is pinned to the top of the dev's forum profile, and every major roadmap decision since the V0.01 build is documented in it. As of the September 2026 build, the roadmap outlines four major modes: co-op PVE Survival waves, linear story Missions with doorkicker mechanics, standard PVP Quick Play, and a large-scale objective mode called Ground War.
Roadmap Pillars Documented in the Thread
| Mode | Status (V0.09) | Core Mechanic | Community Priority |
|---|---|---|---|
| PVE Survival | In test | Wave-based co-op against AI squads | High |
| Missions (Doorkicker) | In test | Linear story, breach-and-clear | Medium |
| PVP Quick Play | Live | Standard team deathmatch tuning | High |
| Ground War | Teased | Large-scale objective PVP | Medium |
| Spectating | In test | Free-cam observer mode | Low |
| Teams / Launchers | In test | Squad loadout sharing, underbarrel GL | Medium |
According to the DevForum thread, the studio frames the entire V0.x phase as an "early community test focused on time-to-kill tuning and realistic weapon handling." That framing matters because it tells players that feedback on damage curves, helmet cam behavior, and optic clarity is being collected live, not deferred to a future patch. If a gun feels off in V0.09, the dev log is where the change will be acknowledged.
What Gets Posted and What Does Not
The DevForum thread is not a daily changelog. The studio uses it for structural decisions: new modes, engine rewrites, and confirmed roadmap shifts. Day-to-day build notes — what changed in V0.04 versus V0.03, for example — are pushed to the PoptartNoahh YouTube channel as short showcase videos, while quick patch-timing updates land on X. The group wall sits in the middle, mostly used for community callouts and bug reproduction requests.
TTK Testing Development and Patch Cadence
TTK Testing development runs in a tight V0.x loop, with each version bringing a new mechanic, weapon, or map into the live build. The YouTube channel documented the cadence clearly: V0.01 debuted Helmet Cam, V0.02 added a shotgun and a new map, V0.03 brought a pistol and the flash grenade, and V0.04 introduced the Gunsmith system that lets players tune individual parts of a weapon. As of the live build in September 2026, the game is on V0.09, which is the Gunsmith-heavy milestone most current feedback is built around.
Major V0.x Milestones
| Build | Headline Feature | Source Channel | Date Context |
|---|---|---|---|
| V0.01 | Helmet Cam (P key) | YouTube showcase | Early 2026 |
| V0.02 | Shotgun + new map | YouTube showcase | Early 2026 |
| V0.03 | Pistol + flash grenade | YouTube showcase | Mid 2026 |
| V0.04 | Gunsmith system | YouTube showcase | Mid 2026 |
| V0.09 | Live build (Sept 2026) | Official game page | Current |
The TTK Testing development loop is unusually transparent for a Roblox FPS. Every V0.x release ships a YouTube walkthrough that lists the exact keybinds and settings changes, so a player can verify what is live before downloading the next test pass. That rhythm is also why the DevForum thread has stayed active: players use it to compare their own V0.09 experience against the documented V0.04 baseline.
Platform Support and Settings
The official game page states that TTK Testing targets PC, mobile, Xbox, and PS5 with maximum compatibility, and pins Helmet Cam to the P key. It also recommends Transparent Optics in the Settings menu, which simulates both-eyes-open visibility through the scope. That recommendation is consistent with the studio's stated focus on realistic weapon handling and is the kind of detail that surfaces in the DevForum thread rather than in the patch notes.
Ares VR and the Sibling Projects at Sable Digital
TTK Testing is the studio's flagship, but it is not the only project under the Sable Digital umbrella. The group page lists three sibling projects that share engine code and design DNA with the tactical shooter: ARES VR, the Hellreaver series, and the internal Room Engine. Each one feeds lessons back into TTK Testing in a different way. Developers can dig into the nitty-gritty of that feedback loop in our Ttk Testing Support guide, which documents how ARES VR, the Hellreaver series, and the Room Engine each push telemetry, crash reports, and design notes upstream to the tactical shooter.
Project Lineup
| Project | Genre | Role in Studio Pipeline | Community Status |
|---|---|---|---|
| TTK Testing | Tactical FPS | Flagship, current focus | Active V0.x testing |
| ARES VR | VR shooter | VR mode prototyping, optic research | Niche community |
| Hellreaver | Action series | Combat feel, melee animation system | Cult following |
| Room Engine | Internal tool | Modular building blocks for maps | Private alpha |
TTK Testing ARES VR Crossover
ARES VR is the studio's VR shooter, and it shares enough DNA with TTK Testing that several weapon handling experiments show up in both games. The ARES VR optic code, in particular, informed the Transparent Optics setting in TTK Testing. According to the PoptartNoahh YouTube channel, the ARES VR Roblox build is a useful reference for how a given scope will look and behave before the studio ports the optic into the flagship tactical shooter. That crossover is also why the DevForum thread occasionally references "VR testing" when describing upcoming optic options.
Hellreaver and the Room Engine
The Hellreaver series, also credited to Sable Digital, is where the studio's melee animation and hit-feedback work originally matured. Several of the gore and impact reactions in TTK Testing's PVE Survival mode trace back to the Hellreaver combat feel system. The Room Engine is the less visible piece: an internal Roblox toolset that handles modular room construction, door breach logic, and the doorkicker mechanic that defines the Missions mode. None of the Room Engine is sold or licensed externally; it exists so that the studio can build new missions faster than the V0.x cadence would otherwise allow.
How to Engage With the Studio as a Player
Engaging with Sable Digital is straightforward, but the order matters if you want a response. The fastest channel for a quick yes/no question is the X account, the best channel for a structural suggestion is the DevForum thread, and the best channel for a reproducible bug is the Sable Digital Roblox group wall. The official game page also acts as a status check, because the V0.x build number is always listed there.
Step-by-Step: Filing Effective Feedback
| Step | Action | Where | Why It Matters |
|---|---|---|---|
| 1 | Join the Sable Digital Roblox group | Group page | Unlocks role ranks for beta access |
| 2 | Reproduce the bug on a clean V0.09 client | Local test | Filters out client-side mods |
| 3 | Record a short clip of the issue | Screen recorder | Speeds up verification |
| 4 | Post the clip with the V0.09 build number | Group wall | Keeps the bug in the active queue |
| 5 | Cross-link the post in the DevForum thread | DevForum reply | Ties it to the official roadmap |
| 6 | Tag the dev on X if no reply in 48 hours | X / Twitter | Escalates without spam |
If the issue is a structural change — for example, a request to rework how Gunsmith attachments affect recoil — the DevForum thread is the right home. Bug reports and visual glitches belong on the group wall, where the moderators can pin a reproducible clip. The studio reads all three channels, but the priority queue is DevForum > Group > X.
When to Expect a Response
According to community reports on the DevForum thread, the studio typically replies to structural feedback within a week and to bug reports within 48 hours during the V0.x testing window. Patch-timing announcements are pushed to X within hours, while roadmap changes take longer and usually show up as a new reply in the DevForum thread rather than as a post on the group wall.
Frequently Asked Questions
What is the Sable Digital Roblox group for?
The Sable Digital Roblox group is the official community hub for TTK Testing and the studio's other projects, including ARES VR and the Hellreaver series. It hosts patch announcements, role ranks for beta access, and the fastest verified channel for reproducible bug reports tied to specific build versions.
Where can I read the TTK Testing DevForum dev log?
The dev log lives on the official Roblox DevForum in the thread titled "TTK: our very early tactical FPS." It documents the V0.x roadmap, including co-op PVE Survival, Missions, PVP Quick Play, and the upcoming Ground War mode.
Is ARES VR connected to TTK Testing?
Yes. ARES VR is a Sable Digital Roblox project that shares engine code, optic research, and animation rigs with TTK Testing, letting the studio prototype Transparent Optics settings in a smaller VR sandbox before shipping them into the flagship tactical shooter. Several current TTK Testing optic parameters, including reticle scaling curves and barrel-distortion falloff, trace directly back to ARES VR experiment logs.
What is the Hellreaver series?
Hellreaver is an earlier Sable Digital action project, also credited to the studio and tracked in the same Roblox group alongside TTK Testing and ARES VR. Its weighty melee swing windows, parry stun timers, and screen-shake hit-feedback tuning were prototyped there before being ported into the PVE Survival co-op mode, where they now shape enemy stagger behavior and the breach-and-clear flow that the Room Engine's doorkicker logic was later built around.
What does the Room Engine do?
The Room Engine is an internal Sable Digital toolset that drives modular map construction, door breach logic, and the doorkicker mechanic in TTK Testing, letting the studio assemble new missions from prefab room blocks rather than scripting each layout by hand. It is not sold or licensed externally, and exists solely to compress build iteration cycles for PVE Survival and Ground War mission authoring inside the Sable Digital Roblox group's own development pipeline.