Controls, worlds, and safety
What start, stop, and console commands actually do to your world.
Start and stop controls manage the running server for approved pilot accounts. World files use persistent storage separate from the running instance. Stopping is not the same operation as deleting a server.
Persistent storage is not a backup. When private Civo S3 storage is configured, configuration deployments stop the server and verify an off-node archive before applying changes. A backup failure prevents the apply step. Settings offers backup restore and Java save import when the required storage and runtime permissions are configured. These restore into fresh storage and retain the previous volume. Do not entrust your only copy of an important world to a pilot; begin with a disposable test world. Console commands can change or damage a world, so only send commands you understand.
Change settings or mods
Open your world's Settings. Edit game mode, difficulty, player limit, message of the day or Fabric mods, then choose Review changes. Review shows mod additions/removals and resolved version pins, including required dependencies and client-required mods. Modrinth compatibility metadata is checked, but cannot guarantee mods will work together at runtime.
Back up and deploy stops Minecraft, verifies the private backup, applies the new configuration and waits for the new pod to become ready. History shows each real attempt; you can close the tab and return. A failed startup does not automatically restore files. Minecraft version, loader, seed and generation are not editable on an existing world in this release.
Advanced settings expose approved server.properties, exact Modrinth version IDs, and a JVM profile. They edit the same draft as the simple controls; switching Advanced off doesn't reset them. Arbitrary files, JVM arguments and RCON secrets cannot be edited here.
If an operation remains stuck, Stop and recover becomes available after two minutes. It fences the old worker and stops the server before unlocking. It does not restore a backup or restart Minecraft. Contact the operator if recovery cannot be confirmed—never delete runtime locks blindly.
Console
Logs refresh every five seconds while visible. Command output and per-world history remain separate from the log tail. Quick commands fill the input; they are only sent when you choose Send. RCON stays private to the pod. A timeout is not proof that a command didn't execute; inspect the world before repeating it.