Multiclass Server · System Guide
Launcher Enforcement
The server can require players to launch through the NMS Launcher — guaranteeing the correct client, the correct server, and the 4 GB patch. Anyone who doesn't is gently held in the Bazaar with instructions, never disconnected and never crashed.
01What it does
Every login, enforcement checks three things: that you came through the NMS Launcher (which keeps your client patched), that your client is set for the right server (Test or Live), and that the 4 GB patch is installed.
Players who fall short are held in the Bazaar — you can still buy and sell from player traders, but you can't leave until it's fixed. It's a hold, not a punishment: no disconnects, no kick to character select, no crashes. Advanced players who insist on skipping the launcher can opt their account out and take responsibility for their own client.
02For players
The easy way — just use the NMS Launcher
Launch through the NMS Launcher every time. It patches your client, sets the right server, applies the 4 GB patch, and starts the game. Do this and you'll never see a single message below.
If you start the game directly
With enforcement on, starting EverQuest without the launcher holds you in the Bazaar until you fix one of these:
| Reason | What it means | Fix |
|---|---|---|
| No launcher | You didn't come through the NMS Launcher | Close EQ, run the launcher, click PLAY |
| Wrong server | Your client is set for the other server (Test / Live) | Run the launcher, pick the correct server |
| No 4GB patch | Your eqgame.exe isn't 4GB-patched | Run the launcher, apply the 4GB patch |
The hold repeats a red reminder while you're in the Bazaar. Guides and GMs are exempt from all of this.
Opting out — #optout / #optin
Don't want to use the launcher (for example, you auto-login with MQ2)? Opt your whole account out. Type
#optout and you'll get a clickable agreement:
By opting out you agree to run the NMS Launcher and check for a new patch before reporting any bug or asking a GM for help. If a patch is available, install it first. Opted-out accounts that skip this may be denied support.
Remember: run the NMS Launcher and check for a new patch before reporting a bug. Type
#optin to turn enforcement back on.Warnings you may still see
Even opted out, the game still warns you — in red — about problems it can detect. These don't hold you; they're heads-ups:
03For Guides & GMs
Status 20+ can view and manage any player's opt-out with #check.
| Command | What it does |
|---|---|
| #check <name> | Show opt-out status, revoked status, and the last client report |
| #check optout <name> | Opt an account out on their behalf |
| #check optin <name> | Opt an account back in |
| #check revoke <name> | Ban an account from opting out, and force enforcement back on |
| #check unrevoke <name> | Lift the opt-out ban |
The "last seen" line is the support tool — launcher / channel / 4GB at a glance when someone reports a problem.
That report line is how you triage an opted-out player's complaint: if it's a wrong-server or missing-4GB
issue, you can point at their own opt-out agreement. Revoke is the abuse
hammer — it clears their opt-out, forces enforcement back on, and blocks them from opting out again
until a GM runs #check unrevoke.
04Operator reference
- Master switch: the rule
Custom:RequireLauncher(defaultfalse). When off, the whole system is dormant — other servers are unaffected. - Channel:
Custom:IsTestServermarks a server Test (true) or Live (false). The client reports its own channel — baked into the DLL and flipped Test→Live at promote time — so wrong-server detection works even for players who bypass the launcher. - Holding, not kicking: enforcement holds a player in the Bazaar through the existing progression zone-gating. No disconnects, no character-select kicks, no crashes.
- Opt-out is account-wide and persists across zones, relogs, and server restarts.
- Warnings fire once per zone-in. The non-Multiclass-server warning is client-side and appears on any server that isn't ours.