Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To run an All the Magic: Arcana server, download the matching ServerFiles-<version>.zip from the Arcana release’s additional files, extract every file into a clean server directory, run it with a 64-bit Java 21 runtime, accept the EULA after the first launch, and then configure access for your players. The captured release is Arcana 0.13.0 for Minecraft 1.21.1 on NeoForge, paired with ServerFiles-0.13.0.zip.

Use the same Arcana release, Minecraft version, NeoForge loader and configuration on every client. A minimum of 6 GB allocated RAM is the broader All The Mods starting point, not a tested Arcana optimum; adjust it in usr_jvm_args.txt after observing your server.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What you need before installing

Arcana is an ATMTeam modpack for Minecraft 1.21.1 using NeoForge. The server pack supplies the server-side files; it is not the same download as the ordinary client profile.

  • Minecraft Java Edition: Every player needs a licensed Java Edition account and client. Mojang’s server software is intended for Java Edition and requires a compatible Java runtime.
  • 64-bit Java 21: Minecraft 1.20.5 and newer use Java 21, and NeoForge requires a 64-bit JVM. Check the runtime before troubleshooting mods with java -version. The output should identify Java 21 and a 64-bit virtual machine.
  • Memory: The general All The Mods server guide uses at least 6 GB of allocated RAM as a baseline for most packs. Arcana has no separately published official RAM target, player-capacity figure or benchmark, so treat that amount as a starting point rather than a guarantee.
  • A machine or host: You can run the server on your own computer, on another machine on your LAN, or on managed hosting. Your choice determines who handles networking, updates, backups and uptime.
  • A connection plan: Local players can connect without Internet port forwarding. Internet players normally require a firewall rule and router/NAT forwarding for TCP port 25565 unless you change the port in server.properties.

Keep enough memory for the operating system and any other services. Giving Java every available gigabyte can make the host unstable even when the Minecraft process itself has more heap.

Download the correct Arcana server pack

Server and client files must come from the same Arcana release. Starting with a different client version and trying to “make it work” on the server is a common cause of missing-mod and registry errors.

  1. Open the Arcana project’s Files page on CurseForge.
  2. Select the release you want to run. For the currently captured release, select All the Magic – Arcana-0.13.0.
  3. Open that release’s additional files and download the matching ServerFiles-0.13.0.zip. In another release, replace the version in both names with the exact same version number.
  4. Download the normal client pack for that release as well. Give it to players or use it to create your local client profile; do not substitute a similarly named release.

Do not combine server files from one Arcana version with the mods, configuration or world from another unless the release notes explicitly support that migration. Keep the original ZIP as a rollback copy.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Install Arcana on a local machine or host

1. Create a clean server directory

Make a new directory used only for this server, such as Arcana-Server. Avoid extracting over another modpack. A clean directory prevents old mods, configurations and launch scripts from being loaded accidentally.

2. Extract the complete archive

Extract every item in ServerFiles-0.13.0.zip into the new directory. Preserve the directory structure supplied by the pack. Do not place the ZIP itself in a directory and expect the launcher to read inside it.

For managed hosting, upload the complete extracted contents to the provider’s main server directory, not merely the mods folder. The All The Mods server instructions specifically require all extracted files in the main folder.

3. Select Java 21 (64-bit)

Install a 64-bit Java 21 distribution if it is not already present. In a terminal opened in the server directory, run:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
java -version

On a host with a control panel, choose Java 21 in the server’s runtime or startup settings. If the panel offers several architectures, select 64-bit. A Java 17, Java 8 or 32-bit selection can stop NeoForge 1.21.1 before the mod list is even read.

4. Set the heap in usr_jvm_args.txt

Open usr_jvm_args.txt in a plain-text editor and locate the -Xms and -Xmx options. -Xms is the initial heap and -Xmx is the maximum heap. Begin with the guide’s 6 GB baseline when your host has sufficient free memory, then change the values only after checking actual operation.

For illustration, a six-gigabyte allocation is commonly written as -Xms6G and -Xmx6G. Keep the syntax already supplied by the server pack and change only the values. On a managed host, do not set flags that exceed the RAM purchased from the provider. If the file already contains other JVM options, leave them intact unless the pack documentation tells you otherwise.

