Documentation

What you need before you start #

You must be the owner of the Discord server or hold the Administrator permission in it. Krios validates this against the Discord API on every dashboard session, so access cannot be spoofed by lower-ranked members. You also need a Discord account in good standing to complete the OAuth sign-in; no separate Krios account or password is created, and revoking access is always available from your Discord Authorized Apps settings.

If your community uses Discord's Community feature with membership screening or rules channels, Krios is fully compatible — the welcome module fires after a member passes screening, not before, so welcome cards are only sent for members who actually complete onboarding.

Recommended first-day checklist #

After the wizard finishes, take five extra minutes to harden your server: confirm the Krios role sits above your moderator roles, enable the Anti-Nuke module from the dashboard and review its default thresholds, publish a ticket panel in your support channel with /ticket-panel, and send a test /warn against an alt or a willing moderator to verify the log channel receives the event. Servers that complete this checklist on day one report dramatically fewer configuration issues later, because every subsystem has been exercised end to end while the setup is still fresh.

Full Panel ↔ Bot parity #

Every configurable bot feature has its equivalent in the web panel: Auto-Mod, Audit Logs (with filter, search and pagination), Giveaways, Reaction Roles, Counting Game, Krios Gatekeeper (anti-bot verification with its verified role), the Suggestion Box, the live Status Panel and the Krios Enterprise promo. Configure from Discord with commands or from the browser — both write to the same database instantly.

For external monitoring, the public /api/health endpoint checks the web process and the database in real time (200 = healthy, 503 = degraded), and the panel APIs include anti-abuse request limits.

How detection works #

Krios continuously watches your server's audit log and correlates every destructive action — bans, kicks, channel deletions, role deletions, and webhook creations — with the account that executed it. Each executor gets a rolling action counter per category, evaluated inside a configurable time window. When any counter crosses its threshold within that window, the engine classifies the behavior as a nuke attempt and triggers the configured response instantly, without waiting for human confirmation.

This windowed-threshold design is what separates legitimate administration from an attack. A moderator deleting one obsolete channel never trips the system; a script deleting fifteen channels in ten seconds does. Every threshold is independently configurable — maximum bans, maximum kicks, maximum channel deletions, maximum role deletions, and maximum webhook creations — so you can tune the sensitivity to match how your staff actually works.

Protection against mass-banning #

Mass-ban attacks are the most common nuke vector because a single compromised moderator account can ban hundreds of members through the API in under a minute. Krios tracks ban velocity per executor: when an account exceeds the configured ban threshold inside the detection window, the engine immediately strips the executor's ability to continue — applying the configured punishment (removing their roles, kicking, or banning the attacker, depending on your settings) — and logs a full forensic record of what happened, including the executor, the targets, and the exact timestamps.

Because detection is velocity-based rather than permission-based, this protection works even when the attacker is a long-trusted moderator whose account was phished. The account's history does not matter; its behavior in the last few seconds does.

Protection against mass channel and role deletion #

Channel and role destruction is the second pillar of a nuke: deleting every channel erases pinned knowledge, webhooks, and permission structures that can take days to rebuild. Krios applies the same windowed counters to channel deletions and role deletions independently, so an attacker cannot stay under the radar by alternating between the two. When either threshold trips, the engine stops the executor and raises a high-priority alert in your security log channel so your team knows exactly which structures were lost before the intervention.

Webhook creation is monitored as its own category because attackers frequently create webhooks in bulk to spam @everyone with malicious links after a takeover. Exceeding the webhook threshold receives the same treatment as any other nuke signal.

Rogue admin protection #

Most security bots silently exempt administrators, which makes them useless against the actual threat model — admins are precisely the accounts with the power to nuke. Krios takes the opposite stance: with the Anti-Nuke module enabled, administrators are subject to the same behavioral thresholds as everyone else. The only hard limit is Discord's own hierarchy — Krios can only act on accounts whose highest role sits below the Krios role, which is why placing the bot's role at the top of your hierarchy during setup is non-negotiable for full coverage.

