A list of daemons this server can be assigned to. If the setting is changed you will have the choice between just changing the daemon ID of the server without transferring files or automatically transferring server files to the new daemon and changing the setting automatically as soon as the transfer has succeeded

The name of the server executable file. Empty for default. Settings specific to this executable will be loaded from the .conf file matching the executable name. For example "minecraft_server.jar.conf" for the name "minecraft_server.jar"

Advanced Server Settings

Should not usually be changed. Leave empty to generate automatically as "serverX" where X is the server ID. This is the directory where all server files will reside, it's a sub-directory of the "servers" directory

Server JAR directory
The "jar" directory inside the server directory. If the JAR file is not found here it will be copied from the daemon "jar" directory

Server base directory
The server directory itself. If the JAR file is not found here it will be copied from the daemon "jar" directory

When using something other than "Daemon JAR directory" you need to run the daemon in "multiuser" mode. Please also see the following security recommendation.
When this as well as the "Owner selectable JAR" is enabled the user will also have the option to enter an arbitrary JAR name.
Default: Daemon JAR directory

This determines how replies to the status command ("list" for Minecraft) are handled. Options:

Known console output
Treat any kind of recognized console output as a sign that the server is still running. This includes replies to the status command, player connects/disconnects, error messages, chat, etc.

"List" command output
Require a recognized format of the "list" command output in reply to using the "list" command in order to consider the server still running.

Any console output
Any kind of console output from the server will be accepted as a sign that the server is still running

Panel Configuration

The contact email of the administrator of this panel. Setting this will enable the "Support" menu entry. This is required for the "Welcome" and "Assign" email functionality as well as password resets to work

When enabled allows every user to generate their own API key. This is not recommended unless you want to enable users to be able to use external apps to manage their server. We suggest disabling user registration when this is enabled
Default: No

When enabled displays the input field at the bottom and newer messages get added at the bottom. When disabled the field will be at the top with new messages added at the top (this was the old behavior)
Default: Yes

This enables the MySQL database provisioning feature under "Advanced">"MySQL Database". The servers still need to have the "Owner can create MySQL DB" setting enabled for the owners to be able to use this themselves.
For this feature to work at least the DB Host, Username and Password have to be specified
Default: No

The hostname of the DB server to be used for user created MySQL databases. We recommend using a separate MySQL server for these databases. This can also include a port, for example "localhost;post=3306"

Timeout in seconds for connections to the daemon. When your panel frequently loads for a long time because a daemon is not reachable try reducing this. Similarly, if you're getting "Empty Response" errors for daemons that are up but potentially overloaded, try increasing this
Default: 5

When a daemon times out it will be marked as offline for this number of seconds. Offline daemons are not sent any commands to avoid slowing down panel load times. When daemon connections are usually stable you can safely increase this. If your daemon connections are unstable and time out frequently you might have to lower or disable this. Use 0 to disable this feature
Default: 10

Allowing IP changes means that the login session will be considered valid even if a users IP changes. This is useful when logging in on mobile devices but it also means that stolen session cookies will be valid. Then this is enabled IP changes will be allowed by default
Default: No

When using a 2.0.0+ panel with daemon versions prior to 2.0.0 you need to enable this setting
Default: No

Configuration Files

Configuration files shipped with the Multicraft package are named ".conf.dist" in order to avoid overwriting your existing config files. To enable a config file, simply remove the ".dist" part and edit the file to suit your needs.

Daemon: multicraft.conf

This is the main configuration file of the daemon. All settings are documented directly in the multicraft.conf.dist that comes with the downloaded Multicraft archive. The setup.sh script will set the most relevant settings but you might still have to fine tune certain settings like the amount of memory available to the daemon if you're using billing system integration.
Most settings in that file can be changed at runtime but the daemon needs to be informed of the change in the panel under "Settings">"Operations">"Reload Daemon Config File"

Daemon: scripts.conf

This file can be used to configure scripts that can be run directly from the panel. The available settings are documented in the file itself. Additional help can be found here: Running Scripts

Daemon: default_server.conf

This file sets the default settings that are not defined in server executable .conf (see jar/*.conf below) files or if the executable .conf file doesn't exist. The format is the same as for these .conf files

Daemon: server_configs.conf

This file defines the config file to use depending on the server executable name. If there is a conf file for the executable file name (e.g. craftbukkit.jar.conf for craftbukkit.jar) then this file is ignored, otherwise it will be used to determine the conf file to use. The available settings are documented in the file itself.

Daemon: templates/*/template.conf

Every template can optionally provide a template.conf file. Available settings are documented in the template.conf that comes with the sample template "cleanmodsplugins": "templates/cleanmodsplugins/template.conf".

Daemon: jar/*.conf

Panel: protected/config/config.php

This is the main panel configuration file. You should not have to edit it manually since the front end installer (install.php) initializes it for you and you can change most settings directly in the panel under "Settings"->"Panel Configuration". When you need to change the database connection details you can do so by either editing this file or by re-running the front end installer.

Panel: protected/config/internal/application.php

This file should not usually have to be changed but certain features can be enabled by editing it, for example: