Features — Sentinel

HONESTY

“Implemented in code” means the feature exists in the source. It was reviewed by reading the code, not by running the bot, so individual behaviours may differ in production. “Needs external setup” means it relies on a third-party service, API key or node that the bot operator must provide.

ModerationImplemented in code

Day-to-day moderation commands: kick, ban, unban, mute, unmute, warn (with a stored warning history), softban, bulk message clearing, channel lock/unlock, slowmode, nickname and role changes.

Getting started: Staff use /moderation subcommands; they are also available as prefix commands (default prefix !).
Requirements: The bot needs the matching Discord permission (Ban Members, Kick Members, Manage Messages, Manage Roles, etc.).

/moderation

AutoModImplemented in code

A rule engine with 10 modules: anti-spam, anti-flood, mention protection, link protection, invite protection, content filters, anti-raid, scam protection, account security and edit monitoring. Each module can log, delete, warn, time out, kick, ban or quarantine, with escalation, exemptions, presets, an incident log and statistics. A monitor mode detects and logs without punishing.

Getting started: Run /automod setup, then tune modules in /automod panel. Use /automod test to preview what a sample message would trigger before enabling punishments.
Requirements: Message Content intent. A log channel is chosen during setup. Data is kept in the bot’s automod.json.

/automod

AntiNukeImplemented in code

Rate-based protection against destructive actions. 10 protection modules watch channel deletion/creation/changes, role deletion/creation/changes, bans, kicks, webhook creation and bot additions; each has its own threshold and time window (for example 3 channel deletions within 10 seconds by default).

Getting started: Open the panel with /antinuke setup, toggle modules and edit thresholds.
Requirements: Uses the server audit log; the bot should be placed high in the role list so it can act.

/antinuke

Security Center & HoneypotImplemented in code

The Security Center offers a status overview and a server lockdown that locks text channels for the default role, then restores what it changed with /security unlock. The honeypot is a trap channel: any normal user message posted there is treated as a trigger and removed automatically.

Getting started: /security setup, /security lockdown; /honeypot setup creates or selects the trap channel.
Requirements: Manage Channels / Manage Roles for lockdown; Manage Messages for the honeypot.

/security/honeypot

VerificationImplemented in code

Gate your server behind a verification button. Configure a verified role and an unverified role, a verification channel and category, a log channel, a custom panel title/description and button text. Options include blocking bots, a minimum account age, a minimum time in the server and DMing users.

Getting started: /verify setup walks through the steps; /verify panel posts the panel; /verify config shows the current setup.
Requirements: Manage Roles and Manage Channels. Verification is disabled until you configure it.

/verify

WelcomeImplemented in code

Greet new members with a configurable message (placeholders such as server name and member count), an optional welcome embed, an optional generated welcome image card and an optional direct message.

Getting started: Open the configuration panel with /welcome setup.
Requirements: The image card needs the Pillow library on the bot host; without it the card is skipped.

/welcome

TicketsImplemented in code

A full support-ticket system: panels and ticket types, claim/unclaim, assignment, priority and status, staff-only notes, add/remove members, rename, transcripts, statistics and a configuration diagnosis. Stored in a local SQLite database. English and French interface.

Getting started: /ticket setup opens the admin panel; /ticket panel manages panels; /ticket diagnose checks the configuration.
Requirements: Manage Channels to create ticket channels; staff roles are configured in the panel.

/ticket/support

MusicNeeds external setup

Music playback in voice channels with search, queue management (play next, move, shuffle, jump, history), loop, seek, lyrics, volume, audio filters (bass boost, nightcore, vaporwave and presets), autoplay and per-server settings. Searches YouTube, YouTube Music and SoundCloud.

Getting started: /music play, /music queue show, /music panel; admins use /music admin (status, nodes, DJ role, permissions).
Requirements: Requires a reachable Lavalink v4 node. Availability depends on that node; audio sources can change or be blocked.

/music

TempVoiceImplemented in code

Temporary voice channels created on demand, with a control panel for the room owner: rename, user limit, lock/unlock, hide/show, transfer, claim, invite or remove members and delete. A three-step setup wizard configures components and resources.

Getting started: /tempvoice setup launches the wizard; /tempvoice panel posts the public panel.
Requirements: Manage Channels. Data is stored in voicetemp.json.

/tempvoice

Economy & CreditsImplemented in code

A server economy with wallet and bank, daily and weekly rewards, work, payments between members, a custom shop, missions, a leaderboard and statistics. A separate lightweight credits module offers balance, daily and stats, with admin-only add/set/remove controls.

Getting started: /economy panel configures the economy; /economy additem and /economy removeitem manage the shop.
Requirements: Stored in local SQLite databases.

/economy/credits

LevelingImplemented in code

XP from text messages and voice activity, level-up messages, rank cards you can customise (background, themes), leaderboards by XP / voice / messages, a daily XP streak, role rewards, XP multipliers, temporary XP events, ignored channels/roles and a minimum account age.

Getting started: Admins use /levelset (settings, rewards, multipliers, events, XP edits); members use /leveling or /rank.
Requirements: Manage Server for admin commands. Data is stored in leveling.json.

/leveling/levelset/rank/leaderboard

GiveawaysImplemented in code

