Server Setup Guide
This guide will explain how to set up an server locally, or with a server host.
Requirements
- Create Chronicles: Bosses and Beyond
- Create Chronicles: TBA
- A server with at least 8GB of RAM
- A CPU with at least 3.5GHz
- Java 17 installed (preferably from Adoptium).
Installation
- Go to the CurseForge page of the modpack
- Click on Files and choose the same version you plan to use on your client.
- Scroll to Additional Files and download the Server Files
- Extract the
Server-Files.zip
into a new folder.
If you're using third-party antivirus software, exclude this folder to prevent important files from being deleted or corrupted.
It’s a good idea to keep your server and client version up-to-date to benefit from bug fixes, performance improvements, and new features.
Java Setup
Check the Requirements section to see which version of Java is required to run the modpack correctly.
If you don't know how to install Java, refer to the Java Installation Guide.
If you have multiple Java versions installed, the system default (java
) might point to the wrong version. Fortunately, the server's startup script allows you to specify which Java installation to use.
How script works
The script checks for an environment variable called CCB_JAVA
. If it's set, it will use that as the Java executable.
If not, it defaults to your system’s installed java
command (JAVA_HOME
).
Step 1: Check Your Java Version
Run this command in your terminal:
java -version
You should see output similar to:
openjdk version "17.x.x"
If the version matches the one listed in the requirements, you're good to continue! ✅
Step 2: Check if JAVA_HOME
is already set
Before setting anything, check if it's already configured:
- Windows (Command Prompt)
- Linux
echo %JAVA_HOME%
-
✅ If it returns a valid path (like
C:\Program Files\Java\jdk-17...
), you're good! You can skip Step 3. -
❌ If it returns
%JAVA_HOME%
, it means it's not set — continue to Step 3 to set it.
echo $JAVA_HOME
If it returns nothing or an invalid path, follow the steps below to set it.
Step 3: Set JAVA_HOME
JAVA_HOME tells your system (and most launchers) where Java is installed.
- Windows
- Linux
▶️ Watch YouTube Video Guide (if needed)
-
Search for Environment Variables in the Start Menu
-
Click "Edit the system environment variables"
-
In the System Properties window, click Environment Variables
-
Check if
JAVA_HOME
is already listed under:- 🔸 System variables
👉 If it exists, select it and click Edit instead of adding a duplicate.
-
If it's not already set, click New:
-
Variable name:
JAVA_HOME
-
Value: your Java install folder (⚠️ not the
bin
folder)
Example:C:\Program Files\Eclipse Adoptium\jdk-17.0.9.9-hotspot
-
-
Click OK → OK → OK
-
To verify it’s working, open Command Prompt and run:
echo %JAVA_HOME%
If it returns a valid path you did everything correct ✅
🔍 How to Find the JDK Installation Path
If you're unsure where your JDK is installed, you can run one of the following command to find its location:
where java
This will return something like:
C:\Program Files\Eclipse Adoptium\jdk-17.0.9.9-hotspot\bin\java.exe
Now just remove the \bin\java.exe
part, and that’s your JAVA_HOME
path:
C:\Program Files\Eclipse Adoptium\jdk-17.0.9.9-hotspot
Add the following lines to your ~/.bashrc
, ~/.zshrc
, or ~/.profile
:
export JAVA_HOME="/path/to/java"
export PATH="$JAVA_HOME/bin:$PATH"
🔄 Reload the config:
After editing the file, reload it using:
source ~/.bashrc
Replace
.bashrc
with.zshrc
or.profile
depending on your shell.
To verify Run the following:
echo $JAVA_HOME
Optional: Use CCB_JAVA
to Run Java (Skip this if you don't know)
If you want to use a specific Java version just for the server script, you can set the CCB_JAVA
environment variable.
Local Installation
- Extract the server files to a folder.
🐧 Linux Users:
- Ensure the server folder has read/write permissions.
- Run this command once to make the start script executable:
sudo chmod +x startserver.sh
▶️ Start the Server
- Windows: Run
startserver.bat
- Linux: Run
startserver.sh
📌 The first launch will generate several files. Do not interrupt this process.
Accept the EULA
Then open eula.txt
and change:
eula=false
to eula=true
Once you see:
Dedicated server took XX seconds to load
🎉 Your server is ready, and you can join!
Server Host Installation
Most server hosts support one-click modpack installs, but if not, follow these steps:
- Set up a fresh Forge server matching the modpack’s Forge version.
- If no Forge installer is available, see the Custom JAR section below.
- Upload the extracted Server Files using FTP/SFTP (e.g. with FileZilla).
- If SFTP isn't available, upload the
.zip
file and extract it using the host’s file manager.
Server Host Custom JAR
If your server host requires a .jar
file:
For newer Forge versions:
- Use
ServerStarter.jar
For older Forge versions:
- You may be able to use
forge-*-universal.jar
✅ Steps:
- Upload the server files to the root directory
- Adjust
mcVersion
andloaderVersion
if needed - Set the custom JAR to
ServerStarter.jar
in your host settings
Updating Your Server
Make sure the server is completely shut down before proceeding.
🔒 Back up your world before updating!
✅ Automatic (Host Installer)
- Use your host's modpack control panel to perform a one-click update (if available)
🧰 Manual Update Steps
1. Delete the following folders from your server:
config/
defaultconfigs/
kubejs/
mods/
2. Download the latest Server Files
3. Replace the deleted folders:
- Unzip the downloaded server files.
- Copy and replace the deleted folders on your server with the new ones from the archive.
✅ Your server is now updated and ready to launch!