The Ryzom Core Quick Start package provides you with a fully preconfigured project folder. Enabling you to easily get started with running the entire asset creation and development pipeline to build your own MMORPG, and to collaborate on the Ryzom Core technologies.
This release integrates the complete game development workflow in one package. Build new assets. Add new landscape. Create new missions. Design a new sound library. Develop the client, shard, and web tools. Debug locally. Orchestrate production servers. Deploy client and server patches.
Download the following three archives, and extract as specified.
Replace any occurence of Y:\ryzomcore in this guide with your installation folder.
If you have 3ds Max available, copy the appropriate build of 3ds Max plugins from Y:\ryzomcore\redist directly into your 3ds Max installation folder.
Ensure that you do not have any drive called R:\ in your system. This procedure will map the project drive to R:\, due to certain tools which only support absolute paths, or which have hardcoded paths. 3ds Max project files should always be opened through this mapped drive.
Optionally, edit Y:\ryzomcore\.nel\config.json before proceeding. Configure the paths to your 3ds Max installation, as well as the fingerprint for your code signing certificate. Leave as-is if not applicable.
Run _configure.bat from the Y:\ryzomcore folder.
This script will detect the project installation path, create some convenience shortcuts inside the installation folder, and run the build pipeline setup script. If you ever move your installation to a different folder, or want to change options, just run this script again. Aside from using the 3rd party libraries and tools listed above, as well as the R:\ drive, the quick start package is fully self-contained, and does not affect any system-wide settings.

You can get a code signing certificate from any reputable certificate shop. It is not necessary for development, but it is highly recommended when targeting production. The cheapest Sectigo certificate from Xolphin is sufficient.
If you need to unmap the R:\ drive for other uses, run the _r_uninit.bat script. Run _r_init.bat anytime you want to work on the Ryzom Core project again. The R:\ drive is also unmapped upon reboot.
The first-time configuration may take a while. When it is done, press any key to close the configuration script.
Run the web_on.bat script. This will launch MariaDB at port 9040, PHP-CGI at port 9041, and Nginx on port 9042.

Browse to http://localhost:9042/setup/install.php?dev. The paths, ports and database names should already be filled in correctly.
Choose a Setup Password and an Admin Password of at least 8 characters each. Then fill in the Administrator Account panel with a login, an e-mail address and a password. This is your first game account, and it gets the :DEV: privilege.
Click on Configure to initialize the databases. The user for the shard admin tool at http://localhost:9042/admin/ is admin, with the Admin Password you chose.
You can verify the configuration by checking the shard table in the nel database using phpMyAdmin, which is located at http://localhost:9042/phpmyadmin/. Log into the local development database with the default root username and no password. MariaDB only listens on localhost, and the /phpmyadmin/, /admin/ and /setup/ pages are only served to browsers on this machine.

There should be one shard. The value for WsAddr should match your local hostname.
The administrator account you entered in the installer is ready to play with. It also signs in to the account tool at http://localhost:9042/account/, which the localhost_account shortcut in your installation folder opens.
Registration is closed by default. To make more accounts for testing, sign in to the account tool with the administrator account, go to the Dev page, set Account Registration to 1, and save the settings. Then browse to http://localhost:9042/account/?page=register, and create as many accounts as you need.
To give another account developer privileges, go to the user table in the nel database. Enter :DEV: as new value for Privilege on the user.
A quick start that was configured with the 4.0 package (Python 2.7 and the web servers in its own external folder) runs everything from the C:\2026q4_external_v143_x64 package after the upgrade: Python 3, MariaDB, PHP, nginx and phpMyAdmin. The external folder of the project is not used anymore, and _configure.bat writes the configuration of the development web into pipeline\shard_dev\web. The database keeps its place in pipeline\shard_dev\mysql: after the first web_on.bat with the newer MariaDB, run
"%RC_MARIADB_DIR%\bin\mysql_upgrade" -u root --port=9040from cmd_tools.bat once, then the setup upgrade below. The setup upgrade also points the development domain at its services on 127.0.0.1, where the development shard listens.
A quick start that was configured before the account tool replaced the AMS, the old account management system, needs the setup upgrade once after updating the code: browse to http://localhost:9042/setup/upgrade.php, which asks for your setup password. The accounts you have are kept. Run _configure.bat again for the localhost_account shortcut, and delete the localhost_ams shortcut, which leads nowhere now. The upgrade notes of the web services have the details.
The shard scripts open the service dashboard: servdash_gui in its own window, or, with "Headless": true in .nel\config.json, servdash_cli in the console for a box reached over SSH. Each process has a row with a state light and a start or stop button, and the pane of the selected process shows its console with a command line. The screenshots below are of the older Win32 dashboard; the layout is the same.
The development domain binds every service port to localhost (BindAddress = "127.0.0.1"; in patchman\shard_ctrl_dev.txt and in the AES config), so the naming services, the service ports, the admin ports and the backup service cannot be reached from other machines. The client ports of the FES (UDP and QUIC, 47911 and 47912), the client ports of the session browser (TCP, the FES port plus 1000: 48911 and 48912, used by the Ring terminals, the character selection and moves between shards) and the web server on port 9042 are the only ports open to the network, and the web server refuses the database console, the web admin and the installer to other machines.
Run the shard_unifier.bat script. This launches the Unifier which joins the mainland and Ring shards together, as well as the administrative services. Wait for all the services to launch, then switch to the SU tab.

To start the Mainland shard, run the shard_mainland.bat script. Wait for the services to launch. EGS, GPMS, and IOS may take a while during the first run. When all the tabs are opened, switch to the EGS tab.
If any service fails to start, use the controls in the dashboard to restart the service. This may occur due to port conflicts.

Run shard_ring.bat. This will start the Ring shard. Switch to the DSS tab.

The development shard is stored under Y:\ryzomcore\pipeline\shard_dev. Its configuration files are generated from the patchman repository.
Run the client_dev.bat script, log in. Create a character, and play or launch the Ring editor.


Run cmd_build_gamedata.bat from the main project directory to open the build pipeline console.
To rebuild leveldesign, run the leveldesign_dev.bat convenience script.
The convenience scripts are self descriptive. Use the build_gamedata shortcut, and explore their contents in notepad to see how to issue commands to the build pipeline scripts directly.
If you want to update all repositories before proceeding, first run Y:\ryzomcore\_upgrade.bat
Run _configure_docker.bat. This will prepare the necessary Docker build images. This step is only required to build production server and client binaries for Linux.
To configure and build all projects, run code_configure_rebuild_all.bat. This may take a while.
The Visual Studio project for client development can be found under Y:\ryzomcore4\build_win32\client_dev\RyzomCore.sln. By default it uses .\pipeline\client_dev as working directory to connect to your local development shard.
When rebuilding for production, run the executable_dev.bat script from the gamedata build terminal to update the client and server installation layouts with the newly built binaries.
Make sure the shard, including the Web, is shut down.
Run the web_wipe.bat script from the main project directory. It removes the database, the web configuration of the project under .\pipeline\shard_dev\web, and the configuration the web setup wrote into the code folder.
Remove the shard_dev directory, located under .\pipeline.
Run _configure.bat again. It writes the web configuration, and reinitializes the shard.
Then follow the initial configuration steps again for reconfiguring the Web.
TODO: Link to next steps.
Close the Ring dashboard. When that is finished, the Mainland window. Then the Unifier. After that, close the Web. In the console, F12 twice does the same for one dashboard, and servdash_cli --shutdown-all stops every running dashboard with its services.