Customizing your game server: configs, mods, and performance

One-click deploy gets a game server online in minutes, but the fun really starts when you make it *yours*: custom rules, mods, plugins, a tuned config and a world that runs smoothly under load. On a Nxeon game server you get full file and FTP access plus dedicated resources, which means none of this is locked behind a restrictive panel — you can shape the server exactly how your community wants it. Here's how to go from a stock deploy to a customized, well-tuned server.

Know your server's file layout

Every game server keeps its settings in files. Before changing anything, get oriented:

• The main config — for Minecraft that's server.properties; for Valheim, launch arguments; for Rust, a startup config and console commands. This controls the fundamentals: name, player slots, difficulty, world seed, ports.
• World/save data — the directory holding your persistent world. Back this up before any big change.
• Mods/plugins directory — where add-ons live (mods/ or plugins/ in many games).
• Logs — your first stop when something misbehaves.

With full file and FTP access on Nxeon, you can reach all of these directly rather than being limited to whatever a locked-down control panel chooses to expose.

Editing the core configuration

Start with the main config file. Common things people change first:

• Server name and message of the day — how your server appears in listings.
• Player slots — match this to the resources your plan provides; overselling slots is the fastest route to lag.
• Difficulty and game rules — PvP on or off, keep-inventory, mob spawning, day length.
• World seed — set this before first launch to start on a specific map.
• Whitelist/allowlist — for a private community server, restrict who can join.

Edit the file over FTP or in the terminal, save, and restart the server for changes to take effect. Always keep a copy of the original so you can revert a change that doesn't land well.

Adding mods and plugins

This is where a server becomes distinctive. The workflow is broadly the same across games:

1. Match the loader and version. Mods and plugins target a specific server type (e.g. Fabric, Forge, Paper/Spigot) and game version. Mismatches are the number-one cause of crashes — check compatibility first.
2. Drop them in the right folder. Upload the mod/plugin files to mods/ or plugins/ via FTP.
3. Restart and read the logs. Watch startup for errors. A failed mod usually announces itself clearly in the log.
4. Add one at a time for big changes. When installing several, add them in batches so that if something breaks, you know which one did it.

Plugins (server-side only, like Paper plugins) are easiest because players don't need to install anything. Full mods (like Forge/Fabric mods) are more powerful but often require players to run a matching modpack.

Tuning performance

Dedicated resources give you room, but a busy world still benefits from tuning:

• Right-size the memory. Give the server process enough RAM for your player count and mods, but not so much that garbage-collection pauses grow. For Java games, set sensible heap flags rather than throwing the whole box at it.
• Limit view/simulation distance. In Minecraft, a smaller view distance dramatically cuts CPU and memory load with little impact on play. This single setting fixes most "why is it lagging?" complaints.
• Prune entities and chunk loading. Runaway mob farms and always-loaded chunks are common culprits. Plugins exist to cap and clean these up.
• Keep mods lean. Every mod costs something. Remove ones nobody uses.
• Watch the metrics. Live CPU and memory graphs tell you whether you're near a limit — and whether it's time to scale up.

Because your Nxeon game server has dedicated resources rather than a slice shared with noisy neighbours, the performance you tune for is the performance you actually get.

Managing the server day to day

• Back up before you tinker. Snapshot or copy the world directory before installing mods or editing configs. Nxeon's backups are a safety net, but a quick manual copy before a risky change is smart practice.
• Use FTP for bulk file work. Uploading a modpack or swapping a world is far easier over FTP than command by command.
• Automate updates where you can. Auto-updates keep server versions and mods current so your world is always ready — but pin versions when you're running a delicate modpack that breaks on upgrades.
• Scale when you outgrow the tier. If your crew grows and the metrics say you're maxed out, bump RAM, vCPU and slots in a moment rather than starting over.

Troubleshooting the usual suspects

• Server won't start after adding a mod? Version mismatch — check the log, remove the offending mod, confirm loader/version compatibility.
• Persistent lag? Reduce view/simulation distance first, then look for entity build-ups and check whether you're at a resource limit.
• Can't connect? Confirm the port is open and forwarded — our port checker (/tools/port-checker) tells you whether it's reachable from the internet.
• Corrupted world after a crash? Restore from a backup or snapshot — the reason you take them.

Make it yours

A stock server is a starting point. With full file and FTP access, dedicated resources and the freedom to add any compatible mod or plugin, your Nxeon game server can become exactly the world your community wants — tuned, modded and smooth. Explore game server plans and supported titles at /game-servers, and check reachability any time with /tools/port-checker.