Towns & Kingdoms — Beyond the ForgeHandbook

Guides / Multiplayer

Set up a dedicated server

Host your own Towns & Kingdoms 3 world and keep the server and clients on the same pack build.

01 / Prepare

Choose the matching files

Obtain the Towns & Kingdoms 3: Beyond the Forge file supplied for your installation. The official CurseForge project covers multiple editions, so check the edition and exact pack file before downloading. A TK2 server archive belongs to another Minecraft installation.

Use the matching dedicated server package when one is provided. If you have only a launcher export, obtain the server installation instructions through the official Discord. A manifest ZIP is an installation description, not a ready-to-run server, and a client mod folder can contain renderers or menu mods that do not belong on a dedicated server.

Create an empty server directory. For an existing world, stop the old server and take a complete backup before replacing any files.

02 / Runtime

Check the server’s Java runtime

For Minecraft 1.21.1, NeoForge’s baseline is 64-bit Java 21. Use the runtime specified by your dedicated server package if it gives one. Check the Java executable used by your server panel or start script.

java -version

If several Java versions are installed, select the required executable in the host panel or by its full path in the start script.

03 / Loader

Install NeoForge

If your server package supplies startup scripts, follow its instructions. For a manual loader installation, download the matching installer from the NeoForge downloads page. Run the installer from the server directory.

java -jar neoforge-21.1.267-installer.jar --installServer

The installer creates run.sh, run.bat, user_jvm_args.txt and the loader libraries. Keep those generated files together. Use the loader required by the pack instead of substituting an unrelated newer build.

04 / Pack content

Keep the common content together

Install the dedicated package’s content, configuration and data as instructed. Preserve the complete common KubeJS structure: startup_scripts, server_scripts, config, pack_data and data. Custom items registered at startup must match the clients.

Keep shared mod configuration and any supplied defaultconfigs alongside the matching mods. Client assets and client scripts remain on the clients. Do not remove a content mod because its name sounds visual; use the server package’s supplied list or the mod’s documented environment.

ContentWhat must stay in step
Content mods and custom registrationsMatching common mods and KubeJS startup definitions
Recipes, tags, loot and weapon capabilitiesThe matching server scripts, pack_data and kubejs/data
Textures, models, trails and client UIThe matching client assets and client-side installation
World and per-world configurationPreserve the existing world and its configuration during updates

05 / First start

Launch and accept the EULA

Start with ./run.sh on Linux or .\run.bat on Windows. Read the Minecraft EULA and, if you agree, set eula=true in eula.txt, then start again.

Set the Java heap in user_jvm_args.txt. The following is an example allocation, not a statement of the host’s total RAM:

-Xms4G
-Xmx8G

Leave memory for the operating system and Java’s non-heap allocations. Watch actual use before changing the limit. Wait for the server’s Done message and check the first-start log for missing mods or failed scripts.

Keep online-mode=true for a normal authenticated server. Enable a whitelist for a private group. Use the game port configured in server.properties; the default is TCP 25565. Open only the required game port in the host and network firewall.

06 / Keep the world healthy

Test before inviting everyone

  1. Join with a matching client. Confirm that custom items, recipes and the character systems appear without registry errors.
  2. Test a small shared workshop. Craft a basic component, use a weapon and identify a piece of equipment before importing large builds.
  3. Back up a recoverable installation. Keep the world, its server configuration, pack configuration and KubeJS content together. Test the restore process on a separate copy.
  4. Update the whole required set. Stop the server, follow the patch’s merge or replacement instructions, update clients and fully restart. Keep the previous working backup until the update has been tested.
  5. Measure a slowdown. Note what was running and collect the relevant logs or a Spark profile. Change one cause at a time.

For access to an official world, use the official servers page. For an installation failure, collect the logs described in the support guide.

Find a weapon, ingredient, mod, chapter or skill.