For this protection to be meaningful, treat your role hierarchy as a security boundary: keep the set of roles above Krios as small as possible (ideally only the server owner), and audit it whenever staff changes. The server owner can never be acted upon by any bot — that is a Discord platform guarantee — so the owner account should be protected with 2FA and used sparingly.

Configuring thresholds and responses #

All anti-nuke settings live in the dashboard under your server's module configuration. You choose the detection interval, the per-category maximums, and the punishment applied to a detected attacker. Stricter thresholds (lower maximums, longer windows) catch attacks earlier at the cost of occasionally challenging unusually fast legitimate cleanup work; looser thresholds give staff more headroom but let an attacker do more damage before tripping the wire. A practical starting point for most communities is the default configuration, tightened after a week of observing your staff's normal activity patterns in the security log.

When the module intervenes, every action is written to the audit log system with full metadata. You can export this evidence at any time with /audit-export in JSON or CSV format, which is invaluable for post-incident review, for appeals, and for deciding whether a tripped threshold was an attack or a false positive that warrants tuning.

Anti-Spam #

The anti-spam system monitors message velocity and repetition per user and per channel. When a member crosses the spam heuristics — rapid-fire identical messages, mass mentions, or sustained message floods — Krios removes the offending messages and applies a graduated response, starting with a timeout via the mute role created during /setup. Because the mute role's channel overrides were provisioned by the wizard, a muted spammer is silenced everywhere at once, including in threads and voice text channels, with no per-channel configuration needed.

Anti-spam runs entirely on behavior, so it catches both human spammers and self-bot scripts. Every removal is logged with the original message content preserved in the log embed, allowing moderators to review exactly what was deleted and reverse the action if a false positive occurs.

Anti-Link #

The anti-link module blocks unauthorized links to prevent phishing, scam giveaways, and server-advertisement spam — the three most common payloads delivered to Discord communities. When enabled from the dashboard, Krios deletes messages containing links from members who lack an exempt role and notifies the channel briefly so the member understands why their message disappeared. Discord invite links receive special scrutiny since they are the primary vector for raid recruitment and competitor poaching.

Moderators and administrators are exempt by default, and the module is designed to be toggled instantly: many communities enable it permanently in general channels while leaving dedicated media or promo channels free, using Discord's per-command and per-channel integration settings for fine-grained control.

Warnings and escalation thresholds #

The /warn command issues a formal warning to a member with a required reason, stored permanently in the database and visible to your whole staff team. Warnings are the connective tissue of fair moderation: instead of each moderator acting on partial knowledge, every warning is centrally recorded with the issuing moderator, the reason, and the timestamp, so escalation decisions are based on a member's complete history rather than one moderator's memory.

Escalation is automatic and threshold-based: as a member accumulates warnings, Krios applies progressively stronger consequences — a timeout at the first threshold, a kick at the next, and a ban at the final one. This removes the awkwardness of staff having to personally decide when 'enough is enough' and guarantees identical treatment for identical behavior. Members are notified via DM when warned, including the reason, which courts have nothing to do with but community-trust research consistently shows reduces repeat offenses.

Anti-Raid #

Raids — coordinated waves of accounts joining simultaneously to spam, harass, or scout for nuke opportunities — are detected by monitoring join velocity and account characteristics. When a join wave matches raid patterns (many accounts joining within seconds, freshly created accounts, default avatars), Krios can automatically lock down entry by removing the suspicious accounts before they ever post. The module is Premium because it requires sustained, real-time analysis of the member stream, and it pairs naturally with Anti-Nuke: raids are frequently the reconnaissance phase of a later nuke attempt.

All raid interventions appear in the security log with the full list of affected accounts, so legitimate users caught in a wave (it happens — a popular streamer mentioning your server looks a lot like a raid) can be identified and re-invited quickly.

The audit log system #

