Skip to main content

AI Companion — Usage

This page explains how to work with the AI Companion day to day, and gives you an idea of everything it can help with. If it isn't switched on yet, see AI Companion setup first. For the underlying ideas (proposals, sessions, page awareness), see the AI Companion concept.

Opening the Companion​

Click the AI Companion button (the sparkles icon) in the top-right of the admin header. A panel slides in from the right.

On a ticket page you'll also find two shortcuts that open the Companion already focused on that ticket:

  • an Ask the Companion prompt on the ticket's Investigation tab, and
  • an "Unsure how to answer? Let AI do the talking" link next to the reply box.

Sessions​

The Companion organises your work into sessions, like a chat history:

  • The button opens a list with Open and Archived tabs and a + New session button.
  • Each session is private to you, named automatically from your first message, and renamable.
  • Continue later closes the panel but keeps the session in your open list.
  • Archive marks a session as done and moves it to the Archived tab.
  • Sessions are never deleted, so you (and admins) can always look back at what was asked and approved.

Keep one session per task. A session's focus is fixed when you create it, so when you move on to a different player or ticket, start a fresh session rather than reusing an old one.

Talking to it​

Type what you need in plain language and press Enter (use Shift+Enter for a new line). You can write in German or English — for player-facing replies it will match the player's language.

A turn runs in the background and takes a few seconds to up to a minute, since the Companion may look up several things before answering. While it's working you'll see "The assistant is working…", and you can't send a second message in that session until it's done. As it works, it shows a short note of which areas it consulted.

Approving what it proposes​

The Companion never changes anything on its own. When it wants to take an action, it adds a proposal card to the chat with a plain summary and two buttons:

  • Approve — carries the action out immediately, using the same logic as the normal admin pages.
  • Reject — discards it.

A single answer can include several proposals (for example a reply and an internal note, or two alternative replies). Decide each one separately. Cards are colour-coded by status — Pending, Approved, Rejected, or Failed — and link straight to the player, faction, or ticket involved so you can double-check before approving.

If you don't like a proposal, just tell the Companion what to change and it will draft a new one — there is no inline editing.

What the Companion can help with​

You don't need to learn any commands — just describe your goal. Below are the areas it understands today, to give you a sense of what's possible. Think of these as inspiration, not a fixed menu.

Support tickets

  • Open a new ticket with a player to start a conversation, with the opening message drafted for you.
  • Rewrite your rough notes into a calm, professional reply to a player.
  • Read the whole ticket conversation and summarise what the case is about.
  • Draft an internal, staff-only note on a ticket.
  • Pull in another ticket you remember that's relevant to the current case.

Investigations

  • Search the game logs for kills, deaths, connections, building, money transfers and more, within a time range or around a location.
  • Correlate what players and factions were doing, and summarise the findings.
  • Check your server rules and judge a case against the actual wording.
  • Pin a relevant log event to a ticket as evidence.

Players

  • Look up a player's profile: identities, faction, balance, ban and whitelist status, last known position, linked Discord.
  • Check and adjust a player's balance (give, remove, or set an amount, with a reason). A player's wallet balance is org-wide — one balance shared across every server in the organization.
  • Ban a player, add or remove them from the whitelist, or clear a player's claim block.
  • Leave an internal note on a player.
  • Send a player a Discord DM, or grant/remove a Discord role.

Factions

  • Look up a faction's details, members, and balance.
  • Review a faction's treasury history and adjust its balance.
  • Leave an internal note on a faction.

Shop and orders

  • Find a player's orders and inspect what was bought and delivered.
  • Refund an order, or re-deliver items a player paid for but didn't receive.
  • Gift a player items for free — either a ready-made shop kit or specific items.

Bases and territory

  • Locate a player's or faction's base for a raid, by combining base alarms, recent building activity, and detected bases — so you don't have to hunt down coordinates yourself.

