Helios Rust Console Bot Documentation

/set link-role

Choose linked-player and platform roles, then safely sync existing members.

Last reviewed
Maintained by
Helios RCE

Choose the Discord roles Helios gives players after they link their game account. These settings apply to the whole Discord community, not just the game server open in the dashboard.

Before you start

You need Manage Server in Discord. The Discord setup command is free; the dashboard controls require Premium on the open game server.

Create ordinary linked-player roles first. Helios needs Manage Roles, and its highest role must sit above the roles it assigns. Use dedicated link roles, not staff roles or roles with unrelated purposes.

Setting roles does not link anyone, grant in-game VIP, or activate a Premium subscription.

Use the dashboard

  1. Open your game server in the dashboard.
  2. Choose Overview → Shared setup and admin tools → Link Roles → Configure.
  3. Choose a Base link role.
  4. Optionally choose separate PlayStation and Xbox roles, or None.
  5. Choose Save Setting.

Link Roles form with the existing base role and no platform roles selected

The unchanged form on Helios Bot Testing. It was closed without saving.

A linked player receives the base role plus the role for the console recorded on their link. With no console recorded, only the base role is expected.

Use Discord

/set link-role role:@Linked

With platform roles:

/set link-role role:@Linked playstation:@PlayStation xbox:@Xbox

Include every platform role you want to keep when you rerun this command. Omitted platform options clear their saved selections; they do not preserve the previous choices.

Update members who are already linked

Saving the role choices does not itself update every existing member.

  1. Review your saved choices.
  2. In Overview → Shared Helios systems → Role Syncing, choose Sync Link Roles.
  3. Read the result. If updates were queued, let the background job finish; progress is saved and resumes after a restart. A completed summary can show members updated, roles added, and roles removed.
  4. Check a few actual Discord members afterward.

Sync Link Roles can run in the background. It adds the expected configured roles, removes the wrong configured platform role, and removes currently configured link roles from members who are no longer linked. A queued response means the work was accepted, not that every role has already changed. Large communities and Discord rate limits can add delay; check members before starting another sync.

It manages the roles currently selected in your link settings. Do not assume it cleans up every old role you previously used. Review obsolete roles separately.

A completed summary does not guarantee every member was updated: deleted roles, missing members, or Discord permission failures can prevent individual updates.

Open Overview → Shared setup and admin tools → Link Emoji. Enter one standard emoji, or leave it blank to reset to ⚡, then choose Save Setting. This is shared across your Discord community.

Link Emoji dialog showing the default lightning emoji and the background nickname-update explanation

In Discord, run /settings server, choose your game server, then click Link Emoji. The form has the same shared effect: enter one standard emoji and Submit, or Cancel to leave it unchanged. Opening it through one game server does not limit the nickname change to that server.

Actual Discord Link Emoji modal with the default lightning emoji and Cancel and Submit buttons

Existing value inspected without submitting. The example keeps the default ⚡.

Existing value inspected without saving. This setting changes a nickname prefix; it does not choose a role or link a player.

Nickname Changes must be enabled under Overview → Shared Helios systems for the prefix to apply. Existing linked nicknames update gradually in the background; large communities can take hours. Check Helios's nickname permissions and role hierarchy, and inspect a few actual members before assuming the work is complete. Repeated saves do not make the queue instant.

If roles are missing

Use an ordinary player role. Helios’s own bot role and other managed integration roles cannot be assigned to players. Roles must sit below Helios and cannot include Administrator, Manage Server, Manage Roles, or Manage Webhooks. A higher position alone does not make an unsafe role assignable.

  • Check the player's link and recorded console.
  • Check that the chosen roles still exist.
  • Move Helios above the assigned roles and give it Manage Roles.
  • Save the role choices, then sync existing members.
  • Check the actual member before rerunning a failed operation.

See Player Link, Staff Permissions, and Custom Auth Roles for the separate player and staff systems.