Every automated and manual action Krios takes — warns, mutes, deletions, anti-nuke interventions, ticket events — flows into a unified audit log stored in the database, independent of Discord's own 45-day audit log retention. The /audit-export command exports this history as a JSON or CSV attachment, filterable by category and capped at the limit you choose, giving you durable, offline evidence for disputes, transparency reports, or staff reviews. Treat the export as your server's black box recorder: when something controversial happens, the answer to 'who did what, when' is always one command away.

Publishing a ticket panel #

Run /ticket-panel in the channel where you want the panel to appear — typically a dedicated #support or #open-a-ticket channel that members can read but not write in. The command accepts options that define the panel completely: a title shown at the top of the embed, a description explaining what the ticket is for and what information members should prepare, the staff role that will be granted access to every ticket opened from this panel, the category under which ticket channels are created, and an accent color to match your server's branding.

Once published, the panel is persistent: it survives bot restarts and requires no maintenance. Members click the button, and Krios instantly creates a private channel visible only to the member, the configured staff role, and the bot itself. If your panels ever end up in a broken state — for example after channel deletions outside the bot — the /reset-panels command rebuilds them cleanly.

Organizing with categories #

Each panel binds to a Discord category, and every ticket opened from that panel is created inside it. This is the key to scaling support: create one panel per concern — general help, member reports, partnership inquiries, billing questions — each pointing at its own category and, if you want, its own staff role. Your moderation team sees report tickets, your admin team sees partnership tickets, and nobody wades through channels irrelevant to them. The /setup wizard provisions a default ticket category for you, but you are free to create additional ones and reference them when publishing specialized panels.

Ticket channels are named predictably after the opening member, so staff can see at a glance who a ticket belongs to. When a ticket is resolved, closing it removes the channel — keeping your category clean — while the record of the conversation lives on in the transcript.

Transcripts and audit trail #

Accountability is what separates a ticket system from a private channel. On Premium servers, every closed ticket generates a full HTML transcript: a styled, self-contained file reproducing the entire conversation — messages, embeds, timestamps, and participants — that can be archived, shared with the affected member, or reviewed during staff audits. Transcripts make 'a moderator was rude to me in a ticket' a verifiable claim instead of a he-said-she-said dispute, protecting both members and staff.

Ticket lifecycle events — opened, claimed, closed, by whom and when — are also written to the unified audit log, so ticket activity appears in /audit-export alongside moderation actions. For communities with formal support SLAs, this is the data source for measuring response times and ticket volume.

Best practices for support teams #

Keep the panel description specific: tell members what to include (their order ID, the user they are reporting, screenshots) so staff do not spend the first three messages extracting basics. Restrict the /ticket-panel command itself to administrators via Discord's integration settings, while granting the day-to-day staff role only the ability to participate in tickets. And establish a closing discipline — tickets that stay open indefinitely clutter the category and bury genuinely active conversations; close resolved tickets promptly and rely on transcripts whenever history is needed.

Universal modal tickets #

The ticket panel now uses a single "🎫 Abrir Ticket" button. When a member clicks it, Krios opens a modal asking for a Subject and a Description, then creates a private channel pre-filled with their answers.

This replaces the old fixed-category dropdown, so the system works on any server without extra setup. Re-run /ticket-panel to publish the new button-based panel.

/setup — guided module setup #

Use /setup welcome to pick the channel where dynamic welcome cards are sent and toggle the module on or off. Use /setup counting to enable the Counting Game in a dedicated channel; enabling it resets the streak so the server starts counting from 1.

Every /setup subcommand validates that Krios has the permissions it needs in the target channel before saving, and reports exactly what was changed.

/config — fine-grained configuration #

The /config command (Manage Server permission) exposes per-module settings: anti-nuke thresholds and action, anti-link toggles and domain whitelist, ticket category and limits, warn escalation thresholds, anti-spam threshold/interval/action, the leveling curve, and auto-responder management (autoresponder-add, autoresponder-remove, autoresponder-list).

Only the options you provide are changed — everything else keeps its current value — and each change is recorded in the audit log.

Always in sync with the dashboard #

