Configuration Editor
Guides and release notes are shown in their original language.
On this page
← All guides · MANAGE & MAINTAIN
Use Configure for common server fields. Use Server Options → Open Config Editor for the game's actual files. Minecraft also exposes its files in Minecraft Control Center → Settings & files.
Save a configuration safely
- Stop the selected server through Synix and wait for its tracked processes to exit.
- Back up the affected configuration and any important world data.
- Open the correct file for that server. Some games have multiple files or configuration instances.
- Use Search and the type filter to find settings. Keep game keys, maps, and accepted values in the game's original syntax.
- Review your changes in Structured View and Raw Preview, and resolve validation errors.
- Click Save Changes. Synix checks the file and the shared settings mapped by that game's definition.
- Confirm the save completed, then reopen Configure to check the updated common fields.
- Start manually and confirm the intended settings/world in the game's log.
A file changed by another editor or the game since you opened it is not silently overwritten. Reopen it and compare the new contents.
Saving also updates Synix
The editor's Save action updates matching, supported fields in the selected server's entry in servers.json, then refreshes the dashboard. It is not limited to Minecraft.
The mapping uses the game, exact configuration file, section/nested location, and key. Synix does not scan unrelated files for a matching word or copy arbitrary mod settings into its database.
Examples of shared values, when defined for that game:
| Configuration information | Matching Synix information |
|---|---|
| Server name | Server entry/display name where the profile maps it |
| Game, query, app, or RCON ports | Corresponding network fields |
| Maximum players | Saved player limit; obsolete cached maximum is cleared |
| Server, admin, or RCON password | Protected saved credential field |
| World/save name, seed, size, mode | Corresponding world settings |
| RCON enabled, crossplay, invite code | Supported management/connection fields |
For both ARKs, the correct GameUserSettings.ini bindings include server/admin passwords and other shared fields. An identically named key in another section or an unrelated INI file is not a substitute.
For Minecraft, server.properties uses edition-specific rules, including Java escaping/continuations. The advertised MOTD is separate from the local Synix entry name. Unknown mod options remain in their own files.
Save also checks mapped values when you made no text changes. This can repair drift between the selected configuration and Synix's saved fields.
Missing keys do not mean “erase the Synix value.” Ambiguous duplicate keys and invalid mapped values produce an error rather than a guessed value.
Check Synix Values is not the Save sync
Check Synix Values compares the configuration with values managed by Synix and helps identify mismatches or missing managed fields. It is a review/repair tool.
If you intentionally changed a value in the game file, use Save Changes to synchronize that file's mapped value back into Synix. Read a proposed repair before applying it: a repair based on the old entry may not represent the edit you wanted.
Do not edit servers.json manually while Synix is running. Its passwords may be Windows-protected values, not plain text.
Formats and preservation
Supported editing includes INI/properties, JSON, XML, YAML, and profile-specific formats such as SII or space-separated settings. Only supported scalar/value edits are exposed; this is not a universal editor for every programming language or file.
The format-aware editor preserves surrounding structure, comments, order, quoting, spacing, and encoding where the supported parser can do so. A normal value edit is not a template reset.
YAML: nested mappings, indented lists, and supported single-line values are editable while retaining indentation/comments. Complex features such as anchors, aliases, inline collections, and multiline values are refused rather than rewritten unsafely. Use the game's supported tools for files outside this subset.
A syntactically valid file can still contain game-invalid settings. The game log and a real client test remain important.
If saving fails
Saving the file and updating Synix's shared fields form one coordinated operation. If persistence fails, Synix attempts to restore the original configuration and in-memory fields. It refuses to roll back over a newer external edit.
Read the error and preserve the named backup/recovery file. Do not repeatedly click Reset or discard recovery data. A secondary recovery failure needs attention before starting the server.
Saved credentials in Synix remain protected for the current Windows user; the game may still require readable passwords in its own config or launch arguments.
External edits and restored backups
An edit made entirely outside Synix does not automatically trigger the editor's Save workflow for every game. Reopen the correct configuration in Synix and save it to reconcile mapped fields.
Minecraft additionally re-reads supported properties before setup/start and on stopped-server Refresh. Do not assume this is a live filesystem watcher for all games.
After a full-server backup restore, Synix re-reads the game's mapped configuration fields before declaring recovery complete. If that settings update fails, the files may already be restored but Start is blocked until the pending sync succeeds. See Workflow Safety & Recovery.
Repair, templates, and reset
- Normal save: writes the intended supported value edits and syncs mapped fields.
- Fix Config / repair: addresses supported missing or invalid managed settings; read the proposed changes.
- Reset/template replacement: can restore defaults and remove customization. Back up first.
Some games generate files on first start; others have complete built-in templates. A template revision can preserve a one-time copy named .synix.before-template-v<revision>.bak. Ordinary configuration writes can also retain a .synix.bak copy. These are useful recovery files, not substitutes for independent full backups.
Do not use a configuration reset to “fix” missing runtimes, occupied ports, or incompatible mods.
Related: Server Setup · Minecraft · Backups