{width="1536" height="1024" loading="lazy"}

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

Emberveil — the vanilla 1.12.1 realm on a custom Unreal Engine 5 client that launched August 15 — has published its one-month report, and it is one of the more transparent post-launch retrospectives this corner of the private server scene has produced. The numbers are specific, the team names its own failures, and the omissions are at least as interesting as the statistics.

The month in numbers

The headline statistics from the official report:

The team is disarmingly honest about the crash-fix treadmill: "Every single patch in that range had 'crash fixes' in the notes. Every one. We are not especially proud of that, but we are proud of the direction." Many of the bugs, they note, had been "lurking for nearly twenty years" in the original 1.12 client and core — the price of rehosting a twenty-year-old game on a new engine.

What the report does not contain is any concurrency or population figure. For a project whose pitch is a hand-tuned single realm, that omission matters: you can audit its engineering, but not its health. We have covered before how population claims on private servers need verification — Emberveil's case is the inverse problem, a server declining to make a claim at all. Treat any third-party population figure for it as unverified.

What actually shipped in month one

The feature list is aggressive for thirty days:

• Dungeon Finder and Group Browser are live — in-world queueing that does not require sitting in a capital. (Teleport-to-dungeon is planned but not yet implemented.)
• Database browser and Armory at database.emberveil.org, with 3D model previews and per-character lookups.
• An addon directory and Lua API documentation, including roughly 20 new API functions (PlaySoundFile, GetPlayerFacing, wipe, and more) — meaningful because UE5 client projects usually strand the addon ecosystem that makes vanilla playable.
• Launcher 1.9.6 gained an AddOns Manager (install/update/remove verified addons without touching manual installs), multilingual patch notes, live server status, and a one-click bug report button.
• A title system for challenge-mode completions, a website-based unstuck tool, and a pile of new GM tooling.

The fix list runs from the mundane to the historically loaded: fear and charm effects no longer desync characters; control returns correctly after Eyes of the Beast and Mind Control; shaman totems work; Power Word: Shield can be self-cast outside a raid; other players' movement is visibly smoother; mailed attachments no longer delete sibling mail; Windows 7 support is restored; HighDPI rendering is correct; and the client supports Chinese pinyin input and Unicode symbols — an obvious nod to the server's multilingual ambitions (the site ships in English, Spanish, Russian, and Simplified Chinese).

One fix reframes the whole project: the progression system was reworked because it had been wrongly gating too much content. Phases now restrict only raids, world bosses, and world events — the server runs the complete 1.12 game beneath them. That is the correct reading of "progressive release": pacing, not castration.

The Android client is real, and walled off

The report's biggest reveal: Emberveil runs on Android as a full game client — combat, quests, chat, proximity voice, and the auction house — not a companion app. It began, per the team, as a bet that the client could run on a pocket device.

The guardrails are unusually careful. This is a closed beta: no public download, invites not yet sent, and the first wave is deliberately tiny. Testers play on a separate test realm with fresh characters, no data carries in or out, and everything is wiped afterward — "We would rather find out the hard way that a build eats your gold somewhere the gold does not matter." Signups are open at emberveil.org/mobile-beta.

Context: why this report is worth reading

Emberveil occupies the same "vanilla, but the client is new" lane as other UE5 experiments, and its first month overlapped with the most crowded news window the vanilla private server scene has had in years — Forever's beta, Frostmourne's launch, and the ongoing Turtle successor ecosystem. Against that backdrop, a nine-hour DDoS absorbed without downtime mirrors what Frostmourne faced on its own launch night, and suggests DDoS mitigation is now table stakes for any high-visibility launch.

The report's closing line — "It has stopped feeling like we are building this for you. It feels like we are building it with you" — is the kind of thing every project says. The difference here is the receipts: a public bug count, versioned client revisions, and named next steps (Android invites, phase unlocks, continued patch cadence). What remains unproven is the only number that was withheld.