The TTK Testing Roblox group is the single verified community hub where Sable Digital posts every patch note, roadmap update, and bug report thread for the tactical shooter. Run by developers Poptartnoahh and CanyonJack, the Sable Digital group page now sits north of 90,000 members and acts as the central nerve center for anyone who wants to track V0.x testing in real time. Players who want a direct line to the studio, faster patch intel, and a feedback channel that actually gets read should make this group their first bookmark.
What the TTK Testing Roblox Group Actually Is
The TTK Testing Roblox group is not a fan-made Discord mirror or a third-party aggregator — it is the verified, Roblox-issued group owned by the Sable Digital studio. The group page lists TTK Testing as the flagship project, the studio's two leads as owners, and a community roster that has more than tripled since the V0.01 Helmet Cam debut in late 2025, according to community data.
Sable Digital is the same studio that previously shipped ARES VR, the Hellreaver series, and the RooM Engine. The group is therefore both a community surface and a studio-wide hub: when the team teases new modes, the announcement lands here first before it surfaces on YouTube or DevForum.
Core Identity of the Group
| Attribute | Detail |
|---|---|
| Group name | Sable Digital |
| Roblox group ID | 7358272 |
| Verified status | Roblox-verified studio group |
| Member count | ~90,000+ as of 2026 |
| Lead developers | Poptartnoahh, CanyonJack |
| Studio history | Previously operated as NC Software |
| Flagship game | TTK Testing |
| Sister projects | ARES VR, Hellreaver, RooM Engine |
Group Roles and What They Unlock
Membership in the TTK Testing Roblox group is mostly symbolic — there is no exclusive in-game loot gated behind the rank. The real value is the signal: members see pinned announcements at the top of the group wall, get tagged in major patch breakdowns, and can post in the group forum without queuing behind non-member spam. Players who want to help with structured feedback often cycle between this group wall and the studio's official Roblox game page, where DevLog-style patch lists are also mirrored.
TTK Testing Official Links and Where the Studio Posts
The group page is the anchor, but the Sable Digital team broadcasts across a small, consistent set of channels. Knowing which channel carries which kind of information saves players from chasing rumors on Reddit threads.
The Verified Channel Map
| Channel | What Lands Here | Cadence | Best For |
|---|---|---|---|
| Sable Digital Roblox group | Patch banners, group events, role calls | Per build | Joining the 90k community |
| PoptartNoahh on X | Short build notes, server test pings | Daily during V0.x | Tracking live hotfixes |
| TTK Testing DevForum thread | Long-form roadmap, patch retros | Weekly | Studying the V0.x roadmap |
| PoptartNoahh YouTube channel | Full update showcases, weapons tours | Per major build | Verifying what's live |
| Roblox game page description | Compatibility notes, control defaults | Static + per build | First-time install setup |
For cross-checking weapon and attachment changes, the YouTube showcases are especially useful because each one pairs a V0.x build number with on-screen footage of the new gunsmith slot, which is harder to fake than a text patch note.
Why the Group Page Leads the Loop
The TTK Testing Roblox group is the only channel where every other announcement is mirrored in summary form, which is why most veteran players treat it as the "front page." A typical V0.x release cycle lands like this: Poptartnoahh drops a YouTube showcase, a short X post flags the timing, the DevForum thread adds long-form dev commentary, and the Sable Digital group wall pins a one-paragraph recap with the build number. The group is the only stop where the entire loop is summarized in one scroll.
Choosing the Right Official Channel for Support
Players who want a real response have to choose the right door. Sable Digital does not run a help-desk ticketing system, so the team's attention is split between the group wall, DevForum, and direct DMs to the two leads. Picking the wrong channel for the wrong request is the most common reason feedback gets ignored.
Picking the Right Channel for Your Request
| Request Type | Best Channel | Why It Works |
|---|---|---|
| Bug report with reproduction steps | DevForum thread (structured format) | Poptartnoahh actively responds |
| General Q&A | Roblox group wall (community answers) | 90k members can answer faster than devs |
| Press or collab inquiry | Direct DM via X (PoptartNoahh) | Linked account, public, trackable |
| Patch timing question | Group pinned post or X timeline | Avoids DM clutter |
| Moderation or member dispute | Group shout through group wall | Studio moderators are tagged in |
The Bug Report Workflow
When a player files a TTK Testing bug report, the studio's working pattern is to read the DevForum thread first, then cross-reference the group wall, and finally DM the reporter for a clip. A solid report therefore includes the build number (for example, V0.09 mi), the game mode, the weapon class, and either a short screen recording or a step list. Players who skip the build number usually get a "which version?" reply, which burns the loop.
The group page also acts as a crowd-sourced QA layer. Members regularly post clips of misaligned sights, stuck lean animations, or unusual Hardpoint zone timings. The studio then triages these clips into the next V0.x hotfix — a workflow that is one of the reasons TTK Testing's gunplay iterates so quickly between V0.04 and V0.09 mi.
TTK Testing Studio History and the Group's Origin
The group did not start as a TTK Testing project page. Sable Digital was previously known as NC Software, and the studio shipped several Roblox projects before the tactical FPS ever entered V0.01 testing. Understanding the studio history explains why the group wall carries so many non-TTK posts, and why the community treats the group as a long-term project rather than a one-game fan page.
Studio Milestones in Order
| Era | Project | Group Wall Signal |
|---|---|---|
| Pre-2024 | NC Software (early group) | Archived under Sable Digital |
| 2024 | ARES VR launch | First large member spike |
| 2024–2025 | Hellreaver series | Reusable combat framework |
| 2025 | RooM Engine rollout | Tech backbone for TTK Testing |
| 2025 | TTK Testing V0.01 Helmet Cam | Group re-pinned to TTK Testing |
| 2026 | V0.09 mi live build | 90k+ member milestone |
The Creator Exchange and the Two Leads
The TTK Testing creator exchange happens at the level of Poptartnoahh and CanyonJack trading tasks rather than a public hiring page. Poptartnoahh is the public face — YouTube showcases, X posts, DevForum comments, and the official developer YouTube channel. CanyonJack handles much of the back-end and combat tuning, which is why weapon recoil changes between V0.04 and V0.09 mi credit both names. Players who want to support the project without spending Robux typically engage the creator exchange by leaving thoughtful DevForum comments, which the team reads before locking the next patch.
TTK Testing Group Members and Community Signals
The 90,000-member count is more than a vanity metric — it shapes what kind of feedback loop the studio can sustain. A larger member pool means faster bug reports, more clips of edge-case bugs, and a richer set of community-made loadout guides. The group members are also the source of the V0.x testing volunteers who show up during weekend stress tests.
Why the Member Count Matters
| Group Size Bracket | Studio Behavior |
|---|---|
| Under 10k | Studio handles QA in-house |
| 10k–50k | Community bug reports start getting pinned |
| 50k+ | Studio runs scheduled public stress tests |
| 90k+ (current) | Studio triages community bug reports per patch |
A useful habit for new members is to read the pinned post before posting. The Sable Digital team uses pinned posts to flag which V0.x build is currently live, which modes are being tested, and which bug class is being prioritized. Skipping the pin often leads to reports on already-fixed issues, which clutters the feedback loop.
Group Events and How to Get Noticed
Group events on the Sable Digital page are the studio's main way of recruiting playtesters for new modes. A typical event is a 30-minute window where the team invites the group to stress-test a new mode (such as the earlier Hardpoint rollout) and asks members to post their feedback in a single DevForum thread. Active members of the TTK Testing Roblox group who consistently file good reports tend to get fast-tracked into later playtests — a quiet but real incentive for players who want closer contact with the dev team.
Players who want to know when a playtest is going live should follow the X account in addition to the group wall, because not every playtest gets a pinned group post. The combination of group wall + X timeline + DevForum thread is the lowest-friction way to catch a playtest window in time to join.
Frequently Asked Questions
How do I join the TTK Testing Roblox group?
Search for the verified Sable Digital group inside Roblox or open the official Sable Digital group page directly, then hit the Join button. Membership is free, and the studio's two leads manually approve new members during high-traffic patches so allow a few hours during V0.x launches.
What is the fastest way to file a TTK Testing bug report?
Post in the TTK Testing DevForum thread with the build number, the mode, the weapon, and a short reproduction list. The team triages DevForum reports first, then cross-references the Roblox group wall, so a structured post there is the single fastest path to a fix.
Can non-members see TTK Testing patch notes?
Yes. Patch notes land publicly on the DevForum thread, the developer YouTube channel, and the official Roblox game page description. The Roblox group is mainly a community-and-feedback surface, while the DevForum thread is the authoritative text log of every V0.x build.
Where do the two TTK Testing creators post the most?
Poptartnoahh posts the most on YouTube and X for short-form patch intel and on the DevForum thread for long-form dev commentary, while CanyonJack appears mainly in the DevForum thread and inside the group's pin threads. Players who want the deepest read of why a V0.x change happened should follow the DevForum thread, not just the group wall.
Is the TTK Testing Roblox group the same as the official Discord?
No. The Roblox group is the only channel owned and verified by Sable Digital inside the Roblox platform, while the studio also runs accounts on YouTube, X, and DevForum. Players should treat the Roblox group as the canonical Roblox-side hub and the other channels as mirrors, with the DevForum thread acting as the long-form record.