Server Configuration & Dashboard
Guides and release notes are shown in their original language.
On this page
← All guides · EVERYDAY USE
The dashboard manages your local server entries. Select the intended row before using Readiness, Server Options, Configure, Start, Restart, or Stop.
Read the dashboard
Search filters the server list; the status filter narrows it further. Activity & Diagnostics explains ongoing work and errors. Clearing visible activity is not the same as deleting all saved logs.
Top-level CPU/RAM figures describe host resource usage. Use Live Process Details for tracked server processes. A running process is not proof the game finished loading or is reachable by internet players.
Player counts depend on the game's supported query/management channel. N/A does not mean zero. Counts and named-player management are separate capabilities.
Add or import
Add Server offers new-server setup, existing-server import, and the Game Support Catalog.
Creating an entry uses the selected profile's download, configuration, and launch behavior. Import Existing Server registers an installation in place rather than reinstalling it.
The catalog distinguishes available definitions from recorded verification. A listed game is not a guarantee that every action, mod, or version has been tested.
The four setup steps
| Step | What it does |
|---|---|
| 1 — Server details | Choose the server name, game, and applicable edition/version/runtime |
| 2 — Required settings | Complete the game-specific mandatory fields and validation |
| 3 — Review | Display and review the current settings summary |
| 4 — Save Server / Save Changes | Save only after the valid current settings have been reviewed |
Once required settings pass, select Review in the setup strip. The summary must be shown before Save is enabled. The same review gate applies when editing an existing entry.
Changing settings invalidates the previous review. A queued click or Enter must not save unseen choices. If Save is disabled, read the status message, resolve errors, and open the current Review again.
Configuration pages
| Page | Common contents |
|---|---|
| General | Name, game/edition/version, loader/framework, player limit, and applicable world/mode/RAM fields |
| Security | Supported server/admin passwords and required service credentials |
| World Generation | Supported map, seed, world-size, and generation choices |
| Network & RCON | Game/query/app/admin endpoints, RCON, and supported crossplay options |
| Automation | Backup/update on start and restart/maintenance scheduling |
| Discord | Notification destinations and event routing |
| Install & Launch | Installation folder and supported launch options |
Fields depend on the game definition. Hidden or unavailable options are not proof of a broken control.
Use Beginner mode for a simpler view and Advanced mode when you need supported technical fields. Keep machine-facing commands and values in the syntax expected by the game.
Seed controls respect supported game rules. A new seed does not rewrite terrain in an existing save.
Start, stop, and restart
Use Synix lifecycle controls rather than simultaneously running a second launcher.
Start can install/update required files, check prerequisites, finish pending recovery, and perform requested pre-start backup/update work before launch. If a required backup or requested update fails, the server stays stopped and the failure is shown.
Stop requests the supported graceful shutdown and checks the tracked process group. A timeout can lead to staged forced termination; unsaved progress can be lost. Wait for the result before starting another instance.
Restart is an intentional coordinated stop/start. Killing the process outside Synix can look like a crash to the watchdog.
External deployments such as Dune have different ownership/lifecycle limits.
Server Options
The menu adapts to the selected game and current state. It can include:
- Server/config/log/backup folders and configuration editing.
- Backup and restore, add-on management, and supported update/validation actions.
- Minecraft Control Center or Satisfactory Control Center.
- Supported player management, process details, connection information, and LAN/WAN tests.
- Launch-file export for eligible profiles and Delete Server.
Minecraft's Console and Players tools are inside its Control Center; the generic Player Management Center entry is not duplicated for Minecraft.
Availability depends on capability, runtime state, and whether another operation is in progress. Read the explanation instead of trying to bypass an operation lock.
Configuration file edits
Saving a supported game file in the Configuration Editor also updates mapped common values in Synix's selected entry and servers.json.
The match is based on the game/file/key mapping, not arbitrary similarly named settings. Reopen Configure after a successful save to see the new values. A config change outside Synix does not imply a universal live watcher.
Launch arguments and exported scripts
Synix already supplies supported managed arguments. Duplicating a password, port, mod ID list, or world argument can cause conflicts.
Create Batch File, where available, exports a resolved launch command. It can contain readable credentials and must be kept private.
Running an exported script separately does not provide all Synix operation locks, backups, scheduling, or watchdog coordination. Do not run it while the same server is active in Synix.
Delete a server
Stop first and preserve anything you want to keep. Read the named installation and the optional backup-deletion choice before confirming.
Deletion removes the selected server's installation and associated Synix add-on bookkeeping/recovery data. Backup removal is separately selectable. Shared paths and other server data must not be treated as disposable.
Do not delete the shared AddOns directory manually to clean up one entry. If deletion fails, read the error and inspect the recorded state before retrying.
Related: Readiness · Configuration Editor · Workflow Safety & Recovery