Minecraft Server Guide

← All guides · GAME GUIDE

Select the server, then open Server Options → Minecraft Control Center. Its pages bring Minecraft management together; opening the window does not start the server.

Create or import the right edition

1. Add a new Minecraft server or import an existing installation.
2. Choose Java or Bedrock. They are separate server types.
3. For Java, select the Minecraft version, loader/runtime, and compatible build offered by the selectors.
4. Review name, world, player limit, memory, ports, and enabled security fields.
5. Complete required settings, open step 3 — Review, then save.
6. Run Readiness and start. Read any agreement before accepting it.
7. Wait for loading to finish and test with the matching client edition/version.
8. Back up the working server before changing runtimes, worlds, or mods.

Synix prepares the supported Java runtime/server combination. Bedrock uses the official Bedrock Dedicated Server package, not Java.

Choose the correct Java runtime

Selection	Intended content
Vanilla	Unmodified Java server; not a Fabric/Forge or Bukkit plugin loader
Fabric	Compatible Fabric server mods
Forge	Compatible Forge server mods
NeoForge	Compatible NeoForge server mods, where versions/builds are offered
Paper	Compatible Bukkit/Paper server plugins
Purpur	Compatible plugins for the selected Purpur/Paper-based server build

Use the versions actually available in the selectors. A detected Quilt, Spigot, or other framework in an imported installation does not mean Synix offers an installer for every release of it.

Match Minecraft, loader, mod/plugin, dependencies, and client requirements. Creating a mods or plugins folder does not install the runtime. Java JARs are not Bedrock behavior/resource packs; Bedrock pack activation remains edition-specific.

Control Center pages

Page	Main actions
Overview	Start, Stop, Restart, Setup, Apply Runtime, Readiness, and connection information
Console	Live output, command input, and prepared command actions
Players	Online/saved access-list information and supported player actions
Settings & files	Editable server files, text editing, structured editing, and setup
Worlds	Recognized worlds, world ZIP import, and world activation
Mods & plugins	Server-pack import, Mod & Plugin Manager, and metadata compatibility checks
Backups	Full-server backup, verification, and restore
Schedules	Existing Synix restart and maintenance settings
Change recovery	Recorded changes and supported undo actions
Diagnostics	Recent log/crash hints, readiness, compatibility, and process resources

Actions depend on the edition, running state, installed files, and available management channel.

Console and player management

The Console page supports the available Synix-managed console, localhost management channel, or optional Java RCON. Hidden native console windows can still have a working local command channel.

Choose a quick command to prepare it, review its player/message arguments, then send it. Commands remain in Minecraft's original syntax, not the UI language.

Supported actions include announcements, player lists, kicking, operators, allowlists, time/weather, and saving. Java-specific ban/pardon commands are not offered as Bedrock commands. Operator access grants powerful permissions; do not give it merely to troubleshoot joining.

Players can include online names and saved access-list entries. A player count is not a named roster, and an empty names table does not prove the server is empty. Refresh and check the available command channel before drawing conclusions.

Minecraft player tools are consolidated here instead of duplicating the generic Player Management Center entry in Server Options.

Use Synix Stop/Restart for lifecycle changes so the watchdog recognizes intentional shutdown. Keep RCON/admin endpoints private unless you have a secured remote-administration arrangement.

Settings and synchronization

Use Settings & files → Edit File for text edits or Structured Editor for format-aware editing. Stop first.

Saving known server.properties values updates the matching Synix entry, including supported ports, player limit, world, seed, mode, and command-channel settings. The advertised MOTD is separate from the local entry name. Mod-specific keys stay in the mod's own files.

Synix also re-reads supported properties before setup/start and on Refresh while stopped. Invalid external edits or conflicting ports must be corrected before proceeding. An editor will not overwrite a file that changed after it was opened.

See Configuration Editor for shared-field mapping and failed-save recovery.

Change versions or loaders

1. Make a full backup, including worlds and configs, and stop the server.
2. Open Setup, choose the target version/runtime/build, review, and save.
3. Choose Apply Runtime in the Control Center.
4. Review and finish the preparation/change operation.
5. Start manually and check the console and a matching client.

