Classic Forever 1.60.1 server project reaches the beta, with launcher risk

September 25, 2026

Comprehensive Status Tracker, Emulation History & Development Directory

← All news

By WoW Tracker Editorial ·

A Reddit post describes a personal Classic Forever server running the 1.60.1 beta client. The author says it is capped at level 20, follows the official beta zone-for-zone, has no donations or shop, and gives access through a shared account and launcher after DM approval.

The project has a public first-party repository and status feed. The feed reported both login and world online during this crawl, and a direct port check found both service ports reachable. The repository publishes source, release metadata, SHA-256 files, and supported client builds. It does not publish a player count or open registration.

Security warning

The launcher is not a normal game installer. Its source says it changes the beta client's configuration and writes a server public key into the client process memory. Releases are unsigned, and the project warns that antivirus software may flag the executable. The Reddit thread also contains reports of an earlier Google Drive batch file, which was not independently verified.

Treat this as a high-risk development server. Use the source repository for review only, verify any binary independently, and do not treat shared credentials or an unsigned launcher as safe by default. Tracker listing stays at dev because access is invite-only and the project is still being assembled.

Update September 26: the project has since shipped a verifiable build chain. Launcher v1.1.2 publishes a GitHub Actions build log, the exact source commit, a SHA-256 in the release notes, and a .sha256 sidecar. I downloaded the binary, hashed it, and it matches the published value byte for byte across four independent signals. I also read the patcher source directly and confirmed the write is 32 bytes of key data into the heap only, guarded by a full key-store validation before and after. The binary is still unsigned, still writes to another process's memory, and access is still by shared account, so the risk profile is unchanged in kind. Full detail, including what I could not verify, in the launcher build verification post.

Update November 4, 2026: the original defexnicolas/wow-classic-launcher repository and its status feed have been removed, so the links in this post no longer resolve. The findings below are the record of the September 25 reading and cannot be re-checked against the original source. The tracker entry stays dev with the removal noted and its current status unverified.

SOURCES: Reddit discovery thread and the public launcher repository (since removed, see the update above). The repository linked to its first-party status feed, which is also gone.