Reference
Troubleshooting & Recovery
Diagnose client startup, connection, login, graphics, and account problems in the right order.
Audience: All players | Reading Time: 10 min
Use a fixed diagnostic order
- Capture the exact symptom: Record the visible message, when it occurs, and whether the client closes or remains responsive.
- Confirm prerequisites: Verify Windows, x86 Visual C++ 2010, DirectX June 2010, and a writable extracted client folder.
- Confirm realm availability: Make sure the local or hosted server is running before changing client files.
- Confirm client endpoint: The client package must be patched to the correct server address; same-machine offline play uses 127.0.0.1.
- Confirm credentials: Use the game login from My Account, not the email address, with the same password.
- Change one variable: Retest after each correction so the cause remains identifiable.
Client does not start
| Symptom |
Likely cause |
Action |
| Missing DLL message |
Legacy runtime missing |
Install Visual C++ 2010 Redistributable (x86) and DirectX June 2010 |
| Window flashes then closes |
Wrong working directory or incomplete extraction |
Use the supplied root launcher and re-extract the full client |
| Access denied or patch failure |
Protected install folder |
Move the client to a writable user folder |
| Security software blocks x2.exe |
Historical unsigned executable flagged |
Verify the package source, then allow only the known client folder if trusted |
| Black screen or bad resolution |
Legacy display mode incompatibility |
Try a conservative resolution and disable overlays |
Login and connection failures
- Wrong username: The client expects the generated game login shown on My Account, not your email.
- Wrong password after a change: Sign in on the website and use My Account to update the PostgreSQL web credential and game password together.
- Cannot reach server: For offline play, start the database and all five game services before the client.
- Incorrect endpoint: Rerun the approved connection patch for 127.0.0.1, LAN IP, or hosted server address.
- LAN-only failure: Check Windows Firewall and whether the client is using the server PC’s LAN IPv4 address rather than localhost.
In-game issues
- Missing progression chest: Check the character inventory and available space. The grant is character-bound and protected from duplication.
- Chest will not open: Confirm the required level and that every earlier chest in the linked chain was opened.
- Quest appears stuck: Re-read difficulty, dungeon, item, and completion-rank requirements before repeating the run.
- PvP desync or delay: Test a wired connection, reduce background traffic, recreate the room, and compare another host.
- Character asset problem: Restart with the realm’s current patched client. Historical assets must match the server build.
How to write a useful issue report
| Include |
Example |
| Environment |
Windows 11, same-machine offline server |
| Exact time |
2026-07-01 19:42 Mountain Time |
| Action sequence |
Launch → login → character select → dungeon queue |
| Visible result |
Exact error text or screenshot |
| Expected result |
Character should enter the selected dungeon |
| Reproduction rate |
3 of 3 attempts after restart |
| Recent changes |
Password changed, client repatched, or firewall updated |
