If you run a personal Minecraft server for your family the way I do, you may have seen the recent headlines: during a hearing on California’s Protect Our Games Act, a lobbyist for the Entertainment Software Association (ESA) told lawmakers that private Minecraft servers are “illegal,” “not in any way affiliated with Microsoft,” and effectively a form of piracy. The bill — which would have required publishers to provide tools for community-run servers after a game’s official servers shut down — failed to advance out of committee.
I want to push back on the ESA’s framing, and then make the case for something the debate keeps skipping over: self-hosted servers, and Bedrock’s official Linux server software in particular, are one of the best low-stakes ways to introduce a kid to Linux, networking, and system administration.
The “illegal” claim doesn’t hold up to scrutiny
Start with the plain facts. Mojang and Microsoft distribute the Bedrock Dedicated Server software directly from the official Minecraft website, free of charge, specifically so people can run their own servers. Calling that setup “piracy” is a strange way to describe using a tool the publisher built and hands out itself.
The ESA’s actual legal position is narrower than the soundbite suggests, and worth taking seriously on its own terms: private servers, they argue, still operate under Microsoft’s intellectual property, Microsoft has not relinquished its rights over that IP, and the company could in principle revoke the ability to self-host at any time. That’s a coherent legal point about licensing and enforcement discretion — it is not the same as the servers being illegal today. Millions of people have run private Minecraft, Terraria, and similar servers for over a decade with explicit publisher tooling and no enforcement action. “The publisher retains the right to shut this down eventually” and “this is currently unlawful” are two very different claims, and the ESA’s testimony blurred them for legislative effect.
The safety argument is a separate thread, and it’s fair as far as it goes — a self-hosted server run by a parent for their kid genuinely doesn’t have Microsoft’s moderation layer, so that responsibility falls on you. But that’s an argument for parental oversight, not an argument that the practice is unlawful. Plenty of things adults are legally free to do carry more risk without an intermediary watching — that alone doesn’t make them illegal, just something to supervise.
What the hearing was really about is the underlying Stop Killing Games proposal: should publishers be legally required to hand over server tools when they discontinue a game? That’s a genuine, contestable policy question with real arguments on both sides — publishers worry about liability, ongoing IP exposure, and supporting infrastructure they no longer control; preservationists worry about games becoming permanently unplayable the moment a company flips a switch. Reasonable people land differently on it. But the “illegal” framing wasn’t really an argument in that debate — it was a talking point that overstated the current legal reality to make the underlying policy fight look already settled.
The upside nobody’s talking about: Bedrock’s Linux server is a genuinely great way to teach kids Linux
Here’s the part I think gets lost in the “is it legal” argument: setting up a personal Bedrock Dedicated Server on Linux is one of the most motivating, low-risk on-ramps into real computing that a kid can get.
A few reasons this works so well:
- The payoff is immediate and personal. Unlike a generic “learn the terminal” tutorial, the reward for getting
bedrock_serverrunning on Ubuntu isn’t an abstract skill — it’s a world your kid and their friends can log into tonight. That motivation carries them through frustration that a worksheet never would. - It touches real system administration, not toy exercises. Getting a Bedrock server running teaches package management, file permissions, editing a config file (
server.properties), opening a port, and understanding IP addresses and networking basics — all real skills, just scoped down to a project a kid actually cares about. - Mistakes are cheap. Break the server, corrupt a world file, misconfigure a port — nothing is lost that a backup or a fresh download can’t fix. That’s exactly the kind of low-stakes environment where kids should be encouraged to poke around and break things.
- It scales with curiosity. A basic server on a spare machine or a Raspberry Pi is the whole lesson for a while. But the same setup naturally opens doors to the next steps — scheduling automatic backups with cron, monitoring resource usage, maybe eventually standing up a second service alongside it. Kids who get hooked tend to ask “what else can this machine do?” on their own.
- It’s the opposite of a walled garden. A lot of kids’ first computing experience is entirely inside polished apps where the underlying machine is invisible. Running your own server flips that — suddenly there’s a terminal, a filesystem, and a process that your kid is responsible for keeping alive.
None of this requires expensive hardware. An old laptop, a Raspberry Pi, or a cheap secondhand mini PC is plenty to host a small private world for a handful of players, which makes it an accessible weekend project rather than an investment.
Where that leaves us
The ESA’s “illegal” line generated headlines, but it’s a shakier legal claim than it sounded like in the room, and it sidesteps a much more interesting reality: the same official server software the lobbying group was disparaging is quietly one of the best tools available for getting a kid genuinely comfortable with Linux. If you’re already running a personal server, that’s not something to be defensive about — it’s worth treating as the hands-on computer science lesson it already is.
