Server Guides

• Windows, macOS, or Linux
• At least 2 GB RAM (1 GB if running server only)
• Java Development Kit (JDK) 8 or newer (OpenJDK recommended)
• Git
• Apache Ant (for compiling)
• Optional but recommended: MariaDB (for MySQL) + HeidiSQL, or just use the built-in SQLite option for easiest setup

• Download the latest OpenRSC Single-Player release or clone the Core-Framework repository from GitHub/GitLab.
• Install OpenJDK.
• On Windows: Run Start-Windows.cmd, choose option 1 to start the game.
• On Linux/Mac: Use the equivalent Start script.
• Create a new character when the client opens.
• This is the fastest way to test everything locally before hosting publicly.

• Install OpenJDK, Git, and Apache Ant.
• Clone the Core-Framework repository:

git clone https://github.com/Open-RSC/Core-Framework.git

• Choose database type in connections.conf (SQLite is easiest for beginners; MySQL/MariaDB is better for public servers).
• If using MySQL: Set up MariaDB, create a database (usually named preservation), and import the core.sql file.
• Compile and run the server:

cd server
ant compile-and-run

• You should see "Game world is now online" or similar.
• Compile and run the client from the Client_Base folder the same way.
• Make your first character an admin by updating the group_id in the players table (via HeidiSQL or equivalent).

• Copy a preset config file (e.g. default.conf, preservation.conf, or rsccabbage.conf) and rename the copy to local.conf.
• Edit local.conf to change:

• • Server name
• • Experience rates
• • Members/F2P status
• • Tick speed
• • Max players
• • And many other options

Restart the server after any config changes.

• Port-forward the server port (default is usually 43594) on your router.
• Update the client's ip.txt with your public IP.
• Share the compiled client or have players connect using the RSC+ client by adding a new world with your IP, port, and RSA keys (shown in the server console).

• Always start with a local setup before trying to host publicly.
• Join the OpenRSC Discord for help — the community is active and helpful with setup issues.
• Make a backup of your database before making big changes.
• For public servers, use a strong database password and consider a VPS if you don't want to keep your home PC on 24/7.