Getting connected takes about fifteen minutes. Read step one carefully — it is the part we cannot do for you.
1. Obtain your own copy of the game client
We do not distribute, host, mirror, or link to game client files, and we cannot help you find them. Requests for client files in our forums or Discord will be removed. This is not us being unhelpful — distributing Daybreak's copyrighted game data would end this project, and it is the one rule we cannot bend.
If you owned the original discs, that is your copy.
2. Install outside Program Files
Put the game somewhere like:
C:\Games\EverQuest
Do not install into C:\Program Files or C:\Program Files (x86). Windows applies additional permission restrictions to those directories, and a DirectX 7-era game that expects to write files next to its own executable will fail in confusing ways — usually a silent crash on launch, or settings that never save.
3. Create your accounts
Register here. That is the only account you have to make — a game account is created for you at the same time, with the same username and password. That is what you type at the client login screen.
You can manage it, change its password, or add more game accounts from your game accounts page.
Consider giving the game account its own password. The Trilogy client sends it over a legacy login flow that predates modern transport security, so it is worth not sharing it with the account that can post as you and manage your profile.
4. Install the Winsock DLL, then run the patcher
Order matters here. The stock EverQuest patcher has our server's address compiled into it nowhere — it only knows the original one. The Winsock DLL is what redirects its network calls to us, so it has to be in place before the patcher can reach anything.
- Download the Winsock DLL: [link to be added]
- Put it in your EverQuest folder, next to
eqgame.exe. - Run the patcher.
With the DLL in place the patcher connects to us and pulls down what it needs — eqhost.txt, Glide3x.dll, d3drm.dll and the rest of the compatibility layer:
| File | Purpose |
|---|---|
eqhost.txt |
Tells the client which login server to use |
Glide3x.dll, d3drm.dll |
Translate the client's DirectX 7 calls for modern GPUs |
| Gameplay / compatibility DLL | Our server's client-side compatibility layer |
The patcher never downloads game content — by design, and as a legal safeguard. If it is offering you zone or model files, you are not running ours.
5. Connect
Launch the client, sign in with your game account name and password, and pick a server. The status page shows exactly the same list, so you can check what is up before you launch.
| Server | What it is |
|---|---|
| Tunare | Progression. Classic → Kunark → Velious, then characters retire to Tranquility and it starts again. Where most people begin. |
| Innoruuk | The same journey with PvP rules. Each cycle uses a different historical classic ruleset. |
| Tranquility | Permanent, locked at Luclin. Where Tunare characters retire when a cycle ends. |
| Drunder | Permanent PvP, locked at Luclin. Where Innoruuk characters retire. |
| Zebuxoruk | Test server, always one era ahead of live. Changes are proven here first. |
The names follow a rule: servers that cycle are named for gods, servers that stay put are named for places in the Planes.
The progression ends at Velious and does not continue into Luclin or the Planes — that would mean supporting more client versions than a volunteer team can do well. Luclin is where finished characters go, not somewhere the cycle passes through.
If you are new, start on Tunare. It is the busiest server and it begins at Classic, which is where the game makes the most sense.
Troubleshooting
Antivirus flags the patcher or the DLLs
This is expected and it is a false positive. A small unsigned executable that downloads DLLs and patches another program's network calls looks, to a heuristic scanner, exactly like malware. Windows Defender and most commercial AV products flag it.
The fix is a folder exclusion, added before you download:
- Open Windows Security → Virus & threat protection
- Manage settings → Add or remove exclusions
- Add an exclusion → Folder → select your EverQuest folder
Add the exclusion first. If your AV quarantines a DLL mid-download you will get a partially patched install, which produces much stranger errors than a clean failure.
If you are not comfortable adding an exclusion, that is a reasonable position — you can verify the SHA-256 hash of each file against the published manifest before allowing it.
The client crashes immediately on launch
Almost always the Program Files problem from step two. Move the installation to a path you own.
The client launches but the server list is empty
Check the status page. If the login server is unreachable we say so there. If it shows servers and you see none, the Winsock DLL is probably not being loaded — confirm it sits in the same folder as eqgame.exe, then check that eqhost.txt is there too. Re-running the patcher will not fix a missing Winsock DLL, because the patcher needs it to reach us in the first place.
Graphics glitches, black screen, or a tiny window
This is dgVoodoo2 configuration. The defaults we ship work on most hardware; if yours needs adjusting, ask in the forums and include your GPU model.