Helios Rust Console Bot Documentation

/bind auth_group and required_role

Restrict binds by in-game auth level, Discord role, or both.

Last updated
Maintained by
Helios RCE

Use auth_group and required_role when a bind should not be available to everyone.

These options are configured while creating or editing a bind.

What Each Option Does

  • auth_group: limits the bind by in-game auth level
  • required_role: limits the bind by Discord role

Use auth_group when the bind should only work for in-game staff or authorized players.

Use required_role when the bind should only work for linked players with a specific Discord role.

You can also use both together when a bind should require both staff auth and a Discord role.

Where You Configure It

  • /bind add
  • /bind edit
  • Easy Binds for simpler preset-driven setup

bind add example

Example Uses

  • Staff-only moderation binds
  • VIP-only utility binds
  • Event binds reserved for a Discord event role
  • Owner/admin binds that should not be available to normal linked players

Example

/bind add trigger:"!kit" command:"kit givetoplayer starter {PlayerName}" required_role:@VIP
/bind add trigger:"!cleanup" command:"ent kill" auth_group:owner

Validation Checklist

  • Test the bind with an allowed account
  • Test the bind with a blocked account
  • Confirm the player is linked if the bind depends on a Discord role

Related Pages