Kynex FAQ

Kynex is a comprehensive Discord management bot designed to help server administrators moderate their communities effectively. It includes features like auto-moderation, logging, warning systems, and various moderation commands.

Visit the Kynex website and click on the "Invite" button. Make sure you have the Manage Server permission to add bots to your Discord server.

The bot's prefix is ~. It also supports slash commands (e.g., /help), which are recommended for their ease of use and built-in guides.

Kynex supports both types! Prefix commands start with ~, like ~kick @user. Slash commands start with /, like /kick user: @user. Slash commands offer helpful autocomplete and are easier to discover within Discord.

Use the ~help command for a list of prefix commands or simply type / to see a list of all available slash commands in Discord.

Kynex includes: kick, ban, unban, warn, unwarn, warnings, mute, unmute, lock, unlock, purge, and role commands. All commands are available in both prefix and slash formats.

Use ~warn @user reason to issue warnings. Each warning gets a unique ID. View warnings with ~warnings @user and remove specific warnings with ~unwarn @user warning_id. Warnings are stored per server and include moderator info and timestamps.

Kynex uses role-based muting. You need to create a role named Muted 🔇 in your server and configure its permissions (deny Send Messages in channels). The bot will then assign/remove this role when you use ~mute and ~unmute.

Yes! Kynex automatically filters inappropriate language based on a configurable bad words list. When triggered, it deletes the message, applies a 30-minute timeout to the user, and sends an alert to your configured alert channel.

No, users with the Manage Messages permission are automatically exempt from auto-moderation filters.

Use the /setup-alert command (requires Administrator permission). Select the channel where you want to receive moderation alerts using the dropdown menu. This channel will receive notifications about auto-moderation actions with interactive buttons to manage timeouts.

Auto-moderation alerts include three persistent buttons: +15m (extend timeout by 15 minutes), -15m (reduce timeout by 15 minutes), and Remove Timeout (completely remove the timeout). These buttons work across bot restarts.

Kynex logs: member joins/leaves, message edits/deletes, bulk message deletions, channel creation/deletion/updates, role creation/deletion/updates, member profile updates (nicknames, roles), bans, unbans, and all moderation command executions.

Use the /setup-logs command (requires Administrator permission). You can set separate channels for action logs (moderation events) and error logs (bot errors). Select your channels from the dropdowns and click 'Save Configuration'.

Action logs track server events and moderation actions (joins, leaves, bans, command usage, etc.). Error logs track bot errors and issues that need attention from server administrators.

Currently, logging is all-or-nothing. Simply don't set up log channels if you don't want logging, or set them to a channel only administrators can see.

Check these common issues:
• Make sure you're using the correct prefix, which is ~.
• Verify the bot has Read Messages and Send Messages permissions in the channel.
• Try using slash commands with / instead.
• Check the bot's status to ensure it's online.

Kynex needs appropriate permissions to function. Key permissions include: Kick Members, Ban Members, Manage Messages, Manage Roles, Manage Channels, View Audit Log, and Moderate Members (for timeouts). Ensure the bot's role is high enough in the role hierarchy.

Slash commands can take up to 1 hour to register after inviting the bot. If they still don't appear, try removing and re-inviting the bot with the correct permissions. Make sure you have applications.commands permission enabled when inviting.

Create a role named exactly Muted 🔇 and configure its permissions to deny sending messages in your channels. Make sure the bot's role is positioned higher than the Muted role in your server's role list.

Ensure you've set up an alert channel using /setup-alert. The bot needs the Manage Messages permission to delete filtered messages and Moderate Members permission to timeout users. Remember that users with Manage Messages permission are exempt from filters.

Use /setup-logs to configure your log channels. Ensure the bot has Send Messages and Embed Links permissions in those channels. For detailed audit log information, the bot also needs the View Audit Log permission.

The timeout control buttons in auto-moderation alerts are 'persistent,' meaning they continue to work even if the bot restarts. This ensures moderators can always manage timeouts from alert messages, regardless of when they were sent.

Kynex stores server-specific configuration (prefixes, log channel IDs, alert channel IDs) and warning data (user IDs, reasons, moderator info, timestamps). No message content or personal data is permanently stored. All data is stored per-server and not shared between servers.

Yes! Use the ~ping or /ping command to check the bot's current latency to Discord's servers.

The ban command includes an optional parameter to delete the user's recent messages (0-7 days). Example: ~ban @user 7 spam bans the user and deletes their messages from the past 7 days. Default is 0 days (no deletion).