Helios Rust Console Bot Documentation

Easy Binds

Owner setup guide for creating, editing, and managing /easy binds across kit, spawn, and teleport actions.

Page Summary

  • This page covers Easy Binds setup for Rust Console quick-chat actions.
  • It is for owners and admins creating guided kit, spawn, and teleport bind workflows.
  • Use it to configure bind actions with cooldown, role, and claim-message controls.

Related Product Pages

Overview

Easy Binds give admins a guided panel to create quick-chat binds without manually writing /bind add command strings. Each bind maps a quick-chat trigger to one of three action types: Kit, Spawn Preset, or Teleport.

Who This Is For

  • Owners defining bind policy per server
  • Admins who manage utility binds for players
  • Staff updating or removing existing binds after wipe changes

Requirements

  • Connected server in Helios
  • Manage Server permission in Discord
  • At least one mapped quick-chat trigger available in your bind catalog
  • For Kit binds: your server returns kit names from kit list
  • For Teleport binds: bind creator has linked their account with /link and can be found in-game

Setup

  1. Run /easy binds server:"<SERVER>" and select the server from autocomplete.
  2. In the Easy Binds panel, click Create.
  3. Select the Category for the quick-chat trigger.
  4. Select the exact Trigger players will use in chat.
  5. In Choose Action, pick Kit, Spawn, or Teleport.
  6. Configure the action path:
  7. If you selected Kit, choose the kit from the dropdown. Use Reload Kits if your latest kits are missing.
  8. If you selected Spawn, choose one preset group (Mini, Scrap Heli, Recycler, etc.).
  9. If you selected Teleport, stand where players should land in-game, click Set Location, then toggle Force on Ground as needed.
  10. Configure shared options for any action:
  11. Set Cooldown in minutes (0 means no cooldown).
  12. Set Cooldown Message (or keep the default).
  13. Set Claim Message (enter off to disable).
  14. Optionally set a Required Role.
  15. Click Create Bind.
  16. Confirm the panel status shows Created "<Trigger>".

Editing or Removing Existing Binds

  1. Run /easy binds server:"<SERVER>".
  2. Click List to review configured binds.
  3. Click Edit to open a selectable bind list.
  4. Choose a bind, update settings, then click Save Changes.
  5. Click Remove to delete a bind you no longer need.
  6. Re-open List to verify final state.

Commands or Controls

/easy binds server:"<SERVER>"
/link

Example Use Case

An owner creates three common utility binds for a wipe start: one Kit trigger for starter loadout, one Spawn trigger for Mini deployment, and one Teleport trigger to return staff to a monitored safe point.

Common Issues

Problem

Create button works, but bind fails to save.

Likely Cause

A bind with the same trigger already exists on that server.

Fix

Use List or Edit to find the existing trigger and update or remove it first.

Prevention

Keep one canonical bind per trigger and document trigger ownership for staff.

Problem

No kits appear in Kit Setup.

Likely Cause

kit list returned no kit names or response formatting is invalid.

Fix

Create/verify kits server-side, then click Reload Kits and re-open Kit Setup.

Prevention

Test kit list after plugin updates and before wipe-day staff setup.

Problem

Teleport location fails to capture.

Likely Cause

Admin is not linked with /link or player position lookup failed.

Fix

Link account, stand still in-game, and click Set Location again.

Prevention

Link admin accounts before running bind setup sessions.

Tips / Best Practices

  • Free tier allows up to 3 binds per server; premium removes that bottleneck.
  • Easy Binds sessions expire after inactivity, so finish setup in one pass.
  • Use role-gated binds for high-impact actions (heli, teleport, vehicles).
  • Keep cooldowns non-zero for expensive actions to reduce abuse.
  • Re-check all bind actions after wipe or map/server key changes.