5. Run the supplied launcher once

Start the generated server script or launcher from the extracted directory. The first run normally creates files, including eula.txt, and then stops. This is expected; it gives you a chance to review the license terms before the world is generated.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

6. Accept the EULA

Open eula.txt, read the Minecraft End User License Agreement, and change:

eula=false

to:

eula=true

Save the file and start the same launcher again. If it stops immediately, check that the file is named exactly eula.txt, the value is lowercase, and the file is in the server’s main directory.

7. Let world generation finish

Leave the console running while NeoForge loads the mods and creates the world. The first launch can take substantially longer than later starts because it builds directories, registries and world data. Wait for the console’s ready message before connecting. Stop the process cleanly from the console after the initial generation if you need to edit properties or make a backup.

Configure memory without guessing

No Arcana-specific official recommendation establishes how many players a particular machine can support. The six-gigabyte figure is a broad All The Mods baseline, not a performance promise. Treat capacity as dependent on the host CPU, storage, view and simulation settings, loaded chunks, dimensions, automation and number of players.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use this tuning sequence:

  1. Start with the baseline allocation in usr_jvm_args.txt, while leaving RAM for the operating system and other services.
  2. Let the server run under the workload you actually expect: exploration, chunk generation, machines and simultaneous players.
  3. Read the console and logs for memory-related errors, repeated crashes or long pauses. Do not raise the heap solely because the operating system reports unused memory.
  4. Change one value at a time, restart cleanly, and compare behavior. Keep a copy of the previous JVM-argument file so you can revert.

Increasing -Xmx cannot fix a wrong Java version, an incompatible mod list or a blocked network port. Resolve those faults first.

Make the server reachable

Same computer

A player launching Minecraft on the server machine can usually connect with localhost (or 127.0.0.1) and the configured port. This tests the server without involving the router.

Other devices on the same LAN

Find the server computer’s private address, such as a local IPv4 address, and give that address to players on the same network. They should use the address and port shown by the server configuration. A private address is not reachable from the public Internet.

Players outside your home network

For Internet access, allow the server process through the host firewall and forward TCP port 25565 on the router to the server computer’s private address. Mojang documents 25565 as the default Java port; if you set a different value in server.properties, forward and advertise that value instead.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Assign the server computer a stable private address, preferably with a DHCP reservation, so the router rule does not point to a changing device.
  2. Create a router/NAT rule forwarding TCP 25565 (or your chosen port) to that address.
  3. Permit the same port through the operating system firewall for the Java server process.
  4. Start the server and test from a network outside the home LAN. Testing only from inside can produce misleading results on routers without NAT loopback.
  5. Give trusted players the public address and port privately. Do not post your home public IP broadly.

Some Internet providers use carrier-grade NAT, which prevents inbound forwarding even when your router is configured correctly. In that case, use a managed host or another connectivity method rather than repeatedly changing Minecraft settings.

Managed hosting

A managed host can remove home-router administration and normally supplies a public endpoint, but compatibility is not automatic. Before paying, verify all of the following:

  • It accepts uploads of the complete Arcana CurseForge server pack, including custom launch files.
  • Java 21 and a 64-bit runtime are available for a Minecraft 1.21.1 NeoForge server.
  • You can edit or upload usr_jvm_args.txt and control the allocated RAM.
  • You have file access for configuration, logs and manual troubleshooting.
  • Backups exist, with stated frequency and retention, and can be downloaded or restored.
  • The advertised storage, player-slot policy and support scope match your intended workload.

Some panels require you to select a custom JAR or startup command. Use the launch method included with the Arcana server files unless the host’s documentation gives an equivalent NeoForge procedure.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Synchronize every client with the server

Each player should install the same:

  • Minecraft version: 1.21.1
  • NeoForge loader version required by the selected Arcana release
  • All the Magic: Arcana release, such as 0.13.0
  • Mod files and configuration supplied by that release

The safest process is for everyone to start from the same CurseForge release page and use the paired client and server downloads. Do not add client-only or server-only mods casually; a modpack may rely on a precise registry and dependency set.

