This guide covers admin setup, commands, player management, world management, and troubleshooting for your Craftopia dedicated server. Craftopia is an open-world survival crafting game with farming, exploration, hunting, and factory automation. For initial server setup, configuration, and connection instructions, see Craftopia Server Setup Guide.

1. Admin Setup

Craftopia dedicated servers use a host-based permission model. The server operator manages the server through the configuration file and the GPanel console.

Server Operator Access

As the server operator, you manage your Craftopia server through:

• GPanel Console: The server console in GPanel displays server output, player connection events, and error messages.
• Configuration file: The ServerSetting.ini file controls all server settings. Edit it via the Files tab in GPanel or via SFTP. See Craftopia Server Setup Guide for details.
• In-game host controls: When connected as the host, you may have access to additional management options through the in-game menus.

2. Admin Commands

Craftopia provides server-side commands that can be entered through the GPanel console or in-game console (when available). Below are the key commands for server management.

3. Player Management

Kicking Players

To remove a disruptive player from the server:

• Use the kick command in the GPanel console with the player's name or Steam ID.
• Alternatively, use in-game host controls if available through the player list menu.
• As a last resort, restart the server from GPanel to disconnect all players, then set a password to prevent the disruptive player from rejoining.

Banning Players

To permanently prevent a player from joining:

• Use the ban command in the GPanel console.
• Banned players are tracked by Steam ID and will be rejected on future connection attempts.
• To reverse a ban, use the unban command with the same player identifier.

Password Protection

The most reliable access control method is setting a server password:

ServerPassword=YourSecretPassword

Only share the password with trusted players. Change it in ServerSetting.ini and restart the server for it to take effect.

4. World Management

Resetting the World

To completely wipe the world and start fresh:

1. Stop the server from GPanel.
2. Connect via SFTP and navigate to the Saves/ directory.
3. Delete or rename the world save folder (rename to keep as backup, e.g., Saves_backup/).
4. Optionally change the WorldSeed in the configuration for different terrain.
5. Start the server. A fresh world will be generated.

Switching Worlds

You can maintain multiple worlds by managing save directories:

1. Stop the server from GPanel.
2. Rename the current Saves/ directory to something descriptive (e.g., Saves_world1/).
3. If you have a previous world, rename it back to Saves/.
4. Start the server. It will load whatever is in the Saves/ directory, or generate a new world if empty.

Auto-Save Management

Configure auto-save frequency in ServerSetting.ini:

AutoSaveInterval=300

The value is in seconds. Default is 300 (5 minutes). Lower values provide more frequent saves but may cause brief pauses on larger worlds. Set to 0 to disable auto-save (not recommended).

5. Troubleshooting

Server Crashes on Startup

• Check the GPanel console for error messages. Common causes include malformed configuration syntax.
• Verify port values have not been manually changed. Ports must match what GPanel assigns.
• Try deleting ServerSetting.ini and restarting to regenerate a fresh config with defaults.
• If the crash is save-related, try renaming the Saves/ directory and starting with a fresh world.
• If the crash persists, open a support ticket with your server IP and the full console output.

Players Cannot Connect

• Verify the server is running in GPanel and check the console for errors.
• Confirm the player is using the correct IP and port from the GPanel Network tab.
• Check that the server password is correct (passwords are case-sensitive).
• Ensure the server has not reached the MaxPlayers limit.
• Verify both the server and the player are running the same version of Craftopia. Game updates can temporarily break compatibility.

Server Not Appearing in Browser

• New servers can take several minutes to appear. Try direct connect while waiting.
• Restart the server if it has been running for a long time without appearing in the browser.
• Players can always connect via direct IP as a workaround.

Performance Issues

• Large builds with many automation setups can increase server load. Consider simplifying complex builds.
• Reduce MaxPlayers if the server struggles with many concurrent players.
• Increase AutoSaveInterval if saves cause periodic lag.
• If performance remains poor, contact support about upgrading your server plan.

Save Corruption

• If the server crashes during a save, the save file may become corrupted.
• Restore from a manual SFTP backup if available. See Craftopia Server Setup Guide for restore instructions.
• Regular SFTP backups are the best protection. Back up your world at least once per play session.

Related Articles

• Craftopia Server Setup Guide
• How to Find Your Server IP and Port
• How to Upload Files via SFTP
• Server Startup Guide

Need Help?

If you run into issues with your Craftopia server that are not covered here, open a support ticket and include your server IP, a description of the problem, and any relevant error messages from the GPanel console.