He Asked Players Why His Game Was Failing. Then He Didn't Quit.

The Ask That Could Have Gone Either Way

On August 14, a Japanese indie developer named Daikoku Choujou — who goes by the handle Daikoku Choujou-sensei — posted something unusual on X. He told his followers he was thinking of quitting game development. But before he walked away, he wanted one last honest answer to a question most developers dread asking out loud: why isn’t your game selling?

He wasn’t fishing for compliments. He explicitly invited harsh criticism. The game in question was Bye Bye Survivor!, a roguelite action title he had released just three months earlier on May 20 for PC through BOOTH and DLsite. It was a straightforward concept — control a character who auto-attacks while you dodge waves of slimes, charge up a powerful attack by holding the right mouse button, and defend crystals from overwhelming numbers. Simple enough on paper.

What happened next, however, is what makes this worth watching.

The Feedback Wasn’t Gentle

The responses poured in. And they were blunt.

Players said the game’s UI and camera angle created visual clutter that made it hard to understand what was happening on screen — even from gameplay videos, the core loop wasn’t obvious. Others noted that the satisfying feeling of clearing hordes of enemies, which is supposedly the game’s main draw, simply didn’t translate. Multiple comments asked the same thing: what exactly makes this fun? Where’s the originality?

Then came the broader industry critique. Several respondents pointed out that Bye Bye Survivor! was a family-friendly title being sold on BOOTH and DLsite — platforms known for adult-oriented content and doujin works — when it might have found a better audience on Steam or itch.io. The mismatch between the game’s tone and its marketplace was a red flag to many players.

Not everyone was negative. Some praised the game’s cute character designs and world-building, telling Daikoku Choujou that with enough iteration and refinement, the title had real potential. The feedback spanned everything from visual design to distribution strategy to fundamental game feel.

For a developer about to quit, that kind of attention — raw, unsolicited, and largely critical — could have been the final straw. Or it could have been the thing that changed his mind.

What Happened Next Separates This From a Cautionary Tale

Daikoku Choujou didn’t delete his X account. He didn’t ignore the feedback. He posted that he had received more advice than he expected — covering not just the game itself but its marketing and distribution — and that he had been missing perspectives he couldn’t see on his own. He said he wanted to use the criticism, including the harshest comments, as fuel. And he said he would reconsider his future in development.

Nine days later, on August 25, Bye Bye Survivor! received version 1.1.0. The patch notes confirmed changes to the UI and camera angles — directly addressing two of the most common complaints. Bug fixes and balance adjustments followed. On August 29, he announced the update on X with a modest claim: “I think it’s easier to play now.”

Then, on August 30, he did something most developers who threaten to quit never do. He started promoting the game again — specifically spotlighting the charge attack mechanic that players had said failed to deliver satisfaction. He returned to the drawing board and the market simultaneously.

Why This Matters Beyond One Developer’s Story

The Japanese indie game scene operates differently from its Western counterpart in ways that aren’t always visible to outside observers. Platforms like BOOTH and DLsite serve as primary distribution channels for independent creators, carrying a user base and cultural context that Steam’s global audience doesn’t replicate. A family-friendly action game listed on those platforms may be invisible to the wrong crowd — or worse, misunderstood by the right one.

Daikoku Choujou’s experience highlights a structural problem that affects dozens of small Japanese studios: the gap between where indie games are hosted and who actually buys them. Steam’s discovery algorithms, review systems, and community features create a completely different market dynamic than BOOTH or DLsite. The suggestion to relocate wasn’t just tactical advice — it was a diagnosis of a distribution mismatch that many Japanese indie devs face without the vocabulary to articulate it.

What’s remarkable is the willingness to absorb public criticism openly. In Western gaming culture, developer-to-player feedback loops tend to play out behind closed doors or in sanitized community manager responses. Daikoku Choujou’s approach — publicly soliciting brutal honesty and then visibly acting on it — is closer to a craft tradition than a modern game industry practice. It mirrors how doujin circle leaders have long operated in Comiket-adjacent spaces: put the work out, take the critique, improve, repeat. The difference here is that the stakes are a full commercial release, not a one-day event.

The Bigger Picture for Small Studios

The timing matters. By mid-August, Bye Bye Survivor! had been on sale for roughly three months — long enough to gather organic reviews and player data, but early enough that course correction was still possible. Many indie developers never reach this inflection point because they lack the bandwidth to process feedback after launch. They either double down silently or walk away entirely.

Daikoku Choujou chose a third path that deserves attention from anyone running a small team or a solo operation: treat public criticism as a design resource rather than a personal attack. The resulting update addressed concrete issues — camera, UI, balance — while the follow-up promotional push signaled a commitment to staying in the space.

The demo remains available on BOOTH and DLsite. Whether the version 1.1.0 changes and renewed visibility will shift sales trajectory is impossible to predict. But the approach itself — asking hard questions, listening publicly, acting visibly — is a model that extends far beyond one game.

In an industry where burnout drives developers out constantly, the decision to stay after hearing why you’re failing is not just personal resilience. It’s a statement about how indie creators can survive when they stop treating feedback as threat and start treating it as architecture.