What's Actually Legal When You Build in Someone Else's World

Filed by Gertrude, UGC Desk. I'll open the way I always do: with a disclaimer, because it's the single most important sentence in this piece.

This is not legal advice, and I am not your lawyer. What follows is a plain-language map of the territory — the four ideas that come up every time a creator builds inside a world someone else owns. A map is not a guide. If real money, a real business, or a real cease-and-desist is on the table, close this article and go talk to an actual lawyer in your actual country. I mean that. Now — the territory.

The creator's oldest question is also the murkiest: I want to build on top of something I didn't make. Am I allowed? Mods, fan servers, custom maps, remixing worlds that belong to a studio. The honest answer is "it depends, and here's what it depends on." Four things. I'll number them.

1. Ownership: it isn't yours, and that's the starting line

Begin from the uncomfortable truth. The world, the characters, the art, the code — if a studio made it, they own it, and your love for it grants you exactly zero rights to it. Being a fan is not a license. Building something wonderful on top of their thing doesn't make your part yours in a way that overrides their part. Everything else — every permission, every tolerated practice, every "but everyone does it" — is the owner choosing not to stop you, which is very different from you having a right. Internalize the starting line and the rest makes sense.

2. The license you already agreed to: read the EULA, because you signed it

Here is the clause nobody reads and everybody is bound by: the End User License Agreement, the wall of text you clicked past to install the game. It frequently says, in plain terms, what you may and may not do with mods, tools, and creations. Some studios explicitly permit single-player mods and even celebrate them; many draw a hard line at anything touching online play, cheating, or reverse-engineering. You didn't just buy a game — you entered an agreement, and it already answered a lot of your questions before you thought to ask them. Read the EULA for the specific world you're building in. It is the first and most authoritative source, and it costs you nothing but the discomfort of actually reading it.

3. Fair use: real, narrow, and not the shield people think it is

People invoke "fair use" like a magic word, and it is neither magic nor a word you get to decide alone. It's a genuine legal doctrine — but it is narrow, fact-specific, and decided by courts, not by creators. Commentary, criticism, parody, transformation, education lean toward fair use; wholesale copying, or anything that competes with the original, leans hard against it. And it varies enormously by country — defensible in one place, plain infringement in another. "It's fair use" is a hope, not a guarantee, and treating it as armor is how creators walk confidently into trouble. Know it exists. Don't mistake it for a permission slip you issued yourself.

4. The takedown: the tool owners actually use

In practice, the owner's everyday weapon isn't a lawsuit — it's the takedown: a formal request that a platform remove your work, sometimes with a legal notice attached. Studios use it selectively, tolerating a thriving mod and fan scene for years — until something crosses their line (usually money, online systems, or brand-damaging content), and then the notices arrive. The pattern is consistent enough to state plainly: single-player mods and fan love tend to be tolerated-to-celebrated; anything touching online play, cheating, commercial use, or reverse-engineering draws the heat. The takedown is a signal, not the end of the world — but building a business on someone else's IP without their blessing means building on ground the owner can reclaim with one email.

So — am I allowed? The honest map reads: you're standing on land you don't own, bound by a license you already signed, holding a "fair use" umbrella that may or may not be open, and the owner has a takedown button they'll press when you cross a line clearer than you'd like to admit. That's not meant to scare you off. Plenty of the best creative work in games lives in exactly this territory, safely, for years. It's meant to make you literate — build with your eyes open, respect the EULA, keep commercial ambitions and online-system meddling out of the danger zone, and know the difference between "tolerated" and "yours."

And when it matters, go find a real lawyer. Because I read the fine print for a living, and even I know the difference between reading the map and being the guide.