One Dubious Copyright Claim Knocked an Open-Source Game Off Google Play

Luanti vanished from Google Play without a malware scandal, privacy breach, or compromised update. The apparent trigger was far more mundane: a shaky copyright complaint that showed telltale signs of being written with AI.

That should worry anyone who distributes software through a platform they do not control.

A Bad Claim Was Enough to Remove a Real Project

Luanti, formerly known as Minetest, is an open-source voxel game engine. It lets users build their own games and servers, earning it the reductive but understandable nickname “free Minecraft.”

Google reportedly removed the app following a copyright complaint from DMCA Tracer. According to the project, the filing contained inaccurate descriptions and fabricated claims packaged in the polished, overconfident language common to AI-generated legal text.

The remarkable part is not that someone produced a bad complaint. Bad complaints are nothing new.

It is that the complaint worked.

A claimant generated a document, submitted it, and disrupted a distribution channel for software developed openly over many years. The project’s public source code and development history did not prevent the takedown.

Platforms Remove First and Ask Questions Later

Google receives copyright complaints at a scale that makes careful manual investigation expensive. Reviewing source code, commit histories, licenses, and competing ownership claims for every filing would require time and specialist knowledge.

So large platforms often default to remove first, appeal later.

From the platform’s perspective, this is rational risk management. Leaving potentially infringing material online can create legal exposure. Taking it down shifts the burden to the developer.

The incentives look very different from the developer’s side. A claimant can produce a convincing-looking notice in minutes. The accused must gather ownership records, write a counterclaim, navigate an opaque appeals process, and wait for someone—or some system—to respond.

The complaint is automated. The defense is still manual.

That imbalance matters even when an app eventually returns. A few days outside search results can mean lost users, broken update schedules, support headaches, and reputational damage. For an independent developer or volunteer-run project, that is not a minor inconvenience.

AI Has Made Abuse Cheap and Fast

False copyright complaints once required at least some effort. A bad actor had to research the target, invent a plausible rights claim, and draft something that resembled a legal document.

Generative AI has crushed that cost.

Give a model a project name, a few keywords, and the desired accusation, and it can produce authoritative-sounding prose almost instantly. The facts may be wrong. The tone will rarely show such humility.

Automated platform systems can make the problem worse by checking whether a complaint has the required fields and legal terminology before considering whether its underlying story makes sense. Once form outranks substance, the decisive factor is no longer how credible a lie is. It is how quickly the lie can enter the enforcement pipeline.

That creates an obvious abuse case. A competitor can temporarily suppress an app. A scammer can pressure a small developer. A serial complainant can impose hours of work at almost no cost to themselves.

This is denial-of-service by paperwork.

The Community Saw a Systemic Problem

A Hacker News discussion about the case reached 79 points and 18 comments on August 28. That is a small sample, not a scientific reading of developer opinion, but the concerns were consistent.

Some commenters raised the possibility that a knowingly false claimant could face legal consequences for interfering with a business relationship. Others framed the incident as corporate censorship disguised as good-faith copyright enforcement.

Both responses run into the same practical obstacle: open-source projects rarely have the resources to litigate. Identifying a claimant, establishing jurisdiction, and hiring counsel can cost far more than restoring an app is worth.

The person filing the complaint gets automation. The project challenging it gets discovery, legal bills, and a calendar full of unpaid work.

The Answer Is Accountability, Not Another AI Detector

Platforms will not solve this by adding a classifier that guesses whether a complaint was AI-generated. AI-written claims can be valid. Human-written claims can be fraudulent.

The process needs better incentives. Repeat false claimants should face meaningful penalties. Before removing established software, platforms should examine easy-to-check counterevidence such as public repositories, license records, and years of development history. When a takedown is wrong, restoration should be fast, transparent, and capable of repairing lost visibility.

Luanti may return to Google Play, and the incident may fade into open-source lore. But the underlying mechanism will remain: anyone can generate accusations at machine speed while developers must defend themselves at human speed.

The real question is not what AI can write. It is how much power platforms are willing to give those words before anyone checks whether they are true.