Modding licences, and the day the takedown arrives

Most mod communities operate on permission that was never actually granted. Not stolen: simply never formalised, because the thing they are building on was released with an end-user licence that says nothing about what they are doing, and everyone proceeded on the reasonable assumption that nobody minds.

Usually nobody does. The interesting question is what happens on the day somebody does.

The permission that does not exist

A game's EULA is a licence to play. It is not a licence to redistribute assets, decompile binaries, host a modified server, or sell anything built on top.

Some studios publish a separate modding policy that grants exactly those things, and those communities are on solid ground. Most do not. What the majority of modding runs on is tolerance: a studio that has not objected, which is legally different from a studio that has agreed.

Tolerance is revocable and does not expire. A project that has run for eight years is not safer for having run for eight years; it is simply a project nobody has objected to for eight years.

Three things that reliably trigger objection

Money. A mod with a storefront attracts attention that the same mod given away does not. This is the single most common trigger, and it is why so many large modding ecosystems have an uneasy relationship with paid content.

Redistributing the game. A project that ships the base assets so people can play without owning the original has crossed a line every studio recognises. Shipping only the code and requiring the original files is the arrangement that survives.

Competing. A mod that offers what the studio is currently selling (a free version of a paid mode, a server for a game with paid servers) is the case where objection is a business decision rather than a legal one.

Projects that avoid all three usually run indefinitely. Projects that do one are usually fine. Doing two is where the letters arrive.

What a takedown actually looks like

Not a lawsuit. A hosting provider receives a notice, the repository or the download disappears, and the maintainer discovers it when somebody reports a broken link.

The damage is not legal exposure: it is that the artefact is gone from the place everybody got it from, and the community discovers that nobody kept a copy. That is the practical lesson and it is unromantic: the thing that survives a takedown is whatever people already downloaded.

Which is why a server running a mod should hold its own copy of every version it depends on. That is not defiance, it is the same reasoning as keeping the jars in your backups — an author's repository can vanish for entirely mundane reasons too.

The asymmetry nobody plans for

A studio can end a modding ecosystem with one email to a host. The ecosystem cannot do anything comparable in return, and has no standing to negotiate.

That asymmetry means the relationship is managed socially rather than contractually: modders avoid the triggers, studios avoid enforcing, and both sides understand an arrangement neither has written down. It works remarkably well and it is entirely dependent on the studio not changing hands.

Acquisitions are the actual risk. A new owner inherits no history of tolerance and frequently applies a policy uniformly, without knowing that a particular community existed.

Why the takedown usually arrives late

The thing that surprises people is the timing. A mod runs for three years, gets popular, and then the notice arrives, and the delay makes the action look arbitrary or malicious.

It is usually neither. Nobody at the studio was watching, because nothing was large enough to see. What changes is visibility: a video, a news article, a player count that crosses some threshold, or a commercial version of the same idea being planned internally. The mod did not become more infringing. It became noticeable.

That has a practical consequence for anybody building on somebody else's game. The period of being ignored is not evidence of permission, and it is longest precisely while the project is least worth defending. Growth is what converts an arrangement everybody tolerated into a decision somebody has to make, and by then the project has users, expectations, and frequently money moving through it.

The servers that handle this well are the ones that assumed it from the start: keeping the content separable, keeping a copy of everything, and not building anything they could not afford to lose.

What a server owner should take from this

Know which of your dependencies are on solid ground and which are on tolerance. A mod with an explicit permissive licence is a different kind of dependency from a mod whose legal status is "nobody has complained".

Keep local copies of everything you run. Know which of your resources are paid and escrowed, because those are the ones you cannot patch yourself when they break.

And understand that a modded server's lifespan has a ceiling set by somebody else's legal department, which is a genuinely unusual property for infrastructure to have, and one more reason the servers that last longest are the ones running on engines whose owners released them deliberately rather than on tolerance that could end on any given Tuesday.