Server rules

  • Read the current rules and quote the exact wording relevant to a case.
  • Update the rules for you — reword a rule, add or remove one, or rewrite the whole ruleset. The change is drafted as a proposal showing the exact diff, and an approved change lands in the rules history like a manual edit.
  • Publish the updated rules to your Discord rules channel afterwards (also as a proposal you approve).

Server settings

  • Look up how your server is configured — the same options you edit on the Settings page — and explain where a given behaviour is controlled instead of you hunting for it.
  • Change a setting for you — for example, remove a flag from the pool players can pick when founding a faction (the "available flags"), or adjust another General, Access, Economy or Discord option. The change is drafted as a proposal showing the old and new value, which you approve. Credential and organization-level settings are off-limits to the Companion.

Custom pages

  • Read one of your custom info pages — just paste its link (e.g. .../pages/trader) or name the page, and the Companion reads its content.
  • Edit an existing page for you — reword or restructure its content, or change its navigation title, headline, subheadline or icon. The change is drafted as a proposal showing the exact diff, which you approve.
  • Creating or deleting pages, and changing who can see a page (its visibility), stay in the admin Pages screen — the Companion doesn't do those.

Discord

  • Read a Discord message or a channel's recent messages from your linked Discord server — just paste a Discord link, or reference a channel, and the Companion reads it back to you. This is read-only; the Companion never posts, edits or deletes anything in Discord here.
  • It can only read channels in your own linked Discord server, never another community's.

Zones

  • List the map zones on your server and what each one enforces (no-build, no-kills, linked-only).
  • Check which zones a coordinate falls inside — e.g. whether a kill or a build event happened in a managed zone — so you can judge a case against the right zone policy.

Actions (automations)

  • Explain how actions work and help you design one from a plain-language goal ("reward players for killing zombies", "alert Discord on a donation").
  • Write the complete Lua script for you, using the correct event data, functions and config fields — and check that it compiles before proposing it.
  • Create, edit or delete a custom action, all as proposals you approve; the proposed script is shown in full on the card so you can read it first.
  • Search the action marketplace and install a ready-made action, or uninstall one you no longer want.
  • Enable or disable an action (this one applies immediately, since it's easily reversed).
  • Read an existing action's script, configuration and recent run logs to help you work out why it isn't behaving as expected.

Scheduler (time-based automations)

  • Explain the difference between actions (which fire on a game event) and scheduled tasks (which run on a clock), and help you set up the right one from a plain-language goal ("post the active bounties to Discord every day at 20:00", "restart the server every night", "wipe vehicles weekly").
  • Build the schedule for you — one-off at a set time, or recurring (hourly, daily, weekly, monthly) — without you needing to know any cron syntax.
  • For a recurring job built from live data (like a daily bounty post), write the underlying action script for it too.
  • Create, edit or delete a scheduled task, all as proposals you approve.
  • Pause or resume a scheduled task (this one applies immediately, since it's easily reversed).
  • Read an existing scheduled task's configuration and recent run logs to help you work out why it didn't run as expected.

Everything that changes data in the lists above is always a proposal you approve, never an automatic action — except enabling/disabling an action or pausing/resuming a scheduled task, which are applied straight away.

Good habits​

  • Be specific. "Refund order 4821 because the trader was offline" works better than "fix this order".
  • One task per session. Start fresh sessions for new cases.
  • Let it do the lookups. You usually don't need to paste IDs — describe the player or ticket and it will find them.
  • Always read a proposal before approving. The Companion is a strong drafter, but you make the call.

Limits​

  • The Companion takes a limited number of steps per turn. For a very large investigation, break it into smaller asks across messages.
  • Only one turn runs at a time per session.
  • Responses arrive once the turn finishes — there is no word-by-word streaming.

Tell us what you need next​

The Companion is focused on ticket support today and we are steadily expanding what it can do across the platform. We'd love to hear your use cases and feature requests — tell us what you'd want it to handle next on our Discord.