Moderation history
Warnings, timeouts, cases, automod events, tickets, and staff notes stay together, so the next moderator can see what already happened.
illest.bot keeps moderation, invites, voice rooms, music, rewards, and staff tools in one place, so the server can run without a pile of half-configured bots.
Warnings, timeouts, cases, automod events, tickets, and staff notes stay together, so the next moderator can see what already happened.
See which invite brought someone in, who created it, and whether a code is attracting suspicious joins.
Members create a room when they need one, control who can join, and leave the cleanup to the bot when everyone is done.
Set sensible defaults for member, moderator, and admin commands, then give individual roles access where it is needed.
The goal is not to show off a giant command list. It is to make the daily server stuff easier to trust, easier to find, and easier to hand off when another staff member logs in.
Command access
Choose who can run what, add aliases, and keep the command list understandable for normal members.
Music
Queue music in voice with a stack built for real sessions, not a demo command that falls over after two songs.
Rewards
Handle booster perks, vanity rewards, autoroles, counters, welcome flows, and other server rituals from one setup.
Assistant context
Let the server assistant remember useful context without turning the dashboard into a black box.
commands
Loading command catalog
dashboard
Guild owners get a place to adjust modules, command access, invite alerts, bot profile details, and community systems without asking a developer to make every tiny change.
Permissions
Keep access clean without editing code or digging through env files.
Community
Levels, economy, quotes, RPG systems, and the fun stuff people come back for.
Bot profile
Tune the bot identity so it fits the server instead of looking stock.
Alerts
Review automod, moderation, and staff-facing signals while the context is still fresh.
quiet protection
Catch spam, invite links, risky words, and repeat abuse before it becomes moderator busywork.
Mass joins and suspicious accounts are easier to review when the signal is grouped in one place.
Give moderators a shared trail instead of scattered DMs and half-remembered history.
Setups should feel like they belong in the Discord server, not bolted on after.
Turn on the core tools first, then grow into the rest. No need to set everything up on day one.