Serverconfig control
Edit game name, passwords, slots, difficulty, loot, day length, and other supported settings.
Run a private or public survival server with configuration access for worlds, difficulty, player limits, mods, scheduled restarts, and backup protection.
Plan size and configuration should reflect the world, players, content, and server software—not only the game name.
Exact compatibility depends on the server version, plan, and third-party content.
Edit game name, passwords, slots, difficulty, loot, day length, and other supported settings.
Use supported pre-generated maps, random worlds, or compatible uploaded saves.
Upload server-side mods and configuration files through SFTP or the panel.
Plan restarts, shutdown warnings, backups, or wipe-related tasks.
Manage permissions, admins, bans, and server tools in supported configuration files.
Review startup output, connection messages, and game commands.
Use the panel for routine work and SFTP when you need deeper file access. Available quotas and limits depend on the selected plan.
Contact support when your setup falls outside these general answers.
Yes, when the files and version are compatible. Upload the complete world and save folders and update the relevant serverconfig settings.
Server-side mods can be uploaded to the appropriate Mods folder. Players may also need matching client files depending on the mod.
Panel schedules can help automate backups, stops, and other maintenance, but wipe steps depend on the world and save structure.
World size, players, zombie activity, mods, map generation, and server settings can all affect resource use.
Choose a plan in the shop, or send your player count and content list for help deciding.
Plan availability, resource limits, and supported add-ons may change. Confirm unusual requirements before ordering.