⚡ Automations

IF a server event happens, THEN the bot acts on its own - kick, ban, timeout, role, message, money... Set up entirely by staff in the dashboard.

🔑 The key difference with Custom commands: a custom command is triggered by a MEMBER typing !name. An automation is triggered by a server EVENT - nobody "invokes" it. That's exactly what makes heavy actions (kick/ban/timeout) safe here and nowhere else: the risk of a member pulling the trigger against someone else simply doesn't exist.

Example

On an 18+ server: trigger = role added = "17 years old" → action = Kick. As soon as someone takes that role, they're removed automatically, no staff member needs to be watching.

Simple / Advanced mode

Same principle as custom commands: 🧩 Simple shows the name, the trigger and the actions - the core of what an automation is. 🛠️ Advanced also reveals the conditions (require/forbid a role) and a dedicated staff-notification channel. Switching mode never erases a hidden field's value.

The 10 triggers

➕ / ➖ Role added / removed - optionally limited to one specific role.
⚠️ X warnings reached - independent from the automatic warning ladder (Moderation page): its own trigger, its own action catalog.
🕳️ Loan defaulted (/pret).
🛡️ Not verified after a delay - checked roughly every hour, not in real time.
🐣 Very new Discord account on join - account younger than X days.
💤 Prolonged inactivity - no message sent for X days.
🚪 Left the server.
🎫 Too many tickets opened in a sliding time window.
🏅 Seniority reached - X days present on THIS server (not the Discord account's age) - reward loyalty (role, money, bonus XP) without manually reviewing who crossed a milestone.

⏱️ The three time-based triggers (not verified, inactivity, seniority) are checked periodically (about every hour), not instantly - a full member list check is too costly to run every minute. Each one only fires once per member for a given automation, even if the condition stays true for weeks - it won't re-kick or re-message someone every hour.

Conditions (advanced)

Refine who the automation applies to: a required role and/or a forbidden role. A forbidden condition always wins on conflict.

Actions (chained)

The same catalog as custom commands (role, message, DM, money, XP, item), plus actions reserved for automations only:

👢 Kick, 🔨 Ban, 🔇 Timeout, ⚠️ Official warning (a real entry in the moderation history, visible on the member record).
✏️ Set nickname, 🔀 Move to a voice channel, 🔌 Disconnect from voice.
🎫 Open a ticket - instead of a direct kick/ban, opens a "system" ticket (no panel/type needed) so staff can decide on a borderline case (e.g. a recent account that isn't necessarily malicious) rather than an automatic, irreversible sanction.

🛡️ A built-in safeguard blocks kick/ban/timeout/official-warning against anyone with real moderation permissions (Kick Members, Ban Members, Manage Server, Administrator...) - a misconfigured automation can never target actual staff.

⏳ Deferred actions

Each action can be set to run immediately (default) OR after a delay in minutes - e.g. a two-action automation: warn now + kick in 1440 min (24h). Right before a deferred action actually runs, the bot re-checks whether the situation still holds (did the member remove the role they got warned for? did they get verified? is the loan repaid? are the warnings still there?) - if it doesn't hold anymore, the action is cancelled instead of firing blindly. This gives members a real chance to fix things before the heavier action lands.

⏱️ Deferred actions are checked on the same roughly-hourly cycle as the time-based triggers above - a delay set to a few minutes can land up to about an hour late. That's expected, not a bug.

Staff notification

Every time an automation fires, the staff gets notified: by default through the Moderation category of the Logs page (event "Automation triggered"). In advanced mode, you can instead set a dedicated channel for that one automation, if you'd rather not mix it with the general moderation log.

No confirmation, just enable/disable

Unlike custom commands, there's no "are you sure?" here - nobody is present to click it when an automation fires on its own. The safety net is the enable/disable toggle: leave a new automation off while you set it up, turn it on once you're confident.

🧪 "Simulate on me"

On each automation, a button shows what WOULD happen for you specifically - conditions and each action - without executing anything (no Discord write, no database write). Useful to check a config before turning it on for real. Since the tester is almost always staff, actions like kick/ban/timeout often show as "blocked" - that's expected: the same protection applies for real once the automation is live.