Because the bot and the web dashboard share one database, there is no separate sync step. After a /config change the bot's in-memory cache is invalidated immediately, so the new configuration takes effect within seconds.

/help — the dynamic command guide #

Krios ships a self-updating /help command. Run /help on its own to see every loaded command grouped by category (Security & Anti-Nuke, Moderation, Setup, Engagement, and Utility) with a one-line description for each — the list is generated at runtime, so it always reflects exactly what the bot can do.

Run /help <command> (for example /help setup) for a deep-dive: the command description, its required permissions, scope, and a full breakdown of every subcommand with its options. Because Discord will not let you run a parent command that owns subcommands, /help setup explicitly lists how to invoke each one — e.g. /setup welcome and /setup counting — so you never have to guess the right syntax.

How it works #

Pick a dedicated channel and the game begins at 1. Each new message must be the exact next number in the sequence, and the same member cannot count twice in a row — someone else has to post the following number. A correct count is confirmed with a ✅ reaction.

The counter is stored per server and updated atomically, so even if two people send the next number at the same instant only one of them advances the streak.

Breaking the streak #

Posting the wrong number, posting something that is not a number, or counting twice in a row breaks the streak. Krios reacts with ❌, resets the count to zero, and announces who broke it so the server can start again from 1.

Because the channel is meant only for counting, any non-numeric message is treated as a break — keep regular chat in another channel.

Setting it up #

Enable it with /setup counting by choosing the channel and toggling it on, or from the dashboard's Counting Game module card. Enabling it always resets the streak to a clean start.

Instant introduction #

When a member starts a message by mentioning @Krios, the bot replies with a clean, branded embed that explains what Krios is, links to the dashboard at kriosapp.dev, and lists a few starter commands such as /ping, /setup and /rank.

It is a friendly onboarding touch: new members get pointed to the control panel and the most useful commands immediately.

When it triggers #

The reply only fires when the message begins with the bot mention, so mid-sentence mentions and reply pings stay quiet, and @everyone / @here are always ignored. This keeps the channel free of noise while still answering genuine questions.

How it works #

Type krios <command> (case-insensitive, so krios, Krios and KRIOS all work) and Krios runs the exact same logic as the matching slash command. Arguments are positional: mention a user or paste their ID for commands like krios userinfo @user, and pass a number for krios purge 10 or krios slowmode 15.

The prefix only triggers when the first word after krios is a real command. A normal sentence that merely starts with the word krios is left completely untouched, so it never interferes with conversation, XP gain or Auto-Moderation.

Hybrid commands & aliases #

Commands available via both slash and prefix are marked with 🗣️ in /help. Many accept short aliases: krios xp (rank), krios whois (userinfo), krios lb (leaderboard), krios clear (purge) and krios si (serverinfo), among others.

Permission and server-only rules are identical in both modes: a member who cannot use /purge cannot use krios purge either, and Krios replies with the same insufficient-permissions notice.

The command arsenal #

Information: krios serverinfo (server stats), krios userinfo @user (member details), krios avatar @user (full-resolution avatar) and krios status (uptime, RAM and latency).

Moderation: krios purge 10 (bulk-delete 1–100 messages) and krios slowmode 15 (set channel slow mode). Engagement: krios rank, krios leaderboard and krios help all work with the prefix too.

/giveaway — run giveaways #

/giveaway start takes a channel, prize, number of winners and a duration (for example 30m, 2h or 1d), and posts an embed that members enter by reacting with 🎉. You can optionally gate entry with a required role, a minimum XP level, or a minimum number of days in the server.

Giveaways close automatically when their timer ends — Krios picks the winners at random among eligible entrants and announces them. Use /giveaway end to close one early, or /giveaway reroll on a finished giveaway to draw fresh winners.

/reactionrole — self-assignable roles #

/reactionrole create posts a panel in a channel (title, description, color and an optional max-selections limit). /reactionrole add binds an emoji to a role on that panel by its message ID, and Krios adds the reaction automatically; /reactionrole remove detaches one.

