3 min readUpdated Oct 8, 2026

How to Set Up Player Roles on Your Path of Titans Server

Player roles let you give staff specific command permissions and custom chat colors on your Path of Titans server. Start with the commands each person needs, then add permissions as their responsibilities grow.

Create a Player Role

  1. 1
    Log in to Bropanel and Stop your server.
  2. 2
    In the sidebar, go to Files.
  3. 3
    Navigate to server/PathOfTitans/Saved/Config/LinuxServer/ and open Commands.ini. Create a file with that name if it is missing.
  4. 4
    Add the example below, keeping any existing roles and player assignments.
  5. 5
    Replace 123-456-789 with the player's Alderon Games ID (AGID). Players can find their ID at alderongames.com.
  6. 6
    Save the file and Start your server.
[Role:Announcer]
+Permission=announce
ChatColor=(R=80,G=180,B=255,A=255)

[PlayerRoles]
123-456-789=Announcer

This example grants the announce permission. It is a useful starting point for someone who posts event notices. If [PlayerRoles] already exists, add the assignment beneath that section instead of creating a second copy.

Each role starts with [Role:RoleName]. Add one +Permission=PermissionName line per permission. Use our chat commands guide when choosing permissions.

For ChatColor, use parentheses as shown. RGB values range from 0 to 255; keep A=255. Without a color, the default is white.

Assign or Remove Roles In-Game

Set yourself up as a server admin first. With the server running, open the in-game text chat and enter:

/promote 123-456-789 Announcer

Replace the example AGID and role name. You can also use the player's username. To remove their assigned role, use:

/demote 123-456-789

To change an assignment through Bropanel, stop the server, edit the player's line under [PlayerRoles], save, and start it again. Remove the line to remove that assignment.

Note

Permission names usually match lowercase commands without /, but /bring needs +Permission=teleport, and /demote needs +Permission=promote. Attribute commands use names with spaces, such as +Permission=set attribute for /setattr. Check the command permission table when choosing permissions. Grant role-management permissions only to trusted staff. See the official chat commands and server admin documentation for these exceptions.

Optional Role Settings

Place these beneath the relevant [Role:RoleName] heading, before the next section.

SettingEffect
OverrideAdminChatColor=TrueUses the role color instead of the whitelisted admin color.
AllowSpectatorAccess=TrueAllows Spectator mode and the admin panel.
ReservedSlot=TrueGives the role reserved-slot access.
CreatorModeAccess=TrueAllows Creator mode.
Hierarchy=10Sets the role's rank; the default is 0.

The four True/False settings default to False. Lower-ranked roles cannot use hierarchy-aware commands, including ban, kick, promote, and demote, against higher-ranked roles.

Check Your Configuration

After restarting, have the assigned player join and try the intended command. For the example role, use /announce Event begins in five minutes.

If the role does not work, check the AGID, the role name in both sections, and the permission spelling. Confirm you saved Commands.ini in the LinuxServer folder before starting the server. A player listed in ServerAdmins has administrator access, so use a separate account when checking a restricted role.

Role syntax and settings are based on Alderon Games' Player Roles documentation.