When a player cannot join, record the exact release number from the client and server before changing files. The official All the Magic repository asks issue reports to include the version in the issue title, which is also a useful habit for private support: it prevents a 0.13.0 problem from being mixed with another release.

Self-hosting versus managed hosting

Consideration Self-hosted machine Managed host
Control Direct access to every file, JVM flag, operating-system setting and log. Web panel and provider limits; confirm that custom server-pack files and startup options are allowed.
Network work You may need firewall rules, router forwarding and a stable private address. The provider normally supplies a public endpoint, so home-router administration is reduced.
Maintenance You handle Java updates, NeoForge/modpack updates, backups, security and uptime. The provider may automate some tasks, but you must verify exactly what is backed up and maintained.
Cost and capacity Uses your existing hardware and connection; electricity, bandwidth and hardware limits are yours. Compare recurring price, allocated RAM, storage, player slots, backup retention and file access.
Recovery You control local copies and can restore any archive you create. Recovery depends on the host’s backup schedule, retention and download/restore tools.

Choose self-hosting when you are comfortable administering Java, the operating system and the router. Choose managed hosting when a public endpoint, continuous uptime and a control panel are worth giving up some low-level control. In either case, retain your own copy of the world and configuration.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Back up before updates

NeoForged recommends backing up the world before updating NeoForge or mods. For Arcana, make a full server copy before changing the modpack release, loader or Java runtime. At minimum, preserve:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • The entire world directory, including every dimension.
  • config and defaultconfigs.
  • server.properties, eula.txt, operator and whitelist files.
  • usr_jvm_args.txt and any custom launch or service files.
  • A record of manually added or removed mods.
  1. Stop the server from its console; never copy a live world as your only backup.
  2. Copy the listed files and directories to storage outside the active server directory.
  3. Keep the old server archive until the new release has been used successfully.
  4. Test the update on a duplicate directory first. Start it with a copied world, confirm that players can join and inspect key areas before changing the production server.
  5. If the update fails, stop it, restore the previous server files and backup, and investigate from the old log rather than repeatedly launching the damaged copy.

Updating only the client or only the server can leave the two sides with incompatible registries. Schedule both sides together and tell players which release they must select.

Troubleshoot in this order

1. Verify Java before reading mod errors

Run java -version in the same environment used by the launcher, or inspect the Java selection in the host panel. Confirm Java 21 and 64-bit. A terminal may use a different Java installation from the one selected by a service or panel, so check the actual startup environment.

2. Compare versions exactly

Confirm the server pack filename, client profile, Minecraft version and NeoForge loader. A mismatch in Arcana release or loader can produce missing dependencies, rejected registries or a disconnect during login.

3. Check the first meaningful console error

Recheck eula.txt, usr_jvm_args.txt and the server’s first stack trace. Fix the earliest configuration or dependency error rather than focusing on later “shutdown” messages, which are often consequences.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

4. Separate startup faults from connection faults

If the server never reaches its ready state, investigate Java, files, memory and mod compatibility. If it reaches ready but nobody can connect, test locally with localhost, then on the LAN, then from outside. This sequence identifies whether the fault is the server process, the private network or the router/firewall.

5. Recheck port and address

Read the port in server.properties. Ensure the router forwards that exact TCP port to the current private address and that the operating-system firewall permits Java. Players outside your network must use the public address, not the server’s private LAN address.

6. Preserve evidence for support

Keep the complete log, the exact Arcana and NeoForge versions, Java output and a description of when the failure occurs. Search or file a version-tagged issue in the official All the Magic repository when the problem remains reproducible. Do not remove half the mods or replace files at random before capturing the original error.

Operational checklist

  • Dedicated directory contains only the selected Arcana server files.
  • Client and server are paired to the same Arcana release.
  • Java reports a 64-bit Java 21 runtime.
  • usr_jvm_args.txt has a realistic -Xms/-Xmx allocation.
  • First launch completed, eula=true was saved, and the server reaches its ready state.
  • Local, LAN or Internet address is appropriate for each player.
  • TCP 25565 is forwarded only when needed and matches server.properties.
  • World and configuration backups exist before updates.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.