Sending TTK Testing feedback to the right channel decides whether your idea becomes a build note or vanishes into a Discord void. The game is published by Sable Digital, formerly known as NC Software, and is led by the developer duo PoptartNoahh and CanyonJack. Because the V0.x testing phase is community-driven, structured feedback through the verified Roblox group, the DevForum thread, and the lead developer's social accounts is what actually shapes the next patch.
Who Develops TTK Testing and Why That Changes How You Submit Feedback
TTK Testing is published by Sable Digital, a Roblox studio that previously operated under the name NC Software. The TTK Testing team is small and visibly community-facing, with PoptartNoahh serving as the lead developer and CanyonJack working alongside as a core builder. According to the Sable Digital official Roblox group, the studio has shipped ARES VR, the Hellreaver series, and the in-house RooM Engine before pivoting full attention to this tactical FPS project.
The Studio Identity and Its Origins
The legacy NC Software branding still shows up in older posts and YouTube descriptions, which is why you may see the same developer answering under both names. The current verified handle is Sable Digital, and the studio's group page has grown past 90,000 members as the testing phase has expanded. Knowing that you are talking to the actual TTK Testing team, and not a fan-run server, changes how you should frame your suggestions: treat every report as if it is going straight onto PoptartNoahh's desk, because in many cases it literally is.
| Studio Attribute | Detail | Why It Matters for Feedback |
|---|---|---|
| Current Studio Name | Sable Digital | This is the verified brand on the official Roblox group page |
| Former Name | NC Software | Older content and credits may still carry the NC Software label |
| Lead Developer | PoptartNoahh | Primary decision-maker on build priority and patch timing |
| Co-Developer | CanyonJack | Works on systems, weapons, and the RooM Engine pipeline |
| Group Size | 90,000+ members | Confirms the group is the studio's main community hub |
Why a Small Team Changes the Feedback Loop
Smaller studios read more of what you write, but they also triage faster. A bug report with a reproduction clip, a timestamp, and the live V0.x build number is dramatically more useful than a generic "gun feels off" message. The PoptartNoahh YouTube channel and X account both serve as secondary feedback surfaces, where short text reports often get acknowledged through community callouts. A well-structured TTK Testing feedback message has a real chance of being quoted in the next V0.x dev log.
The Three Official TTK Testing Feedback Channels
There are exactly three primary surfaces where the Sable Digital team accepts TTK Testing suggestions and bug reports. Each one has a specific purpose, and using the wrong channel is the most common reason player feedback never gets a response. Matching your report type to the right surface is the single highest-leverage move you can make.
Channel 1: Sable Digital Roblox Group
The Sable Digital official Roblox group page is the studio's central announcements and feedback hub. Forum threads inside the group are where the developers pinned roadmap details, server-test announcements, and changelogs for the V0.x cycle. Use this channel for general TTK Testing feedback, including balance impressions, mode requests, and minor visual bugs. The advantage is visibility: hundreds of testers see your post, which often leads to community-driven corroboration that strengthens your report.
Channel 2: DevForum Thread
The official TTK Testing DevForum thread is the most direct line to the Sable Digital development team. Posts here are written in a developer-facing tone and are treated as formal feature requests and structured bug reports. The DevForum is best reserved for technical feedback: reproducible exploits, netcode observations, weapons balance data, and scripting issues that the TTK Testing team can act on at the engine level. Community testing shared on the thread often feeds directly into the V0.x roadmap, which covers PVE Survival waves, doorkicker story Missions, PVP Quick Play, and large-scale Ground War.
Channel 3: Developer Social Accounts
The lead developer PoptartNoahh posts update showcases and short community callouts on the PoptartNoahh YouTube channel and on X at @poptartnoahh. These accounts are ideal for fast-moving feedback: live-server outages, patch-timing questions, and quick "did this break for anyone else?" reports. YouTube comments under the official update videos also act as a public ledger, because every V0.x build showcase, from the V0.01 Helmet Cam debut through the V0.04 Gunsmith Showcase, doubles as a feedback thread for the specific build it covers.
| Channel | Best For | Format | Response Style |
|---|---|---|---|
| Sable Digital Group | General feedback, balance, visuals | Forum post + media | Community + dev visibility |
| DevForum | Technical reports, feature requests | Long-form structured post | Dev-team triage |
| YouTube / X | Live-server bugs, patch timing | Short text or reply | Fast acknowledgements |
How to Write a TTK Testing Feedback Report That Gets Read
A good report reads like a small engineering document. The Sable Digital team processes dozens of community messages per V0.x cycle, and structured inputs are the ones that survive triage. The pattern below is what experienced testers use across the DevForum and the Sable Digital group threads.
Anatomy of a Strong Bug Report
Start with a one-line summary that names the weapon, mode, and V0.x build. Follow with reproduction steps that another player can run in under a minute. Attach a clip or screenshot whenever possible, because the V0.x live server changes weekly and the team often needs visual confirmation to reproduce edge cases. End with expected versus actual behavior so the developer can classify the report as a balance issue, a netcode issue, or a true bug.
-
Build number and mode (for example, V0.09, Ground War)
-
Weapon, attachment, or system involved
-
Reproduction steps in numbered order
-
Expected behavior versus observed behavior
-
Clip or screenshot with a visible HUD
-
Frequency (always, sometimes, one-time)
Anatomy of a Strong Suggestion
Suggestions follow a different rhythm. Lead with the player problem you are trying to solve, then describe the smallest change that would address it. The TTK Testing team has repeatedly delivered small, targeted updates, including the V0.02 shotgun and map drop and the V0.03 pistol and flash grenade drop, so narrowly scoped suggestions have a real chance of being picked up. Avoid bundling five ideas into one post, because the developer almost always triages bundled ideas as a single lower-priority item.
V0.x Phase Feedback Priorities for the Sable Digital Team
The current V0.x phase is explicitly framed as a tuning window for time-to-kill, weapons handling, and mode viability. Knowing what the Sable Digital team is actively tuning helps you focus your TTK Testing suggestions on areas that are genuinely open for community input. According to the official DevForum thread, the V0.x roadmap covers co-op PVE Survival waves, linear story Missions with doorkicker mechanics, standard PVP Quick Play, large-scale objective Ground War, plus teams, spectating, launchers, and gunplay improvements.
| Mode | Tuning Focus | Best Feedback Type |
|---|---|---|
| PVE Survival Waves | Squad AI, spawn pacing | Difficulty curves, wave pacing |
| Story Missions | Doorkicker mechanics, level flow | Stealth balance, mission pacing |
| PVP Quick Play | Time-to-kill, weapon feel | TTK samples, recoil data |
| Ground War | Objective design, vehicle balance | Capture flow, spawn safety |
| Gunsmith (V0.04+) | Attachment combos, optics | Build viability reports |
TTK and Weapons Feel
The lead developer PoptartNoahh has used the DevForum thread to frame the game as a time-to-kill tuning test, which is why weapons feel is the single most appreciated category of TTK Testing feedback. The official Roblox game page pins Helmet Cam to the P key and recommends the Transparent Optics toggle for two-eyed aiming, which means the team is also actively tuning the optics and HUD layer. When you report a weapons-feel issue, include the optic setting, the attachment configuration, and a clip recorded with Helmet Cam off so the developer can isolate the recoil from the camera shake.
Modes, Teams, and Spectating
The roadmap lists teams, spectating, and launchers as upcoming V0.x priorities, which means feedback on team balance, spectator UX, and launcher weapon pacing is being actively collected. A well-timed TTK Testing suggestion about, for example, the Last Man Standing pacing or solo-mode behavior carries extra weight right now, because the testing phase explicitly invites community input on how these features should land. If you want to see how the mode ecosystem is shaping up, the TTK Testing testing phase mode guide walks through the current V0.x mode lineup and the solo/team split.
Common Mistakes When Submitting TTK Testing Feedback
Even experienced testers send reports that get ignored because of small structural mistakes. The patterns below are the ones the Sable Digital team and community veterans have flagged most often.
| Mistake | Why It Hurts | Better Approach |
|---|---|---|
| Reporting in the wrong channel | Bug reports in YouTube comments get buried | Match the channel to the report type |
| Skipping the V0.x build number | The dev team cannot reproduce without it | Always include the live build tag |
| Bundling five ideas in one post | Triage collapses bundled posts into one item | Split into one post per idea |
| No clip or screenshot | Reports are marked "needs evidence" | Attach a 15-second clip |
| Vague tone ("gun feels bad") | Subjective reports get deprioritized | Add TTK samples and recoil data |
Avoiding Platform Confusion
Some players assume TTK Testing has a standalone Discord or Steam page, but the game lives entirely on Roblox under the TTK Testing official game page. If you are hunting for the TTK Testing Discord official link, it does not exist as a primary channel; the Roblox group and the DevForum are the studio's two main surfaces. The PoptartNoahh YouTube channel and X account are the two verified social surfaces run by the actual lead developer, so any community server claiming to be "the official TTK Testing Discord" is fan-run and should be treated accordingly. For the studio's broader history and how the NC Software era connects to the current Sable Digital identity, the Sable Digital studio page covers the full lineage in detail.
Verifying That Your Feedback Reached the TTK Testing Team
Confirmation is a real part of the feedback loop. The Sable Digital team does not acknowledge every post, but there are reliable signals that your report landed.
-
Reply or reaction from PoptartNoahh or CanyonJack on the DevForum or group thread
-
Quote in a V0.x dev log on the official DevForum thread
-
Feature appearance in a future PoptartNoahh YouTube update showcase
-
Community corroboration in the Sable Digital group with matching clips
If none of these appear within a V0.x cycle, the report was likely read but deprioritized rather than missed. A polite bump post at the start of the next cycle, with the original report quoted, is the most effective way to bring it back into the queue. The lead developer's social accounts are also a fair place to ask whether a specific report was logged, and the PoptartNoahh X account regularly amplifies community callouts that include reproduction clips.
Frequently Asked Questions
Who is the developer of TTK Testing?
TTK Testing is developed by the Sable Digital team, previously known as NC Software, with PoptartNoahh serving as lead developer and CanyonJack as a core builder. The studio's verified Roblox group confirms the current branding, and both developers post regular updates through the lead's YouTube and X accounts.
Where do I submit a TTK Testing bug report?
Submit reproducible bugs on the official DevForum thread when they involve netcode, scripting, or weapons data, and on the Sable Digital Roblox group for general gameplay issues. Always include the V0.x build number, mode, and a short clip, because reports without evidence are typically deprioritized during the V0.x triage cycle.
What was the studio called before Sable Digital?
The studio previously operated under the name NC Software, which still appears in older credits, YouTube descriptions, and community posts. The current verified brand is Sable Digital, which is the only name that appears on the official Roblox group page and the lead developer's active social accounts today.
Does TTK Testing have an official Discord?
There is no official TTK Testing Discord listed on the studio's verified surfaces; the Sable Digital Roblox group, the DevForum thread, and the PoptartNoahh YouTube and X accounts are the only official feedback channels. Any community Discord server claiming official status is fan-run and should be treated as unofficial, even if it looks polished.
How long does it take for feedback to influence a build?
Feedback posted during an active V0.x cycle can shape the next minor build, because the Sable Digital team ships small targeted patches such as the V0.02 shotgun drop and the V0.04 Gunsmith Showcase. Larger structural changes tied to the roadmap, including PVE Survival, story Missions, and Ground War, typically take multiple V0.x cycles of consistent community input to land.