Members then react on the panel to receive a role and remove their reaction to lose it. If a max-selections limit is set, extra reactions are reverted so members never exceed it.

/suggest — suggestion box #

/suggest setup defines the channel where server suggestions get posted (Manage Server). Any member can use /suggest submit to send an idea: Krios posts it as an embed and automatically adds 👍/👎 reactions so the rest of the server can vote.

/giveaway — full management, zero friction #

No more copying a message ID by hand: /giveaway end, /giveaway reroll and /giveaway edit auto-suggest active (or ended, for reroll) giveaways as you type. /giveaway list shows every giveaway currently running in the server at a glance, with its prize, channel and time left.

/giveaway edit lets you adjust the prize, description, winner count, duration or requirements of a giveaway that's already running — the change reflects instantly on the public message, no need to cancel and recreate it.

/poll and /choose — frictionless decisions #

/poll creates NATIVE Discord polls: up to 5 options, durations from 1 hour to 7 days and optional multi-select. Discord tallies votes in real time and posts the results automatically when the poll closes — no manual reactions that can be gamed. Also via prefix: krios poll Pizza or tacos? | Pizza | Tacos.

For quick decisions, /choose has Krios pick at random from the comma-separated options you give it.

/trivia — trivia with a leaderboard #

Krios ships a trivia game with over 2,000 questions across six categories: anime, games, movies, countries, flags and culture. Many flag, anime, movie and game questions include a real image (the official flag, the anime's cover art, the movie poster, or the game cover). Use /trivia with no category for competitive mode: a random question appears and clicking the correct button earns 1 point on the trivia leaderboard (a wrong answer costs 1). Picking a specific category is practice mode and does not affect the ranking.

Triple Points mode (/trivia dificil:true, or krios trivia dificil) throws a hard academic question about history, physics, maths, science, geography or art: it is worth 3 points if you get it right, minus 3 if you miss, and only the person who asked can answer. Check the standings with /leaderboard tipo:Trivia.

/mod — moderation actions #

/mod ban (user, reason, delete_days 0–7), /mod kick (user, reason), /mod timeout (user, duration up to 28 days, reason), /mod untimeout (user) and /mod clear (bulk-delete 1–100 recent messages). Each subcommand checks that the moderator and the bot hold the right permission and that the target is actionable.

Ban, kick and timeout are written to the infraction log so they appear in a member's moderation history alongside warnings.

/lockdown — channel control #

/lockdown lock removes the Send Messages permission for @everyone in a channel (the current one by default), and /lockdown unlock restores it. Ideal for pausing a channel during a raid or an announcement.

/lockdown — emergency anti-raid lockdown #

When a raid hits, /lockdown lock instantly denies the Send Messages permission for @everyone in the current channel (or a channel you pass explicitly), freezing the conversation while you respond. /lockdown unlock cleanly restores the previous state. Krios also posts a visible notice in the affected channel so members understand what happened.

The command requires the Manage Channels permission and verifies that Krios itself holds it in the target channel before making any change, so it fails safely with a clear error instead of half-applying an override.

Advanced Audit Log (/auditlog) #

Configure an audit channel with /auditlog setup <channel> (or from the dashboard's Audit Log card). From that point on, nothing escapes Krios: channels created, deleted and edited; roles added, removed and modified; bans and unbans with reason and executor; nickname changes; voice channel joins, leaves and moves; deleted and edited messages; and member joins/leaves — all as clean, color-coded embeds.

Channel and role events include the real executor (pulled from Discord's native audit log), with a visual indicator when the action took over 5 seconds to appear in the native log. Use /auditlog disable to turn it off; the dashboard card mirrors the command for full parity.

/warnings — warning history #

/warnings list shows a member's active warnings with their ID, reason, moderator and date. /warnings clear removes one specific warning by ID, and /warnings clearall wipes every active warning for a user at once. Every clear is written to the audit log.

/aimod — AI auto-moderation (Premium) #

On top of the word filter and Anti-Link, Krios can analyze a message's CONTEXT using a specialized external content-detection service to catch toxicity and harassment a word list would never flag. It's a fully optional layer added on top of existing Auto-Mod — never a replacement.

/aimod toggle turns it on or off; /aimod threshold tunes how strict it is (0 to 1 — the lower, the more sensitive). It is a Premium feature (each analyzed message has a real cost), and it also requires the bot owner to have configured this layer separately — without both, the command stays available but inactive.

/utility — server & user info #

/utility serverinfo shows the server's stats (owner, creation date, members, roles, channels and boost level), /utility userinfo shows a member's account and server details, and /utility avatar displays a user's avatar in full size.

/fun — engagement #

/fun 8ball answers a yes/no question with a classic Magic 8-Ball reply, /fun coinflip flips a coin, /fun roll rolls a die (100 sides by default), and /fun poll posts an embed question and auto-adds 👍 / 👎 reactions for voting.

/announce — branded announcements #

/announce takes a channel, a title, and a description and publishes a polished, DayronLabs-branded embed to the target channel — Krios violet accent, server name and icon in the header, and a signed footer. Use \n inside the description to add line breaks.

The command is Administrator-only and checks that Krios has View Channel, Send Messages, and Embed Links permissions in the destination before posting, then returns a private confirmation to the author. Perfect for official announcements, maintenance windows, and staff broadcasts.

New games: /ppt and /dados #

/ppt plays Rock, Paper, Scissors with interactive buttons — pick your move and Krios reveals Win/Lose/Tie. /dados rolls configurable dice (choose the number of sides and how many dice, up to 5).

The coin flip now uses strictly fair 50/50 RNG, and the magic 8-ball is interactive: it shows a "shaking" state before revealing one of 20 varied answers.

Reminders, AFK and Snipe #

/remind create schedules a personal ping (e.g. "1h Check on the server") that Krios delivers once it's due, with /remind list and /remind cancel to manage them. /afk marks your status as away — it clears itself the moment you send your next message and automatically notifies anyone who mentions you in the meantime. /snipe recovers the last deleted or edited message in a channel, useful for light moderation or plain curiosity.

Live Status Panel (/status panel) #

/status view shows a one-off diagnostic (uptime, database, website, RAM and latency) visible only to you. /status panel start posts that same diagnostic as a persistent panel in a channel, which Krios automatically refreshes every 60 seconds with zero manual upkeep — perfect for a team-visible #status channel. /status panel stop stops it. Both panel subcommands require Manage Server.

New utilities: /banner, /roleinfo, /timestamp and /quote #

/banner shows any user's profile banner in high resolution. /roleinfo breaks a role down: color, how many members hold it, its position in the hierarchy and which key permissions it grants — accepts a mention, an ID or just the name.

/timestamp generates Discord's dynamic timestamps (<t:…:F>) in every format, ready to copy and paste: each reader sees them in their own timezone. /quote quotes any server message into an embed with author, image and jump link, honoring the invoker's channel permissions.

On top of that, /avatar now includes the server-specific avatar when one exists, and /userinfo shows public Discord badges, boost status and active timeouts.

/dato — fact of the day #

The /dato command shows the “fact of the day”: an on-this-day event from history, in both Spanish and English at once. It is the same fact for the whole server throughout the day and refreshes daily. It also works via the prefix with krios dato.

/rank — visual level cards #

/rank now generates an image card with your avatar, level, server ranking and an XP progress bar, instead of a text-only embed — the same canvas engine used by Premium welcome images.

Economy and role shop (/economy, /shop) #

Members automatically earn coins by chatting (with its own cooldown, independent of XP's), can claim a bonus with /economy daily, and can send coins to each other with /economy pay.

The shop (/shop) lets them spend those coins on cosmetic roles you define from the panel — Server Settings → Economy — or with /shop agregar/quitar (Manage Server). It's free on every plan.

Interactive onboarding checklist #

When you add Krios to a new server, alongside the welcome message it now posts a 3-step checklist with buttons: turn on Anti-Nuke, create a ticket panel, and invite your staff team. The first two steps check themselves off automatically once you complete them; the third is confirmed with a button.

Real dashboard analytics #

Each server's Analytics tab (Server Settings → Analytics) shows real charts of daily messages and new members vs. leaves over the last 30 days, plus a top-5 of the most active members. A freshly set-up server needs a few days of activity before the charts have enough data to be meaningful.

Weekly summary via direct message #

Every Monday, Krios sends a direct message to each server's owner with a summary of the week: activity, new members, the most active members, and moderation actions.

It's on by default for every server. If you'd rather not receive it, turn it off from the dashboard (Server Settings → Weekly Digest) or with /config weeklydigest enabled:false.

Starboard (/starboard) #

The Starboard automatically highlights the most-reacted messages in your server in a dedicated channel. When a message reaches the star threshold (or whatever emoji you configure), Krios posts an embed in the starboard channel with the original content, the author, and a live reaction counter.

Set it up with /starboard setup <channel> [threshold] [emoji] or from the Starboard tab in the dashboard. The default threshold is 3 reactions; change it with /starboard threshold <number> (between 1 and 25). The system includes anti-loop protection (messages posted to the starboard channel are never re-processed) and anti-self-star (the original message author's own reaction doesn't count toward the threshold).

Custom Commands — your server's own commands #

Build your own text commands: anyone types "krios <name>" and Krios replies with whatever you configured. Free includes up to 15 plain-text commands.

Premium raises the limit to 100 and adds a custom embed, up to 3 buttons, a required role, a per-user cooldown, and up to 3 aliases per command. Manage them from the Custom Commands tab in the dashboard or with /custom-commands (create, edit, delete, list).

DM Welcome #

Alongside the welcome message in the server channel, Krios can send a private message to every new member the moment they join — useful for instructions you'd rather not post in a public channel. Free for every server.

Turn it on with /config dmwelcome enabled:true [message] or from Server Settings → DM Welcome. It supports the same placeholders as the channel welcome message: {user}, {server}, and {memberCount}.

YouTube & Twitch alerts #

/youtube add watches a YouTube channel and posts an embed the moment it uploads a new video. Free servers can watch up to 5 channels; Premium raises that to 20.

/twitch add watches a Twitch streamer and posts an embed the moment they go live. Free servers can watch up to 2 streamers; Premium raises that to 5.

Weblog — automatic milestone log #

/weblog setup turns a channel into an automatic activity feed: level-ups and giveaway winners are logged there as they happen, no manual posting required. Free servers keep the last 100 entries; Premium keeps the last 500 (older entries roll off automatically).

Sticky messages (Premium) #

/sticky set pins a message to the bottom of a channel: every time someone posts, Krios deletes the old sticky and reposts it so it always stays visible. A Premium-only feature.

Voice-role links (Premium) #

/voicerole link grants a role automatically the moment a member joins a specific voice channel, and removes it when they leave (unless another linked channel still applies). A Premium-only feature.

Timed reaction roles & higher caps (Premium) #

/reactionrole add now accepts an optional duration (Premium only) so a role offer can expire automatically — Krios removes the reaction from the panel once it does. Free servers can have up to 250 reaction role entries per server; Premium raises that to 1,000.

Farewell messages (Premium) #

A dedicated goodbye message in its own channel, separate from welcomes — configured with /config goodbye. This is a Premium-only feature; Free servers do not send farewell messages.

Drama Watcher — public moderation feed (Premium) #

/config dramawatcher posts every ban, kick, timeout and warn to a channel visible to your whole community — full transparency on moderation action, separate from the private staff audit log.

AI Auto-Moderation (Premium) #

/aimod turns on a moderation layer that analyzes a message's CONTEXT (not just a word list) using a specialized external service, catching toxicity and harassment classic Auto-Mod would miss. It is Premium-only because every analyzed message has a real per-use cost.