World save access
Upload compatible worlds and download full backups before changes or updates.
Host a persistent engineering sandbox with access to world saves, workshop content, scenario settings, player limits, backups, and advanced configuration.
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.
Upload compatible worlds and download full backups before changes or updates.
Configure supported mod and item IDs while monitoring compatibility and load order.
Adjust block limits, multipliers, environment settings, passwords, and server visibility.
Manage admins, promoted users, bans, and remote administration options.
Large grids, scripts, physics, players, and mods can require additional CPU and memory.
Use console output, logs, schedules, and backups when managing the world.
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. Transfer the full world save and configuration, then confirm the server version and world path before startup.
Yes, when the dedicated server supports them and the mod IDs are configured correctly. Large collections may increase startup time and resource use.
Physics, programmable blocks, scripts, large grids, floating objects, mods, and many players can all increase simulation load.
Yes. Supported sandbox and session settings can be edited in the world or server configuration files.
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.