TAMods-Server does not yet support the
/sc commands used to run administrative commands on official servers. Support for this may come in future, but TAMods-Server has its own administration system.
The admin system is based on defining roles which are attached to a set of commands they are permitted to run. Additionally, roles may have the
canExecuteLua permission, which allows them to execute raw Lua on the server. Giving this permission to untrusted roles is dangerous, as users are effectively allowed to execute arbitrary code.
To create and remove roles, you can use the functions:
Admin.Roles.add(name: string, password: string, canExecuteLua: boolean)
This adds a role with the given name and password, and defines whether this role has the
This removes the role with the given name from the pool of roles that a user may log into. It does not immediately log any users out of that role.
Admin.Roles.addAllowedCommand(rolename: string, commandname: string)
This adds permission for the role to execute the given command.
Admin.Roles.removeAllowedCommand(rolename: string, commandname: string)
This removes permission for the role to execute the given command.
This example creates an admin role that can execute Lua commands, and gives it permission to access a command we've defined with the name
The commands that roles may be granted permissions for are defined in Lua, using:
Admin.Command.define(commandname: string, arguments: ArgumentDefinition, func: Function)
Users will call your command in-game with
/srvcmd <commandname> <arguments>. Definition of the arguments and command function are described in the below section.
arguments parameter to the command definition function allows you to provide names for each argument the user will provide to the command, and give them a type (boolean, integer, floating point or string) to validate user input against. When the user calls the command, if the arguments they provide do not match the order and type you specify, they will be shown an error message.
A command may have at most six arguments.
The ArgumentDefinition must be an array (i.e. a Lua table with 1-indexed integer keys), where each element is a two-element array (also a table) defining the name and type of the argument. An example of an ArgumentDefinition for a 'set next map' command with one parameter might be:
The function you provide as the final argument to the command definition is the name of a Lua function to call when a player executes the command.
This function will be passed two arguments - the name of the player executing the command, and the role they are logged in as - plus an additional argument for every defined command argument. So if you defined three command arguments, the Lua function should have five arguments.
So for instance, for a 'set next map' command, the Lua function definition might be:
The admin system is currently only accessible from a client running TAMods. Clientside TAMods exposes the following server commands that may be run at the console:
/srvlogin <role> <password>
This attempts to log into the server you are currently in with the given role and password name. The server will respond with a console message on success or failure.
This attempts to run a Lua statement on the server. This will fail if you are not currently logged into a role with permission to execute Lua.
/srvlua command you can run any valid TAMods-Server Lua statement, including to modify a server setting or change a game balance modification. Some Lua actions and settings will not take place until the next map switch. In addition, running these commands does not modify your config on-disk and so will not persist between server restarts.
You should be very careful in defining roles with permission to execute Lua commands, as this gives them access to run any Lua command. Running an invalid Lua command could crash the server - or worse, it could allow compromise of the computer the server is running on (since Lua can be used to interact with the filesystem!).
/srvcmd <command> <arguments>
This attempts to run a defined command with the given arguments on the server. It will fail if the command doesn't exist, your current role does not have access to the command, or the arguments are invalid.
Defining commands and explicitly allowing roles to execute them is safer than granting raw Lua access.
The following Lua functions exist which are primarily useful as Lua commands to be run via the admin interface. They can be run from a config file but are generally not useful in that context.
Sends a message to all connected modded clients which will appear in their console.
Admin.SendConsoleMessageToPlayer(playername: string, message: string)
Sends a message to a specific connected modded player which will appear in their console.
Admin.SendGameMessageToAllPlayers(message: string, time: float)
Sends a message to all connected modded clients which appears in the HUD, lasting for the specified time in seconds. This may not appear for players who have disabled certain HUD elements.
Force-starts the current map if in warmup.
Overrides the map rotation such that at the next map switch, the map will be the one specified. The map should be a valid map definition as per the Server Configuration page.
Forcibly ends the current map.
This example is run as a series of console commands from a client connected to the server, to set the next map and then swap to it.