Permissions appropriate to the selected penalty; the bot’s role must be above the moderated member.
Step by step
1
Enable Moderation and choose team roles and the automatic moderation rules you need.
2
In the commands section, choose available commands. Save; the server command list updates shortly afterwards.
3
In Discord, use /warn, /timeout, /kick or /ban with an appropriate reason.
4
The Cases tab shows history. Filter by member or case details. An empty list means no cases have been recorded yet.
5
Reversing actions and deleting data require appropriate permissions. The bot cannot moderate members whose roles are equal to or higher than its own.
6
Raid: pick a profile (lenient, standard, strict or custom) and start with observe mode. The bot combines signals (join waves, cross-channel spam, mentions, links) and never punishes for account age alone. Emergency lockdown is in the Raid tab, in the Discord alert and under /antiraid lockdown. When it ends the bot restores channels without overwriting changes made by hand in the meantime.
Settings explained
Moderator roles
The team allowed to use moderation commands.
AutoMod
Rules for detecting and responding to messages.
Escalation / anti-raid
Actions after repeated violations or suspicious joins.
Reason, DM and mod log
How penalties are communicated and cases recorded.
Commands
Choose the commands available on this server.
Available commands
A command appears in Discord after enabling its module and the command in the dashboard.
Configure the provider, behaviour and AI usage costs.
+Basic features are free. PexoBot+ adds features or raises limits.
Where to find it
Dashboard → selected server → AI
Bot permissions
Access to the channels in use; Send Messages and Embed Links if the module publishes messages.
Step by step
1
Choose Anthropic, OpenAI or Gemini. Enter your API key and save it with the separate key button. The key is excluded from configuration sent to the browser.
2
Enter a model name available from your provider. OpenAI-compatible APIs can use a custom base URL.
3
Set the assistant name, system instructions, extra server information and reply language. The bot substitutes {name}, {server} and {channel} variables.
4
Choose triggers: mentions, replies to bot messages, selected channels or a custom prefix such as !ai.
5
Choose allowed roles and ignored channels. An ignored channel blocks AI even for mentions or prefixes.
6
Set context, reply cooldown, length and tokens. A custom daily limit can lower the plan limit but cannot raise it; 0 uses the plan limit.
7
Choose a message reply or a new channel message, the typing indicator and sources.
8
In advanced settings choose UTC or another IANA time zone, e.g. Europe/Warsaw. Every request includes the current date, weekday and time in that zone and UTC.
9
Save and run a test. Then check /ai or your chosen trigger in Discord.
10
PexoBot+ provides higher limits, search, broader history scanning and a member directory. History range sets the maximum number of scanned messages.
Settings explained
Provider, model and key
API connection; the key is saved with a separate button.
Persona and server information
System instructions, name, extra context and language.
Triggers and access
Mentions, replies, channels, prefix, allowed roles and ignored channels.
Length, tokens and daily limit
Control replies and API usage; a custom limit cannot raise the plan limit.
Context and history
Message count and history scanning range with PexoBot+.
Reply mode
Reply to a message or send a new channel message, sources and typing indicator.
PexoBot+ extensions
Search, broader history and a member directory.
Available commands
A command appears in Discord after enabling its module and the command in the dashboard.
/ai
Ask the AI
Plan limits
Setting
Free
PexoBot+
Replies per day
150
5000
Context messages
6
20
AI channels
1
10
Reply length (characters)
1000
4000
These are this instance’s plan limits. Some features have extra conditions described beside dashboard settings.
Start with Diagnostics (server panel → Diagnostics). It shows missing bot permissions, deleted channels and roles, roles above the bot's role and missing commands, with a link to the settings. “Why can't the bot…?” checks a chosen role, channel or person and changes nothing on the server.
2
A channel or role is missing: check the bot’s access, channel type and role position. Refresh the dashboard after changing Discord settings.
3
Cannot publish: enable the module, choose a channel, save and check Send Messages and Embed Links permissions.
4
A command is missing: check both module and command switches; wait a few seconds after saving. Its name may conflict with another command.
5
No history or cases: these views populate after the bot performs relevant actions. An empty view does not mean configuration was lost.
6
The bot cannot see messages: the instance administrator should check Message Content Intent in Discord Developer Portal.
7
AI refuses or returns an error: check the key, model, provider quota, ignored channels and daily limit. The tester shows details.
8
Saving failed: keep the page open. Changes stay in the form; read the message, correct the data and save again.