Trigger templates
heliana seeds every new organization with a set of ready-made triggers covering the common Squad admin tasks. They show up in the Triggers table switched Off — nothing runs until you turn one on. Turning one on and editing it is the fastest way to get a working trigger without building from scratch.
There’s no separate template gallery: New trigger opens an empty builder. These seeded triggers are just regular triggers that came pre-filled, so you enable and edit them like any other.
See Create your first trigger for a full walkthrough.
Enable a seeded trigger
Section titled “Enable a seeded trigger”- Navigate to your server, then open the Triggers tab.
- Find the trigger you want in the table. Seeded triggers start Off.
- Click Edit to open it. Review the name, conditions, and actions, and change anything you want — these are starting points, not fixed presets.
- Switch Enabled to On and click Save.
Disabled triggers don’t count against your active-trigger limit, so you can leave the ones you don’t use switched off.
What ships in a new organization
Section titled “What ships in a new organization”Manual triggers — player
Section titled “Manual triggers — player”These add a button to a player’s profile. Each one can be permission-gated per trigger — see Player actions as triggers.
| Trigger | What it does |
|---|---|
| Ban player | Bans the player; prompts for a required reason at run time, and adds a note. |
| Warn player | Sends an in-game warn via RCON and adds a note. |
| Kick player | Kicks the player via RCON, adds a note, and writes a notification. |
| Force team change | Moves the player to the other team via RCON. |
| Remove from squad | Removes the player from their current squad via RCON. |
Manual triggers — server
Section titled “Manual triggers — server”These appear in a server’s status panel.
| Trigger | What it does |
|---|---|
| Force seed bots | Sets the seed-bot target count via RCON and writes a notification. |
| Run RCON command | A one-off RCON button — you type the command at run time. |
| Broadcast | Sends a server-wide broadcast via RCON. |
| Change map | Changes the map via RCON; you provide the layer name. |
| End match | Ends the current match via RCON. |
Event triggers
Section titled “Event triggers”| Trigger | What it does |
|---|---|
| Teamkill autoban | Warns a teamkiller on each offence; bans for one hour after 7 teamkills within an hour. |
| Flag on first join | On a player’s first join, adds them to the verified group and broadcasts a welcome message. Both actions only run if the player isn’t already in that group. Create a group with the slug verified first, or change the slug in the action to a group you already have. |
| Watch notify | When a player who’s in the built-in Watch group joins, writes a notification so your team sees it. |
| Playtime command (!time) | Replies in-game with total playtime when a player types !time in chat. |
| Discord log | Posts events to a Discord webhook — pick the event and edit the message body. |
Scheduled triggers
Section titled “Scheduled triggers”| Trigger | What it does |
|---|---|
| SL kit enforcement | Warns squad leaders who haven’t taken the SL kit; runs every 5 minutes over each online player. |
Adding a player to a group instead of “flagging”
Section titled “Adding a player to a group instead of “flagging””There’s no “flag” action. To tag a player automatically — like the Flag on first join trigger does — an action adds them to a roster group by its slug. The group has to exist first: create it on the Roster / Player Lists side, then reference its slug in the action. The only group seeded automatically is Watch.