We supposed you have finish the compilation and now you want to run your own client to connect on the open shard.
|
Download the latest client from Downloads for Windows. After download launch ryzom_client_r.exe to test the shard.
The Mercurial repository (Getting Source) doesn't contains all big data such as textures and 3D objects. You need first to download the client archive before starting Ryzom Core.
Get the latest client from Downloads for Windows and then extract the archive where you would like it, for example in c:\ryzom_client
and then replace the binary and the drivers with your own from the build folders.
If you play on the official Ryzom shard you can also reuse data from your official Windows client and copy the whole folder to |
Right click on "client"
project on the left tree then click on Set as Startup Project
Right click on "client"
project on the left tree then click on Properties
In Configuration Properties->Debugging->Working Directory
set the path to the client directory, for example c:\ryzom_client
. Press "OK"
Press F5 to run the client.
Create a shortcut R:\code\ryzom\bin\client_ryzom_r.exe
inside c:\ryzom_client
.
Edit the properties of the shortcut and be sure "Start in" point to c:\ryzom_client
.
Double click on the shortcut.
This step is extremely important. It is not an option to use the "client_ryzom_r.exe" packaged with the client archive. Since this installation is often outdated it can cause an annoying issue where none of your characters appear. See Client Connect Errors for more details. |
By default, the client will try to connect on open.ryzom.com:40916
. But if you want to client to connect on another shard, add this line in client.cfg
:
StartupHost = "ip.of.your.server:40916";
So it'll override the @StartupHost in the @client_default.cfg that is :
StartupHost = "open.ryzom.com:40916";
To create a user account, run the client, fill login/password and click 4 times on connect.
Validate the popup you will get.
The account is created.
There is a good chance you'll come across an error or two. If you find one, visit the page detailing Client Connect Errors.
For the legacy client:
These steps will not be needed eventually. |