How to Set Up Admin on Your Trackmania Server

Trackmania admin is password based. There are three levels, each with its own password, and the level you authenticate at decides what you can do.

Set the passwords

1. Stop the server.
2. In the panel open Files and edit:

   UserData/Config/dedicated_cfg.txt

3. Set a strong password on each level in the authorization_levels block:

   <level>
     <name>SuperAdmin</name>
     <password>a-long-password-here</password>
   </level>

4. Save and start the server.

Change the shipped defaults. They are published in every setup guide, and a server left on them is open to anyone.

The three levels

• SuperAdmin, every command including server shutdown and config changes. Keep this to yourself.
• Admin, day to day moderation and map control. This is what staff get.
• User, a limited set. Usually left with no password.

Administering in game

Join the server and authenticate at the level you want using the in-game admin interface or chat command your build provides. Once authenticated you can:

• Kick and ban players.
• Skip or restart the current map.
• Change the match settings in use.
• Force a player into spectator mode.
• Send a server message.

XML-RPC and admin tools

Trackmania's real administration interface is XML-RPC. Server controllers connect to it and provide records, chat commands, map voting and statistics.

• Your server has an XMLRPC_PORT allocated to it, shown on the server overview. Set that value in the system_config section of the dedicated config.
• A controller authenticates with the SuperAdmin password, so it has full control. Run it somewhere you trust.

The panel Console section is attached to the server process and shows everything it logs, which is the quickest way to see whether a controller has connected.

If admin does not work

• Passwords are case sensitive.
• The server must be restarted after editing the config.
• Check the XML is still valid. An unclosed tag stops the server from starting, and the console says where.
• If a controller cannot connect, confirm the XML-RPC port in the config matches the allocated one exactly.