Granting admin rights allows you to manage your server easily and comprehensively with full control. As an admin, you can apply all available game options and functions directly in-game. Below, you will find all the necessary steps to assign admin rights to your server.
Admin rights are configured via the server configuration file. You can access your server's configuration files in the Configuration tab (raw text view). There you will find an overview of available configuration files. Open server.DZ.cfg by clicking the blue button.
In the configuration file, you should find the entry passwordAdmin. Here you must set the desired password for access. Enter your chosen password and click the Save button at the bottom.
To apply the change, the server must be restarted. Then connect to your server and open the in-game chat. Execute the following command to log in as an admin:
#login password
Here is a list of some available commands you can use with your administrator rights:
| COMMAND | DESCRIPTION |
|---|---|
| #login adminpassword | Log in as the server admin. |
| #logout | Admin logout. |
| #mission filename Difficulty | Select a mission by known name and set the difficulty – the difficulty parameter is optional; if not set, the current difficulty remains. |
| #missions | Select a mission. |
| ##restart | Restart a mission. |
| #reassign | Restart completely and reassign roles. |
| #shutdown | Shut down the server. |
| #restartserver | Restart the server. |
| #shutdownserveraftermission | Server shuts down after the mission ends. |
| #restartserveraftermission | Server restarts after the mission ends. |
| #init | Reloads the server configuration file loaded with -config options. |
| #exec ban Name#exec ban ID#exec ban #Player | Allows you to ban a player. |
| #kick Name#kick ID#kick #Player | Allows you to kick a player from the server. |
| #monitor (interval in seconds) | Shows server performance info. If interval is 0, monitoring stops. |
| #monitords (interval in seconds) | Shows performance info on the server console. If interval is 0, monitoring stops. |
| #debug off | Disables debugging. |
| #debug (interval in seconds) | Default interval is 10 if no other interval is chosen. |
| #debug (command) (parameter) | Available commands include: JIPQueueuserQueuecheckFiletotalSentuserSentuserInfo. You can disable any command by appending the parameter off, e.g. #totalSent off. Output varies by command; some write to log files, others to screen, etc. Note that you need a debugger that can intercept OutputDebugString on the client machine. |
| #debug (command) | Admin logout. |
| #logout | There are two available commands: console - sends what is in the server console to the sender; from - outputs to the log file defined in server.cfg, e.g. logfile might be "server_console.log". You receive confirmation of these commands in chat channels. |