Mods & Plugins
Guides and release notes are shown in their original language.
On this page
← All guides · GAME CONTENT
Open Server Options → Mod & Plugin Manager. For Minecraft, you can also enter it from Minecraft Control Center → Mods & plugins.
Start with the downloaded package. You do not need to fill out “Import locations” before choosing a ZIP or folder.
Import a ZIP, mod file, or extracted folder
- Back up the server/world and stop it through Synix.
- Click Import ZIP / folder.
- Choose Choose ZIP or mod file or Choose extracted folder.
- Synix reads the package, looks for recognized metadata/layouts, and matches possible destinations to the selected game and loader.
- Review the proposed add-on system. If several fit, select the one actually installed on this server.
- Check Use files from when the archive has extra wrapper folders. Inspect both source and final destination paths.
- Click Review and import, then read the final checks, warnings, and changes before confirming.
- Wait for completion. Refresh the inventory, start manually when ready, and check the game log and a matching client connection.
Reading or canceling the preview does not install anything or start a server. Importing does not automatically restart one.
An extracted folder is captured for review. If the reviewed package changes before installation, Synix rejects the changed content instead of silently installing different bytes.
Read the four-part review
| Review area | What to verify |
|---|---|
| Compatibility | Correct game/edition, server-side package, loader, versions, and dependencies |
| Destination | Exact files and folders that will be added or replaced |
| Activation | Whether files are enough, or a config entry, load order, scenario selection, or provider ID is still needed |
| Recovery | What the recorded import can undo, and what requires a full world/server backup |
The importer handles recognized layouts and extra packaging folders. It cannot infer the meaning of every possible archive. A ZIP, DLL, or manifest by itself is not proof that it belongs on the selected server.
Manifests help; they are not universal instructions
Examples include Minecraft's fabric.mod.json, mods.toml, plugin.yml, and paper-plugin.yml; 7 Days to Die's ModInfo.xml; and ARK's edition-specific descriptors.
Synix reads supported metadata without executing it. The selected game's definition and loader determine the installation rules. Manifests do not override path restrictions, grant permission to run an installer, or prove server compatibility.
Dependencies, client installation, licenses, provider registration, and version constraints may still require the author's instructions. Missing dependencies are not silently resolved for every package.
Three different kinds of support
| Type | What it means |
|---|---|
| Managed local import | A recognized profile can preview/stage supported files and keep a rollback record |
| Provider-managed IDs | Synix saves the supported ID list; the game/provider downloads and updates the actual mods |
| Documented or detection-only support | The game has a documented method or recognizable folders, but may require manual loader, destination, and activation setup |
Mod support & setup shows the game's documented methods, review date, references, and whether Synix has automatic import rules. Needs verification does not mean “cannot be modded.”
The Game Mod Support catalog covers all 220 profiles retained after the Steam Download Audit. Update Synix if your installed build still contains an older catalog. Documented mod support and successful live install/start/stop/monitoring tests are separate things.
Built-in managed routes
| Game | Route | Important boundary |
|---|---|---|
| Minecraft Java | Loader mod JARs or server plugin JARs | Requires the matching loader/runtime; Java content is not Bedrock content |
| Rust | Oxide/uMod plugins in oxide/plugins | Requires a matching, detected framework |
| 7 Days to Die | Complete packages containing ModInfo.xml | Confirm the active Mods location for the server version |
| Empyrion | Complete scenarios or compiled server-mod packages | Scenario activation is a separate reviewed step |
| ARK: Survival Evolved | Ordered Steam Workshop IDs | Game/provider downloads; not a general file-copy install |
| ARK: Survival Ascended | Ordered CurseForge project IDs | Game downloads using launch configuration; not an offline ZIP deployment |
Minecraft complete server packs have a dedicated workflow in the Minecraft guide. ARK package inspection is explained in ARK mods. See Empyrion, Rust, and other game workflows.
When Synix cannot identify the destination
Read Mod support & setup and the game's/server loader's instructions first.
After choosing the package, Choose destination folder lets you select a confirmed subfolder inside this server. Synix derives supported file types from the package and shows a file-by-file preview. The location is remembered for this server only after confirmation.
Use Advanced: import locations to maintain those saved rules when necessary. It is not the normal first step.
This fallback copies supported files. It does not install arbitrary loaders, compile source, register provider-managed content, create game-specific load-order entries automatically, or bypass client requirements. A rule cannot write outside the selected server root.
If the game requires another data location or activation mechanism that the preview cannot represent, use that game's supported procedure instead of choosing an approximate folder.
Inventory and catalog
The inventory is based on supported content found on disk or in the provider ID list. Search and the selected install area affect which entries you see. Refresh after external changes.
Only changes recorded by Synix have its managed recovery information. A detected file that was installed manually is not automatically a Synix-managed import.
Browse Catalog opens provider websites. It is not a searchable universal in-app marketplace or an automatic dependency installer.
Simple view hides some technical controls, not safety checks. Use the selected row's detail area to read complete paths and status explanations.
Security checks
Imports validate paths, links, collisions, file types/signatures, package limits, and reviewed hashes, and use available Windows Defender scanning. Confirmed malware or unsafe layouts are blocked. An unavailable/inconclusive scan is not the same as a clean result.
These checks are not a sandbox or a guarantee that a mod is safe. DLLs, JARs, Lua, and C# plugins are executable server code. Use trusted sources and normal Windows permissions.
Provider downloads that have not happened yet cannot be scanned locally. Importing an ARK package to discover its ID does not verify the later provider download.
Update, remove, and recover
Back up first and stop the server before changing content.
Roll Back Import reverses the entire recorded import, which may include several add-ons. It restores saved originals and removes files introduced by that operation. It refuses to overwrite later edits or use damaged recorded originals. Roll back newer overlapping imports first.
For a provider-managed entry, Remove Selected changes the configured ID list. It does not delete provider caches, undo world changes, or restore an older provider version.
Removing a mod can make a world unloadable or remove its content. A file rollback is not a world rollback. Keep a matching full backup.
Deleting a server through Synix also removes that server's associated Synix add-on bookkeeping/recovery data; optional backup deletion is a separate confirmation. Do not delete the shared AddOns root to clean up one server.
Related: Backups · Workflow recovery · Game mod catalog