Command Group Binds

Use this when one emote should run a saved sequence of commands. The order is create a group → add its commands → attach a bind. For a single kit or item, Emote Binds offers a shorter setup.

You need Manage Server. Creating and editing Command Groups requires Premium; the bind command itself uses the free-tier bind limits when applicable. Groups are shared across the Discord community, while the bind's server selection controls where it applies.

1. Create a named group

Open Dashboard → Automations → Command Groups → Create Command Group. Give the group a useful name, then choose Create when ready.

An unsaved example. Creating a group saves its name; it does not run any commands.

2. Add the commands in order

Expand your group and choose Add Command. Select the group, enter a label, set Execution position to 1, and enter the Rust Console command. Additional commands use positions 2, 3, and so on.

The existing Test group's command, opened and cancelled without saving. Select your own group when adding a command.

For a kit reward, use a kit that already exists on the target server:

kit givetoplayer pvp "{PlayerName}"

{PlayerName} becomes the player who used the bind. A timed schedule has no triggering player. Save each command, then expand the group again to check its text, count, and order. See Command Groups for the full editor and delivery details.

Run Commands executes immediately on the dashboard's selected server. It is not a preview of a player-triggered claim.

3. Attach the group in Discord

Run /bind add-cmd. Choose the quick-chat message, then select the saved command_group from suggestions.

The actual Discord options. This draft was discarded; no bind was created.

Set server explicitly for your first setup. Omitting it applies this command-group bind to all connected servers in the community. Choose the actual suggestion rather than typing an unrelated name.

Option	First-setup example
message	An unused phrase, such as I need Scrap
command_group	The group you saved
server	Your intended game server
cooldown_minutes	30 — one player's wait in minutes
server_cooldown	Optional shared wait between players
required_role or auth_group	Choose one access rule if needed

/bind add-cmd message:"I need Scrap" command_group:"Starter Rewards" server:"<SERVER>" cooldown_minutes:30

Read the server, group, and phrase before submitting. Submission saves a live bind. The screenshots use the existing Test group; replace it with your own saved group.

4. Check it with one player

Use the chosen quick-chat phrase in game and check each command's result. A partial delivery can leave earlier commands applied; check what arrived before another attempt. Verify the player cooldown and any role or auth restriction too.

To change the attached group later, run /bind edit-cmd, select the server and bind, and choose the replacement group. Editing a group's commands also changes what its existing binds, Shop products, and other users run next.

Position-based commands

For actions that support a live triggering player's position:

Placeholder	Meaning
{PlayerPositionX}, {PlayerPositionY}, {PlayerPositionZ}	The player's live coordinates
{PlayerPositionX}+2	Two units added to the X coordinate
{PlayerPositionY}-1.5	One and a half units subtracted from Y

spawn rowboat {PlayerPositionX}+2,{PlayerPositionY}+1,{PlayerPositionZ}

The player must be online and Helios must be able to read their position. Choose a safe location and cooldown for any spawn or teleport action. See Bind access rules and Command Groups for the shared controls.