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

When Turtle WoW went dark on May 15, 2026 under a permanent injunction, it would have been reasonable to assume its eight-year Vanilla+ experiment — the Mysteries of Azeroth expansion, playable Goblins and High Elves, rebuilt Classic specs — simply ended. Four months later, the opposite has happened: Turtle's code, client and community have fractured into a cluster of successor projects, each carrying a piece of the original forward. At the same time, this week's reports suggest the legal pressure that killed the parent has not stopped at its borders.

Ravencraft: the 1.18.1 reupload

The most established successor is Ravencraft (ravencraft.io), which per its community resource page is effectively a reupload of Turtle WoW 1.18.1, live since August 22. That means the complete Mysteries of Azeroth content: 10 new dungeons, 11 new zones, 4 new raids, and playable Goblins and High Elves on the 1.12 client. Existing Turtle clients can connect by simply repointing realmlist.wtf to logon.ravencraft.io. The project inherited the healthy parts of Turtle's ecosystem too — population trackers, a community database viewer, AtlasLoot-style tooling and the well-documented addon stack (pfQuest-Turtle, Bagshui, pfUI with Nampower/ClassicAPI/SuperWoW). Community trackers currently place its Medivh realm among the more active Vanilla+ populations, though independent population figures for small realms are always worth double-checking before committing.

OctoWoW and Capybara: the same code, different audiences

Two other projects built on Turtle's leaked builds run in parallel. OctoWoW (octowow.st) targets a North American and European audience using a leak of Turtle 1.17.2, with the team datamining 1.18.1 content to restore it — a genuinely odd arrangement in which the successor is reverse-engineering its own parent. Notably, its founders promote a "zero trust" structure: anonymous volunteers who do not know each other's identities, explicitly so that no single cease-and-desist letter can switch everything off at once. Capybara (capycraft.io) serves the Chinese-language Vanilla+ audience with a multilingual realm. Alongside these, Faebright offers a different flavor — TBC content running on the WotLK client as an RP-PvE realm — showing the successor wave is not purely a Turtle phenomenon.

The enforcement tail: reports of a C&D against OctoWoW

Here the sourcing gets thinner and the caveat matters. Community forum reports this week claim OctoWoW's Discord was deleted following a cease-and-desist from Blizzard, though the server itself was still listed as online in the same threads. We are treating this as unverified: no official statement from Blizzard or the project exists at the time of writing, and private-server Discord takedowns have historically preceded — but not guaranteed — full closures. The pattern from this year (Stormforge closed on a C&D alone; Turtle fought and lost; Ascension settled) shows enforcement scales with a project's prominence. If the report is accurate, it would be the first known action against a Turtle successor rather than an original operation.

The bigger picture: the scene regenerates faster than it can be closed

Zoom out and the week's picture is consistent with what we wrote after the Ascension shutdown: the survivors are not retreating, they are iterating. Beyond the Turtle lineage, Emberveil has launched an early alpha of "Unreal Azeroth" — Vanilla rebuilt in Unreal Engine 5 — pointing at where technical ambition is heading next. Meanwhile the blizzlike center of gravity holds: Warmane, Firestorm, ChromieCraft and Whitemane (whose Frostmourne realm launches September 19) continue their progression schedules undisturbed.

For players, three practical takeaways: successor projects of closed servers carry inherited legal risk on top of the usual risks; verify a project's current status through its own live channels rather than third-party listings; and our standing advice on unique credentials and not treating any realm as permanent infrastructure applies doubly here. Our guide to evaluating a community realm covers the full checklist.