All the Mods 11 version 0.13.0-beta was published on 27 October 2026. Before choosing Minecraft server hosting, check which pack release your group will use and whether its matching dedicated-server files are available. The client pack alone does not confirm that a server installation is ready.
This guide covers the 0.13.0-beta release notes and the checks to make before moving a world. It does not give a measured RAM minimum or promise a player capacity for this beta.
Check the pack, Minecraft and loader versions
The official 0.13.0-beta file targets Minecraft 26.1.2, and its changelog identifies NeoForge 26.1.2.124. Keep the pack version, loader and required runtime together when preparing an installation. FTB Evolution 2 targets the same Minecraft 26.1.2; our FTB Evolution 2 server guide shows the Java 25 runtime and the heap that FTB's installer sets up for a pack on this version.
CurseForge displays an R file label, but the release name still says beta. Treat the pack as under development. Follow the requirements supplied with the chosen release; selecting a newer loader separately can leave the pack on an unsupported combination.
Verify matching dedicated-server files
Check the official ATM11 file list for a dedicated-server download that explicitly matches your client pack. The 0.13.0-beta entry checked on 28 October lists no additional files. We have not confirmed a matching 0.13.0-beta server pack, so do not treat the older 0.12.0-beta server download as the matching release.
That observation does not establish that server files cannot become available later. Read the current file listing and the pack author's instructions before installing. Keep the names and versions of the downloads you actually use in your installation notes.
Check that your hosting environment offers the runtime and installation method required by those files before placing an order. A new pack release does not establish that it is already listed in Space-Node's panel installer.
Read the mod and quest changes
The 0.13.0-beta notes remove KubeJS and Rhino and add KubeGroovy. If an existing world has custom scripts or additions, review them against this release instead of carrying over an old scripts directory without checking it.
The same notes warn that contact with fluids from several mods can prevent player movement. They also describe the quests as unfinished and subject to changes as the pack develops. Read the complete changelog for the version you intend to run and include the affected activities in your test plan.
Choose capacity from the complete installation
The release page does not provide a measured RAM minimum or player capacity. Other modpacks and an allocation printed on a hosting card cannot establish what this installation will need.
Describe the exact beta version, your mod additions, any imported world and the expected use when comparing plans. During play, watch the memory figure and server log. Use those observations to decide whether the allocation should change, following the pack's and host's launch instructions.
Keep a complete recovery copy
Stop the existing server and save the world, configuration, mods, scripts and startup settings together. Store the copy separately from the installation you plan to change, and record which versions it belongs to.
Check how you would restore that complete copy before starting the update. Keeping the old server executable alone will not recover the rest of the installation. Make sure your group knows when the test world will be used.
Test before reopening the world
Prepare a separate test installation using the matching server files and their supplied instructions. Read the startup output, then join with the matching client pack. Check connections, saves after a restart, scripts and any activities affected by the beta warnings.
Keep the existing installation available until you have checked the result. If you cannot confirm matching files or recover the world yet, wait before switching the live server. Record the exact errors and versions if you need help with the next attempt.