/bind add-cmd and edit-cmd

Overview 🚀

The /bind add-cmd and /bind edit-cmd commands let server owners and admins connect Helios command groups to in-game player binds.

Before adding a command to a bind, you need to create a command group first. Command groups hold the actual server commands that Helios will run when the bind is triggered.

Example use case:

A player does a quick chat in game like:

"I Need Wood"

Helios detects the bind, then runs the command group attached to that bind.

---

Important Setup Order ⚙️

You must create the command group and add commands first.

1. Create a command group with /cmd group add
2. Add commands to that group with /cmd add
3. Attach the command group to an in-game bind with /bind add-cmd
4. Use /bind edit-cmd later if you need to change the attached command group

---

Commands Covered 💬

Command	What It Does
/cmd group add	Creates a command group
/cmd add	Adds commands to the command group
/bind add-cmd	Connects a command group to a bind
/bind edit-cmd	Edits the command group connected to an existing bind

---

Step 1: Create a Command Group 📁

Use /cmd group add to create the group that will hold your commands.

/cmd group add

Example group names:

• wood
• starterkit
• spawn_rowboat
• spawn_recycler
• give_medical
• raid_alert_test

---

Step 2: Add Commands To The Group 🧾

Use /cmd add to add one or more commands to the command group.

/cmd add

These are the commands Helios will run when the bind is triggered.

For example, if your bind is for wood, your command group could include a command that gives wood to the player.

---

Placeholder Support 📍

Commands can use player placeholders.

This lets Helios run commands based on the player who triggered the bind.

Example position placeholders:

{PlayerPositionX},{PlayerPositionY},{PlayerPositionZ}

You can also offset each position value with + or -.

Example:

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

This means:

• X position is moved by 2
• Y position is moved up by 1
• Z position stays the same

---

Spawn Command Example 🚤

You can use player position placeholders to spawn an entity near the player.

Example:

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

This spawns a rowboat close to the player who triggered the bind.

You can replace rowboat with any valid entity name.

Example format:

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

---

Position Offset Examples 🧭

You can use + or - on each position value.

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

{PlayerPositionX}-3,{PlayerPositionY},{PlayerPositionZ}+4

{PlayerPositionX},{PlayerPositionY}+5,{PlayerPositionZ}

This is useful for commands that spawn items, entities, effects, or objects near the player instead of directly on top of them.

---

Step 3: Add The Command Group To A Bind 🎮

After your command group is created and has commands inside it, use /bind add-cmd.

/bind add-cmd

This connects the command group to an in-game bind phrase.

Example:

A bind could listen for:

i need wood

Then Helios runs the command group attached to that bind.

Example Command Group:

---

Step 4: Edit A Bind Command 🔧

Use /bind edit-cmd when you need to change which command group is attached to an existing bind.

/bind edit-cmd

This is useful if you already made the bind but want it to run a different command group.

---

Example Setup ✅

A simple setup could look like this:

/cmd group add
/cmd add
/bind add-cmd

Example in-game trigger:

i need wood

When the player says the bind phrase in game, Helios runs the command group connected to that bind.

---

Setup Flow 🛠️

1. Run /cmd group add to create a command group
2. Run /cmd add to add commands to that group
3. Use placeholders if the command needs the player’s position
4. Run /bind add-cmd to attach the command group to a bind
5. Test the bind in game with one controlled player
6. Use /bind edit-cmd if you need to change the command group later

---

Requirements 📌

Before using these commands, make sure:

• Helios is connected to at least one server in this Discord
• You have permission to run admin commands
• You selected the correct server when using commands with a server: option
• A command group already exists before using /bind add-cmd
• The command group has commands added with /cmd add

---

Notes 📝

• Most admin commands require Manage Server permission
• Panel-based commands are user-scoped, so each admin should open their own panel
• /bind add-cmd does not create the command group by itself
• Always create the command group first with /cmd group add
• Always add commands to the group with /cmd add
• You can replace rowboat with any valid entity name in spawn commands
• Use position offsets carefully so commands do not spawn things inside players, bases, or terrain
• Test each bind before making it available to the full server