A task is a configuration from which services can be started.
The configuration path for each task is
After changing a configuration, you need to execute
tasks reload in the console.
We recommend managing the configurations with the tasks command. In that case you do not need to keep an eye on the json syntax, and you do not need to reload the configurations after changing anything.
This defines the name used along with the incremental id to identify services started from this task (e.g.
Proxy will result in
This sets the runtime used for services started by this task.
By default, CloudNet only provides the "jvm" runtime, you can add your own with custom modules.
Enables or disables the ip rewrite for services of this task (
We recommend the usage of this feature just in very special cases.
For example, when you want to have several proxies for the Bedrock Edition. (Unfortunately, the Bedrock Edition does not support SRV-Records. Please contact us in that case for further assistance!)
Enables or disables the maintenance mode services of this task (
If the maintenance mode is enabled, services of this task can have a special sign layout and users need the permission
cloudnet.bridge.maintenance to join.
This enables or disables the automatic deletion of service files after they have been stopped. (
Do NOT use this feature to keep persistent data of services like CityBuild. Please use static services instead!
This enables or disables static services. (
If disabled, services will be started in the
If enabled, services will be started in the
Here you can specify on which nodes the services from this task should be started.
If you leave the option empty (as it is by default), the services can be started on every node.
Example (starting the services on Nodes 1, 2 and 4):
Here you can specify to which groups the task should belong.
Here you can specify files which should always be deleted after stopping the server.
This options works even when static services are enabled!
The environment services of this task should run in. Possible values are:
This defines the memory size (RAM) for services of this task.
Here you can set custom jvm options. (For example the Aikar garbage collector flags options)
Here you can set custom process parameters.
This is the port from which the cloud will use ports for the services.
You can use the same start port for multiple tasks, the system will use the next available port.
This defines the minimum amount of services that should be always online from this task.
The includes provides the possibility to download files when each service is prepared.
This is an array of template configurations.
This means you can add multiple templates to one task. For example for different maps:
The deployments provide the possibility to copy each service to a template when it is being shutdown.
The properties can contain any json object which you can access trough the api.
By default, it contains only the SmartConfig from the Smart Module