One download, one checksum.
The full client, and the checksum to make sure the file you got is the one we published.
Not published yet
The download is not up yet. When it is, it will be on this page — anything offered elsewhere is not ours.
When the archive goes up, its name, size and SHA-256 appear in this card at the same moment. Nothing is handed out ahead of that in a private message.
Four steps, in order.
-
Take it from this page only
We only ever hand out the client from this page. A copy that reached you by private message, a re-upload or a search result can have anything hidden in it.
-
Compare the checksum before you run it
On Windows,
certutil -hashfile <file> SHA256prints the hash. It must match the value in the card character for character. If it does not, delete the file instead of opening it. -
Extract outside Program Files, then run the DirectX setup
Somewhere like
C:\Games\Jade Dynasty Mortal. Program Files makes Windows guard the folder and the launcher cannot write its updates there. The client ships a DirectX installer in its own folder; run it once after extracting. -
Register, then enter
Start Launcher.exe — not the patcher. It updates the client, then opens the game. Log in with the name and password you registered on this site.
Before you start the download
Before you start the download.
Two things worth knowing so nothing catches you out halfway through.
Roughly 23 GB once extracted
The download is much smaller than the folder it unpacks into, and you need room for both at once while it extracts. Put it on a drive with space to spare.
We run client version 614. A client from another Jade Dynasty version will not connect, no matter what the folder is called.
Dedicated hardware in France. Latency is honest from western and central Europe; from further away, expect what the distance costs.
The launcher updates itself first, then the game, checking each update as it goes. You download the full archive once and never hunt for a patch again.
Experience rates, drop rates and the level cap have not been settled. We would rather print this than invent numbers you would later have to unlearn.
Why the checksum matters
A tampered client is the oldest trick there is.
Repacked clients are how private-server players lose accounts. The archive we publish and the hash we publish are produced together, so one line of terminal output tells you whether the file on your disk is the file we built.
- The launcher verifies every patch against a signing key we hold, so a mirror cannot slip you a modified update.
- Nothing you do on this website can touch your characters or your items.
- Account mail comes from our own mail system, on our own domain, so a message about your account has a source you can check.
- Backups run nightly and are restore-tested, so a bad night for the hardware is not a bad night for your character.
If something goes wrong
Bring the error, not the guess.
Most install problems are one of three things, and all three are quick to settle if you say which one you hit.
- The checksum does not match. Delete the archive and download it again, from a different mirror if one is offered.
- The launcher cannot write its update. The client was extracted into Program Files or another protected folder. Move it and start again.
- The game closes on start. Run the included DirectX setup; it is the usual cause on a fresh Windows install.
Anything else, bring the exact message to Discord. A screenshot of the error settles in a minute what a description takes an evening to narrow down.
