This new structure is as follows:

1. move data/src/ to ../content, this is the new Content repo
2. rename this Server folder to engine, this is the new Engine-TS repo
3. edit src/util/Environment.ts to change data/src/ to ../content
4. make sure everything still runs

At this point you are on separate git history and can't git pull for updates, but you can copy anything manually from upstream!

1. Download and extract this repo somewhere on your computer.
2. Install our dependencies.
3. Open the folder you downloaded: Run the quickstart script and follow the on-screen prompts. You may disregard any severity warnings you see.

Once your setup process has completed, wait for it to tell you the world has started before trying to play.

The server includes its own web client, so you don't have to download a client!

• NodeJS 22
• Java 17 - later LTS versions are also fine.

Content developers should run npm start. The server will watch for changes to scripts and configs, then automatically repack everything.

Engine developers should run npm run dev. This does what npm start does above, but also completely restarts the server when engine code has changed.

• bad option: --import

You are using an older version of Node. Reinstall and re-run.

• '"java"' is not recognized as an internal or external command

You do not have Java installed.

• XXXXX has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 52.0

You are using Java 8 or Java 11. If you have multiple Java versions, you will need to set JAVA_PATH=path-to-java.exe in your .env file.

This project is licensed under the MIT License. See the LICENSE file for details.