Import a Server
If you’ve already made a Minecraft server outside of auto-mcs, you can import it without having to start over. auto-mcs handles the process automatically, including detecting the server type, Minecraft version, add-on compatibility, and preparing the server for management.
To get started, select Import from the Create a New Server screen. There are two options: importing an external server folder, or importing an auto-mcs back-up.
Import an external server
Section titled “Import an external server”- Stop the original server before copying its files to avoid missing or inconsistent data
- If you downloaded an archive, extract it to a directory of your choice
- In auto-mcs, choose Import External Server and select the extracted server directory
- Continue through the import process. auto-mcs will scan the files, detect the server configuration, and create a managed copy
Make sure you’re selecting the folder that actually contains the server files, rather than the directory above it or the .zip file itself.
Import requirements
Section titled “Import requirements”Generally, the directory needs to contain a functional Minecraft server installation. For most distributions, this means a server .jar file, and a launch script such as start.bat or run.sh that points to the .jar or other required server files. auto-mcs will inspect available .jar files and startup scripts to find the correct one. Some distributions, such as newer Forge and NeoForge servers, use launch scripts and libraries instead of a conventional standalone .jar.
Be sure to keep the rest of the server files, such as worlds, plugins/, mods/, and config/ when applicable. A world folder by itself isn’t a complete server installation; if you’re only moving a world, you can import it while creating a server. However, these can always be added later.
Compatibility
Section titled “Compatibility”Every server distribution supported by auto-mcs can also be imported: Vanilla, CraftBukkit, Spigot, Paper, Purpur, Forge, NeoForge, Fabric, and Quilt. The importer is designed to support older Minecraft versions as well as current releases.
Rather than requiring you to enter the version manually, auto-mcs attempts to determine it from the server .jar, launch scripts, and available metadata. For some servers, it may temporarily launch a copy using an appropriate Java version and inspect the logs to determine the exact Minecraft version.
This works with most conventional server layouts, but unusual launchers, custom installations, or incomplete files can still prevent automatic detection.
Import an auto-mcs back-up
Section titled “Import an auto-mcs back-up”If you’re transferring a server from another auto-mcs installation or from a deleted server, you can use a .amb back-up created by the Back-up Manager.
- Copy the
.ambfile to the computer where you want to import the server - Select Import Auto-MCS Back-up in the import menu
- Choose the
.ambfile and continue
Unlike importing an external server, a back-up already contains the auto-mcs configuration needed to identify the server. The application extracts the snapshot and prepares it for the current installation.
After import
Section titled “After import”Once the import finishes, your server will open in the Server Manager, just like a server created through auto-mcs. From there, you can start it, manage the console, install add-ons, and change its configuration whenever you need to.
auto-mcs also creates a back-up after importing, so you have a snapshot of the server at the imported state before making further changes.
If the imported server fails to launch, see Server Troubleshooting for diagnosing startup errors.
Headless import
Section titled “Headless import”You can also import existing servers and auto-mcs back-ups using the server import command in the headless CLI. Specify the path to an existing server directory:
server import "/home/minecraft/My-Server"Or provide the path to an auto-mcs .amb back-up:
server import "/home/minecraft/My-Server.amb"The path must exist on the machine running auto-mcs, not the computer you’re using to access a remote host. For an external server, select the directory containing server.properties and the remaining server files; for a back-up, select the archive itself. The importer uses the same server detection and preparation process described above.