If You Found a Bug, Did You Help Make the Game? — Reading "The Room You Can't Leave Without Debugging"
If You Find an Anomaly, Don't Turn Back
On July 26, 2026, in a former school two minutes' walk from Iidabashi Station in Tokyo, an unusual indie game showcase took place. Its name: "Debug Shinai to Derarenai Heya" — The Room You Can't Leave Without Debugging. On entry, visitors received a "bug-collection stamp card." Playing games in development and reporting bugs or impressions to the developers earned them stickers; only by collecting a set number of stickers could they "escape" the classroom of the closed school.
The tagline was: "If you find an anomaly, don't turn back — report it." It reads as an almost word-for-word inversion of the rule of The Exit 8 — turn back when you find an anomaly. There, the anomaly was an omen to avoid; here, the anomaly is the deliverable to report. That inversion summarizes the whole design of the event in a single line.
What I want to think about is not the novelty of the event. It is the design that converted debugging — an act that could easily become unpaid labor — into a game where players can leave their mark on a work, and the question of whether that design actually works.
The Verifiable Facts
The organizer is Ad-Virtua Inc. (CEO Seitarō Mizuno). Planning and operations involved "Yuurinchi," a game developer who has exhibited at such events themselves, among others. The venue was a rental space in a former school building in Agebachō, Shinjuku, with twenty booths planned, centered on unreleased and in-development indie games. Admission was free for the first hundred who pre-registered, 500 yen at the door. Exhibiting cost 4,500 yen, first come, first served, with no jurying.
The reward design is graduated. Finding a bug earns a "bug-discovery sticker"; giving feedback short of a bug earns a "bug-report sticker." A set number completes the escape, and successful escapees receive a venue-exclusive sticker by illustrator Tsuchinoko Kizuchi. Report more, and the sticker rank rises — "Silver Debugger," "Gold Debugger." The day also included a talk by game-development YouTuber Hirohasu.
A classroom in a closed school (not the actual venue). The event took over classrooms in a former school building. Photo: Tomo (Wikimedia Commons / CC BY 2.0)
The hard post-event numbers — actual attendance, total play sessions, the number of bugs and impressions reported, and how many were new discoveries for the developers — have not been published at the time of writing (unverified). The reading below rests on primary pre-event sources and one exhibitor's post-event account.
Players Don't Tell the Truth at Demo Events
Yuurinchi, the planner, wrote frankly about the starting point in the announcement article. At game showcases, players rarely speak their minds. The person who says "that was fun" and quits after three minutes. The person who says "I loved it!" and then marks 3 out of 5 on the survey. The person who leaves without a word. The worry that an honest opinion might hurt the developer stops exactly the "real talk" developers want most.
If that diagnosis is right, what's needed is not a request for feedback but a mechanism that breaks the structure of reticence. The design puts bug-hunting at the premise of play. It creates a state where "anything goes" and invites every operation the imagination allows. The moment the pretext of a bug report exists, the player's role flips from "customer evaluating a work" to "person in charge of finding what's broken" — and honesty stops being rude. The design doesn't make opinions easier to voice; it makes voicing them a procedure of the game.
This recalls something from writing about game preservation: the structure by which work that institutions decline to do falls to largely unpaid volunteers. Left alone, debugging falls to the same side. "Have your work-in-progress inspected for free" is just a euphemism for extraction. The design invention of this event is to convert that labor, via stickers and an escape condition, into a game where players leave traces on the work. If a bug you reported is fixed in the release version, some part of that fix is yours — the stamp card looks like a device for making that sense of ownership visible on paper.
A playtest (not from this event). Letting people play an unfinished work is, for a developer, both a test and a gamble. Photo: włodi (Wikimedia Commons / CC BY-SA 2.0)
The Fear of "Bombing"
One more thing in the announcement stands out: the planner does not hide their fear. Past events they organized have run a cumulative deficit of nearly 300,000 yen. What scares them most, they write, is putting in all that time and money and having the event "bomb." The anxiety of showing an unfinished game in public and the anxiety of showing an unfinished event in public share the same structure here. The condition of participation — showing your work bugs and all — applied to the organizer too.
At least one firsthand exhibitor account from after the event can be confirmed. A developer who exhibited a space-exploration game noted the generous spacing of ten booths per classroom and a layout that made it easy to watch visitors play from the aisle, and recorded: "Being the first edition, I didn't know what kind of event it would be, but it turned out to be quite a good one." What this developer valued was not collecting bugs but "watching players' reactions to confirm the direction" of the game. The debugging framing being used, in practice, as a place to test direction — even this single case shows an interesting gap between the design and its actual use.
What We Don't Know Yet
Still, the counter-hypothesis deserves its place. An escape-game gimmick may increase play sessions without producing the deep feedback developers actually need. Sticker-motivated reports can be numerous and shallow. Surface bugs — typos, collision glitches — may surface while the root problems of a game's design never emerge from a three-minute session.
Verifying this requires post-event data: how many reports were already known versus new, which reports exhibitors adopted and which they declined and why, whether sticker rewards affected report quality. None of it is public at this point. Multiple pre-event articles exist, but no independent verification of the outcome has been found. So this article stops at reading the design. The verdict on whether the mechanism worked should be added once the numbers and testimony are out.
Building Doorways on Purpose
Even so, the design itself supports one claim. A few days ago, writing about a program that grows children into movie-theater audiences, I said that an audience left to grow on its own and an audience that enters through a doorway someone deliberately built are different things. What this event attempts looks like the game-development version of that doorway: opening, to players who only ever consumed finished products, an entrance into the time when a game is still being made. What happens routinely in overseas communities through early access and playtesting "has not taken deep root" in Japan — that was the organizer's framing of the problem.
Indie game showcases tend to refine themselves toward polish and instant legibility. The exhibitor quoted above wrote that today's handmade feel will likely fade as things grow more commercial. Against that current, this event inverted unfinishedness from a defect to hide into something close to a condition of participation — an attempt to raise a second axis besides polish. If you found a bug, did you help make the game? The answer is not in yet, but posing that question in the form of play is itself the achievement of a first edition.