Create, edit, pause, resume, end and re-roll giveaways, and view information, lists and statistics.

Getting started: /giveaway create starts one; /giveaway reroll picks a new winner.
Requirements: Manage-level permission is declared on admin commands (see the directory).

/giveaway

Roles & interactive buttonsImplemented in code

Reaction roles, automatic roles driven by members’ custom status text, and a builder for interactive Discord buttons that you can publish, edit, enable, disable and duplicate.

Getting started: /reactionrole setup, /statusrole create, /button create.
Requirements: Manage Roles; the Presence intent is used for status-based roles.

/reactionrole/statusrole/button

Announcements & embedsImplemented in code

Compose and preview announcements, send quick ones, schedule or cancel them, save templates and review history. A standalone command builds custom embeds.

Getting started: /announce create, /announce schedule, /embed.
Requirements: Permissions declared in code are listed in the directory.

/announce/embed

Social notificationsNeeds external setup

Post a message in a channel when a followed TikTok or YouTube account publishes a new video, with per-server configuration, previews and a status view.

Getting started: /notify add, /notify status; a separate /youtube group subscribes to channels.
Requirements: Needs the optional yt-dlp package; platforms can throttle or block requests, which the bot reports as an error.

/notify/youtube

Flow automationImplemented in code

Workflow automation inside Discord. Triggers: manual, member join/leave, message sent, reaction added, role added/removed, scheduled. Conditions: role membership, account age, channel, message text, time. Actions: send message, send DM, add/remove role, wait, log, stop, time out member, delete message. Includes testing, run history and safety controls.

Getting started: /flow panel or /flow create; try a workflow with /flow test before enabling it.
Requirements: Permissions depend on the actions you use (roles, timeouts, deletions).

/flow

Backups & snapshotsImplemented in code

Save your server configuration as a backup, list and inspect backups, and restore from them. Server snapshots can also be created, viewed, compared and restored.

Getting started: /backup create, /backup list, /server snapshot create. Review a snapshot with view or compare before using restore.
Requirements: Restores change your server structure; they need high permissions and should be tested on a spare server first.

/backup/server

Server creatorNeeds external setup

Build a complete Discord server (categories, channels, roles) from a template or generated by AI, browse templates, save the current structure as a template, or clean up manageable channels and roles.

Getting started: /servercreator, /servertemplates. Use /servercleanup with care: it removes existing channels and roles.
Requirements: AI generation needs an OpenRouter API key on the bot side; template mode does not.

/servercreator/servertemplates/servercleanup/serversavetemplate/serverdeletetemplate

Server panels & statisticsImplemented in code

A configuration dashboard inside Discord (/panelsetup), a statistics manager that maintains statistic channels (/statssetup), a per-server bot profile and a counting game.

Getting started: /panelsetup, /statssetup, /bot profile, /counting setup.
Requirements: Manage Server / Manage Channels as declared on each command.

/panelsetup/stats/bot/counting

UtilitiesImplemented in code

Information and helper commands: help, ping, uptime, bot/server/user/role/channel/emoji information, avatars and banners, permissions, timestamps, snowflakes, a calculator, polls and personal reminders.

Getting started: Members can use /utility help to start.
Requirements: Polls and reminders are stored in a local SQLite database.

/utility

OSINT toolkitNeeds external setup

Lookups on public information: IP, RDAP/WHOIS-style data, DNS, URL and HTTP headers, SSL certificates, robots.txt, sitemaps, security.txt, site technology, GitHub profiles, hashing, e-mail domains and username checks. These queries are sent to third-party services.

Getting started: /osint ip, /osint dns, /osint ssl…
Requirements: Depends on the availability of third-party services. Use only on targets you are allowed to investigate.

/osint

Image toolsNeeds external setup

Edit images (grayscale, blur, resize, caption, pixelate and more), analyse them (info, dominant colour, palette), apply fun effects, look up country flags and generate images from a prompt.

Getting started: /image edit …, /image analyze …, /image ai generate.
Requirements: AI image generation calls a public third-party endpoint (Pollinations), so it depends on that service.

/image

AI chatNeeds external setup

Chat with Sentinel AI through OpenRouter. A server can use Sentinel’s configured provider or supply its own OpenRouter key; messages you send to it are processed by that provider.

Getting started: /ai; admins use /aisetup and /aireset.
Requirements: Needs an OpenRouter API key (server-provided or bot-side).

/ai/aisetup/aireset

Fun, games & socialImplemented in code

Polls, 8-ball, dice, rock-paper-scissors, trivia, jokes, riddles, “would you rather”, fortune cookies, a typing-race game, member social profiles and more.

Getting started: /fun, /speedtype setup, /social setup.
Requirements: No special requirements declared beyond Discord permissions.

/fun/speedtype/social/fact/riddle/wyr

Maps, music info, movies & imagesNeeds external setup

Satellite maps and distance lookups, song/artist/album information, movie and TV recommendations with a watchlist, a profile-picture finder with an optional automatic feed, and a board browser. Content comes from third-party sources, so availability and content are outside the bot’s control.

Getting started: /map location, /musicinfo song, /tv, /pfp search.
Requirements: Movie recommendations need a TMDB token on the bot side.

/map/musicinfo/tv/pfp/4chan