Setting Up Admin Roles and Permissions in Rust

Introduction

Properly configured admin roles are crucial for server management. This guide will help you set up a hierarchical admin system with appropriate permissions for different staff roles.

Prerequisites

• Server FTP access or direct file access
• RCON access
• Admin on the server
• Access to server.cfg file

Method: Setting Up Admin Roles

1. Understanding Permission Levels

Rust uses SteamID64 and permission levels for admin rights:

1. Permission Levels:

   • Level 0: Regular player
   • Level 1: Moderator
   • Level 2: Admin
   • Level 3: Super Admin
   • Level 4: Server Owner

2. Finding SteamID64:

   # In-game command
   /steamid
   
   # Or use website
   steamid.io
   

2. Basic Admin Commands

1. Add Admin:

   ownerid <steamID64> <level>
   

   Examples:

   # Add Moderator (Level 1)
   ownerid 76561198123456789 1
   
   # Add Admin (Level 2)
   ownerid 76561198987654321 2
   

2. Remove Admin:

   removeid <steamID64>
   

3. Permission Level Configuration

1. Level 1 (Moderator) Permissions:

   # In server.cfg
   oxide.grant group moderator chat.playerlist
   oxide.grant group moderator inventory.adminexamine
   oxide.grant group moderator playerlist.invis
   oxide.grant group moderator spectate
   

2. Level 2 (Admin) Permissions:

   # Additional to Level 1
   oxide.grant group admin inventory.giveto
   oxide.grant group admin inventory.givearm
   oxide.grant group admin teleport
   oxide.grant group admin kick
   oxide.grant group admin ban
   

3. Level 3 (Super Admin) Permissions:

   # Additional to Level 2
   oxide.grant group superadmin server.writecfg
   oxide.grant group superadmin rcon.login
   oxide.grant group superadmin server.fps
   

4. Command Access Configuration

1. Moderator Commands:

   # Available commands for Level 1:
   /players - View online players
   /spectate - Spectate players
   /examine - Check player inventory
   /mute - Mute players
   /unmute - Unmute players
   

2. Admin Commands:

   # Additional commands for Level 2:
   /kick - Kick players
   /ban - Ban players
   /unban - Unban players
   /tp - Teleport
   /give - Give items
   

3. Super Admin Commands:

   # Additional commands for Level 3:
   /wipe - Initiate wipes
   /restart - Restart server
   /config - Edit configuration
   

Best Practices

1. Role Assignment

• Start staff with lower permissions
• Implement promotion periods
• Document all permission changes
• Regular staff activity reviews

2. Security Measures

• Use strong RCON password
• Change admin passwords regularly
• Monitor admin actions
• Regular permission audits

3. Staff Guidelines

• Create clear rules for staff
• Document command usage
• Set up staff communication channels
• Regular staff meetings

4. Common Pitfalls

• Avoid giving full permissions immediately
• Don't share admin passwords
• Keep staff list updated
• Regular backup of admin configs

Command Reference

1. Essential Admin Commands

# Player Management
ban <steamID/name> <reason>
kick <steamID/name> <reason>
mute <steamID/name> <duration>

# Server Management
server.save
server.writecfg
server.restart

# Information Commands
status
players
fps

2. Useful RCON Commands

# Server Information
status
fps
mem

# Player Management
say
banid
kickall

Troubleshooting

1. Permission Issues

• Verify SteamID64 format
• Check server.cfg syntax
• Confirm permission level
• Restart server after changes

2. Command Access

• Verify permission level
• Check command syntax
• Review server logs
• Test on test server first

3. Common Errors

• Invalid SteamID format
• Incorrect permission level
• Missing configuration entries
• Server restart required

Additional Tips

1. Staff Management

• Create staff application process
• Set trial periods
• Regular performance reviews
• Clear promotion criteria

2. Documentation

• Keep staff manual updated
• Log all admin actions
• Document configuration changes
• Maintain staff guidelines

3. Backup Procedures

• Regular config backups
• Staff list backups
• Permission backups
• Documentation backups

Remember to always test new permissions on a separate test server before implementing them on your main server. Regular audits of admin permissions help maintain server security and prevent potential issues.