Original editorial illustration by RealmList, generated for this article. This is artwork, not game footage or official promotional material.

Nobody picks a community realm expecting it to last forever. But "these things close eventually" is not a useful risk assessment, because the way a realm closes determines whether you get a warning or a Tuesday afternoon email.

In 2026 the scene learned that there are at least two distinct failure modes, and they leave completely different signs.

Two kinds of death

Legal death is what everyone plans for. Blizzard sues or sends a cease-and-desist, the operator settles, the servers go dark on a stated date. It is fast, public, and — in the way that matters to a player — orderly. You usually get weeks of notice.

Cost death is the one people miss. There is no legal action, no dispute, no villain. The operator simply runs out of money or free time, and the realm stops. Project Alterac, a small phased WotLK project tracked since late August, closed on September 15 and said so plainly: the operator cited out-of-pocket costs since an incident with the CDN bill the previous month, no free time left to keep chasing problems, and — notably — named the WoW: Forever beta starting two days later as a factor in how he could spend his time. No legal pressure appears anywhere in the farewell post.

That last detail is the story of the year for community realms, and it is not a legal story at all. Blizzard's biggest competitive move against private servers in 2026 was not a lawsuit. It was shipping a first-party Classic+ beta and letting the audience do the rest.

The legal wave, in order

For context, the legal track through the last twelve months:

Four recognisable names closed in roughly twelve months, and the reasons are not uniform. That distinction is the thing to carry into your next realm choice.

Signals worth checking before you invest

None of these are guarantees. All of them are cheaper to check before you level a character than after.

1. Who pays, and how. A project with a stated funding model — donations, cosmetic-only shops, a no-pay-to-win rule, a public cost breakdown — is telling you it has thought about the invoice. Silence is the risk. A single operator paying hosting out of pocket is the exposed cohort; Project Alterac was exactly that, and its stated reason was financial, not legal.

2. Whether progression was ever monetised. This cuts both ways. Donation systems that convert to in-game advantage were the concrete commercial evidence cited in Blizzard's complaints against the largest projects, which makes them a legal liability. They were also, in the same projects, the revenue that kept the servers running. A project that sells nothing is safer legally and thinner financially.

3. How many people are actually on the team. "No free time left" is a one-person problem. Look for named staff, public GM recruitment, a changelog written by more than one voice, and how quickly bug reports get responses. A team of one that also holds a job is one bad week from closure.

4. Whether the content exists anywhere else. This is the most durable question in the entire scene. The projects that survived 2026 are the ones offering something Blizzard will not or cannot ship — classless character builds, fully custom world content, custom Mythic+ systems, seasonal five-man formats. If your realm is a relatively faithful reproduction of an expansion Blizzard currently sells or has announced, you are competing with the original on its turf, and the audience-drain argument does the work the lawyers used to.

5. What the client is built on. Successor projects built on a leaked core carry inherited legal risk on top of the usual risks. That does not make them unusable; it makes them a different category of bet than a project running its own clean-room code.

6. Whether there is an exit plan you can use. Does the project let you export character data, publish an archive, or hand its database to the community? Some do. Assume the answer is no unless you have seen it happen once.

What the community does instead

The most striking thing about the 2026 closures is that the response was preservation, not replacement.

When Ascension closed, its community opened an archive effort on September 15 to pull WDB and addon data out of former players' game installs before that data decayed — feeding a 21-class port to a widely used open-source core and a reference database that already holds enchant routes and class trees. Earlier in the year, the Turtle WoW shutdown produced a source leak and a successor federation, with independent projects carrying the 1.17 content line forward.

That reflex is now established practice, and it is worth copying. The players who kept their installs, their addon folders and their screenshots were the ones who could help rebuild; the ones who deleted everything on the last day could not.

A working checklist

Treat any community realm as leased, not owned. Practically:

• Keep a complete copy of your client folder, addon set and any custom patches locally — not only in the launcher's managed directory.
• Screenshot or export anything you would want to remember. Character sheets, achievement lists, guild rosters.
• Do not buy cosmetics, mounts or convenience items whose value depends on the server still existing.
• Keep credentials unique per realm, as always.
• Before you invest serious time, ask the two questions from this article that you can actually answer: who is paying for this next month, and what does this project have that Blizzard will never ship.
• If a realm you play on does close, hold your files for a while. Communities archive, and the data you have may be the only copy.