Runtime preparation uses the official provider and preserves world folders and server.properties. Synix records supported replaced runtime files for change recovery. Start is blocked when a recorded installed runtime and the selected profile disagree.

Changing runtime files does not convert every world or modpack. Never assume a world opened by a newer game or different mods can safely be downgraded. Restore its matching full backup when necessary.

Import or update a complete server modpack

1. Stop and back up the server.
2. Set and Apply Runtime for the pack's exact Minecraft version, loader, and build.
3. Open Mods & plugins → Import Server Pack.
4. Select a supported Modrinth .mrpack or a complete server ZIP containing actual mods/plugins and configuration.
5. Enable Include optional server mods only if wanted. Client-only Modrinth entries and client overrides are not imported.
6. Review hashes, metadata/scan results, skipped content, and every added, replaced, or removed file.
7. Confirm the import, then start manually and test.

The pack importer handles supported content such as mods, plugins, config, defaultconfigs, kubejs, and scripts. It does not run pack-supplied launch scripts, overwrite root server.properties, or replace worlds.

A CurseForge client manifest without the actual server files is not a complete server pack. Obtain the author's server package. Synix does not bypass private downloads, provider restrictions, unsupported hosts, or unsupported loaders.

Modrinth downloads are hash-checked. Supported JAR metadata is inspected without running it for loader mismatches, client-only content, duplicate IDs, and declared dependencies. Complex version ranges and incomplete/legacy metadata need manual review. No detected conflict is not proof of safety or compatibility.

For individual files/packages, use Mod & Plugin Manager.

Updating the same pack

Use the same server-ZIP filename for later versions so Synix can identify the pack. Reimport can remove JARs previously managed by that pack but absent from the update only if their recorded hashes still match.

Unmanaged JARs and worlds are not removed. New pack configuration files can replace older configuration; inspect the preview and retain a backup of custom settings.

Worlds

Import World ZIP imports one recognized matching-edition world into a new named folder. It does not overwrite an existing world or convert Java to Bedrock.

Choose an installed world and Activate World to update level-name and Synix's world setting together. The next start loads it.

Changing a seed affects generation of a new world, not existing terrain. Preserve the complete world, including edition-specific associated data, before experimenting.

Change recovery versus full restore

Change recovery → Undo reverses recorded file changes. It restores preserved originals or removes files introduced by that operation. It refuses to overwrite subsequent edits.

Switch away from an imported world before undoing its import. A pending recovery blocks Start until restored files and saved settings agree. Older unrecorded installations may require a full backup for runtime recovery.

After a full-backup restore, earlier workspace changes remain visible as replaced by that backup and cannot be undone against the restored files. New edits/imports create new change records.

A full backup is independent of these receipts and is the right recovery unit for world changes made after playing.

Backups, schedules, and diagnostics

Backups cover the installation folder; check for saves stored elsewhere. Verification and full restore share the same backup/recovery workflow used by other supported servers.

Schedules opens Synix's existing automation settings. It does not create a second scheduler. Review player waits, maximum delay, backups, and updates before enabling unattended work.

Diagnostics searches recent log/crash tails for common runtime, memory, dependency, port, world, and tick-related errors. Findings are clues, not confirmed causes. “No recognized pattern” does not mean the server is healthy.

Process CPU/RAM is not Minecraft TPS/MSPT. Use a compatible in-server profiler when investigating tick performance.

Common problems

Symptom	First check
Runtime selection does not match installed server	Review Setup and Apply Runtime; do not bypass a pending recovery
Modpack rejected	Complete server package, correct loader/version, supported download source, and package warnings
Client cannot join	Edition, game/loader/mod versions, required client mods, and actual game port/protocol
Player commands disabled	Running server and working edition-appropriate console/management connection
Edited value looks old	Save completed, correct file, stopped Refresh/reopen Setup, and no sync error
One very long console line	Confirm current version; inspect wrapped output/latest game log rather than treating it as proof of a hung game

For support, include edition, version, runtime/build, action, and a redacted log excerpt. Never publish RCON passwords or private server files.