Valve Blocks Indie Developer’s Game Demo for Allegedly Using Their Own IP—And Now They’re Stuck in Bureaucratic Limbo

San Francisco, USA — In a bizarre twist of automated copyright enforcement gone awry, Valve’s Steam platform has blocked the release of an indie developer’s demo for allegedly violating copyright—using assets the developer themselves created. The situation, now widely discussed in gaming circles, highlights the growing pains of automated content moderation systems and the disproportionate impact they have on small studios.

The developer, Daikichi (a pseudonym commonly used by independent creators), was developing Wired Tokyo 2007, a game that included visual references to their own board game, Dinostone. Despite clear evidence that the IP belonged to the same creator, Steam’s automated systems flagged the demo as a copyright violation, halting its release. The demo, listed as “Coming soon” on Steam, remains inaccessible while Valve demands bureaucratic proof of ownership.

This isn’t an isolated incident. Automated copyright enforcement systems, while designed to protect intellectual property, have increasingly ensnared innocent creators—particularly indie developers with limited resources to appeal decisions. The case raises critical questions about the fairness of these systems and the burden they place on small studios during crucial launch windows.

How Did This Happen?

Daikichi’s predicament began when Steam’s automated copyright detection system flagged Wired Tokyo 2007 for including visual elements from Dinostone, a board game the developer created in 2007. The system, designed to prevent third-party IP violations, treated the assets as if they belonged to an external entity—despite the developer being the sole copyright holder.

In a post on X (Twitter), Daikichi explained the absurdity of the situation:

“The motif of a board game I personally created in the past, placed within the game Wired Tokyo 2007, is getting caught by Steam’s side as third-party intellectual property.”

Valve’s response was equally perplexing. Rather than recognizing Daikichi as the rightful owner, the platform demanded:

• A documented agreement licensing the images within their own game, or
• A letter of authorization from an attorney—despite the developer being the sole creator.

In a follow-up post, Daikichi described the situation as a “papers, please!” moment, adding:

“It’s not a third party. It’s just me wanting to use my own intellectual property rights myself. I have no idea what the meaning of this is at all.”

The developer’s solution? A self-signed letter authorizing themselves to use their own work—a move that, while creative, left Valve in an awkward position. The platform now faces an impossible choice: accept a letter from the developer to themselves or continue blocking the demo indefinitely.

Why This Matters for Indie Developers

Daikichi’s story is far from unique. Automated copyright enforcement systems, while well-intentioned, have repeatedly ensnared innocent creators, particularly indie developers who lack the resources to navigate bureaucratic appeals. The Electronic Frontier Foundation (EFF) has long warned about the risks of over-automation in content moderation, arguing that:

“Automated systems prioritize speed over accuracy, often resulting in false positives that disproportionately harm small creators.”

For indie developers, the stakes are high. A delayed or blocked demo can mean lost visibility, missed revenue opportunities, and damaged credibility. In Daikichi’s case, the demo—originally promised for release—remains stuck in Valve’s review process, leaving the developer in limbo.

Valve has not publicly commented on the specifics of this case, but the incident aligns with broader criticisms of Steam’s copyright enforcement policies. The platform’s reliance on automated systems has led to repeated controversies, including:

• False copyright strikes against games using public domain assets.
• Delisted titles due to unclear IP ownership disputes.
• Indie developers forced to spend weeks (or months) appealing decisions.

What Happens Next?

As of this writing, Daikichi’s demo remains blocked while Valve reviews their self-authorized “license.” The developer has not confirmed whether the demo will proceed, but their latest posts suggest they are continuing to engage with Valve’s review team.

Industry observers are watching closely, as this case could set a precedent for how Steam handles self-owned IP disputes. Possible outcomes include:

• Approval: Valve accepts the self-authorized license, allowing the demo to release.
• Rejection: Valve declines the documentation, leaving the demo indefinitely blocked.
• Policy Change: Valve revises its automated systems to better handle self-owned IP cases.

Regardless of the outcome, this incident underscores the need for clearer guidelines around automated copyright enforcement—especially for indie developers who often operate with limited resources.

How Indie Developers Can Protect Themselves

For independent creators, the risks of automated takedowns are real. Here are steps developers can take to minimize disruptions:

• Document ownership: Keep clear records of all creative assets, including creation dates and original designs.
• Use watermarks: Embed subtle, unique identifiers in assets to prove ownership if disputes arise.
• Engage early: If possible, communicate directly with platform support before submitting content.
• Know your rights: Familiarize yourself with U.S. Copyright law or equivalent regulations in your region.
• Seek legal advice: For high-stakes cases, consulting an IP attorney can help navigate platform disputes.