Skip to content

Next steps

At this point you have a connected server, a live event feed, and at least one automated trigger running. Here is what to tackle next.

If you run your server with other admins or moderators, add them to your organization so they can use the dashboard without sharing your credentials.

A player’s profile has a Lists tab where you add them to a roster group — the built-in way to tag regulars, mark known griefers, or keep an eye on someone. A seeded Watch group is ready to use out of the box, or create your own.

Bans issued through heliana are stored persistently and tied to a player’s identities (Steam, EOS, BattlEye, or Mojang). Beyond banning players yourself, you can pull in bans from outside sources and see how a player is viewed by other communities.

Beyond the teamkill autoban you set up in the previous step, triggers can cover most repetitive moderation tasks:

  • Create an event trigger — react to any log event: kills, teamkills, chat messages, round endings, player joins.
  • Create a scheduled trigger — run checks or RCON commands on a fixed interval or cron schedule.
  • Build conditions — filter events using AND/OR conditions, regex matching, counters, and player attribute checks.
  • Rate-limit a trigger — prevent a trigger from firing more than once per player in a given window.
  • Use trigger templates — the full list of ready-made triggers every organization starts with, and what each one does.