Servers
Learn how to manage individual server instances in SimpleCloud
Overview
Servers are individual Minecraft instances that SimpleCloud creates and manages based on your group configurations. Each server:
- Inherits its base configuration from its parent group
- Has a unique identifier (e.g.,
lobby-1,survival-3) - Can be individually managed and configured
- Automatically scales based on player demand
Server Lifecycle
Creation and Startup
Servers are automatically created when:
- The configured minimum online count hasn't been reached
- You manually start a server
- Player count requires more capacity based on your scaling settings
Runtime Operation
During operation, servers:
- Report their status to the SimpleCloud controller
- Handle player connections
- Can be modified with certain settings without requiring restarts
Shutdown
Servers are gracefully stopped when:
- You manually stop them
- They're no longer needed (player count decreases)
- The cloud system shuts down
Server States
Servers transition through different states during their lifecycle:
- PREPARING: Server files are being prepared
- STARTING: Server is starting up but not ready yet
- RUNNING: Server is operational and can accept players
- STOPPING: Server is in the process of shutting down
- STOPPED: Server has been fully stopped
You can view the current state of all servers using the simplecloud info servers command.
Managing Servers
Starting a Server
To start a specific server instance:
Example:
Stopping a Server
To stop a running server:
Example:
Editing Server Properties
Some properties can be modified while a server is running:
Available flags:
-P, --max-players uint: Change the maximum player limit-r, --properties stringToString: Modify custom properties (key=value pairs)
Examples:
Custom properties can be accessed by plugins through the SimpleCloud API to enable custom behaviors and configurations.
Server File Structure
Here is the typical file structure for running servers: