Glossary
Terms that show up across guides and reference pages, and what heliana does with each. Each term
below is a heading, so a link to it (/docs/reference/glossary/#term) jumps straight to that term
instead of the top of the page.
heliana uses it to read the Squad server’s log file remotely and, on servers with Config managed by heliana turned on, write Admins.cfg.
See Get SFTP access to the Squad log for what heliana requires of the account.
heliana uses RCON both to read live server state (player roster, layer, player count) and chat, and to carry out actions your automations fire. Game events come from the log over SFTP; the RCON roster is what attributes them to players. See Configure RCON.
EOS ID
Section titled “EOS ID”For a Squad player it is the identifier that defines the player in heliana: a player is not created without it. See Identity platforms.
Steam ID
Section titled “Steam ID”heliana records it alongside the EOS ID for the same player, and a ban can target either. See Identity platforms.
webhook
Section titled “webhook”An outgoing HTTP request an automation sends with ctx.fetch to a URL you choose; the answer (status, headers, body) comes back to the module. See
Automation SDK reference.
Used by scheduled automations. See Cron syntax.
The time zone every schedule and timestamp in heliana is written and evaluated in. A schedule read as a local time will fire at the wrong hour. See Cron syntax.
An operator available when building an automation condition on a text field (chat message, player name, …). See Build conditions.
Access list
Section titled “Access list”A named set of players that heliana delivers to your servers as game config, unlike a tag, which only labels. See Access lists & list leaders.
List leader
Section titled “List leader”A member to whom one Access list is delegated; they manage its entries within a slot limit and see nothing else. See Access lists & list leaders.
Game ID
Section titled “Game ID”The Steam64 or EOS ID of a user. A Steam64 ID is connected with Connect Steam and counts as verified in every organization; an EOS ID is entered in Profile and counts in your organization only after an admin verifies it. See Verify a player’s Game ID.
Patron
Section titled “Patron”A member of the Patreon campaign connected to your organization. See Patreon.
A level of the Patreon campaign, routed to Access lists on each list. See Patreon.
Discord role
Section titled “Discord role”A role of the connected Discord server that an Access list gives while a person holds an entry in it. See Discord roles.
Seeding window
Section titled “Seeding window”A server’s setting: for each day of the week a start and an end time in UTC, or none. A window that runs past midnight belongs to the day it starts on. Seeding is off until you set one. See Reward seeders.
Seeding thresholds
Section titled “Seeding thresholds”Two online counts: seeding runs above the lower one, and the server is live at the higher. See Reward seeders.
Seed reward
Section titled “Seed reward”An entry in an Access list that seeding earns: its term grows by the seeding credit counted over finished windows, up to a ceiling, rather than being set by a sync. See Reward seeders.
A decision against a player: a reason, a duration (permanent or until a date), a scope (all servers or named ones) and the identities it was decided against, its coverage. See How bans are structured.
Ban Source
Section titled “Ban Source”A connection to an outside ban list — BattleMetrics or a Remote Ban File — whose entries heliana syncs in as imported bans and enforces on your servers; your organization does not own them. See Sync an external ban source.
Exception
Section titled “Exception”A local override that stops imported bans from being enforced against one player — on all servers or one named server — without touching any ban record. It covers every imported ban whose coverage overlaps that player’s identities, and never a ban your organization issued. See Manage exceptions.
Automation
Section titled “Automation”A rule that starts from a game event, a schedule or a button, checks conditions, and runs actions. See What is an automation.