Helios Rust Console Bot Documentation
Auto Kit Setup
Set up kit delivery with the guided Emote Bind form or the manual bind command.
- Last reviewed
- Maintained by
- Helios RCE
For the complete screenshot walkthrough, use Autokit Setup. Kit delivery starts with an existing kit and an active Quick Chat bind on the same game server.
Guided setup
Open Emote Binds → Create Emote Bind → Give a kit, or run /easy binds server:"<SERVER>" in Discord.
Choose a phrase, kit, player cooldown, chat type, and access rule. Save paused while checking, then resume and test. A basic kit bind does not need teleport coordinates.
Manual command alternative
Run /bind add and fill these options:
| Option | Example |
|---|---|
| message | Choose I need Scrap from the suggestions |
| server | Your connected game server; select it explicitly when several are connected |
| command | kit givetoplayer "builder" "{PlayerName}" |
| cooldown_minutes | 30 |
| chat_type | All |
| required_role or auth_group | Optional; choose one access rule |
Keep {PlayerName} in the command. A server_cooldown is separate: after one player uses that bind, everyone waits for its shared timer.
Use /bind list to review the saved binds and /bind edit to change one. For cooldown resets, use Cooldown Manager or a carefully filtered /bind cooldown.
Before announcing it
Check the actual items, the cooldown, and both eligible and ineligible players. Use a Discord role or a minimum Rust auth level. Linking is required for Discord role checks; it is not an extra prerequisite for every public kit bind.
If a claim fails, start with the Autokit troubleshooting table, including the trigger mode and Gun Game claim restriction.
