Find the answer.
Configure it correctly.

1. Install the bot

Use the official install flow and place the bot role above every role it must manage. Discord role hierarchy still applies even when the bot has broad permissions.

2. Sign in and link commands

Discord OAuth signs you into the dashboard. Generate a one-time linking key there, run /setup, and submit the key through the private modal.

3. Add an AI provider

Save and verify a supported provider, choose a model, and enable server analysis when the model needs to inspect existing channels, roles, or permissions.

4. Generate and approve

Describe the result with /prompt or the dashboard AI Designer. Review every phase, risk level, dependency, warning, and selected action before approval.

Support

For setup help, join the official support server.

Two separate trust checks

OAuth authorizes the web session. The one-time /setup key explicitly binds the Discord command identity to that account. Completing one does not silently complete the other.

Persistent server selection

The dashboard stores the last server you managed, pins it first, restores it after refresh or sign-in, and safely falls back when access disappears.

A server is missing

• Confirm the bot is installed in the server.
• Confirm your Discord account still has Manage Server or Administrator.
• Refresh the server selector after permission or ownership changes.
• Verify the dashboard session belongs to the same Discord account you linked.

Plan mode

Plan mode turns a request into allowlisted actions. The provider cannot run arbitrary code or directly mutate Discord. ServoX normalizes, validates, risk-scores, and freezes the plan before approval.

Chat mode

The standalone /chat command is advisory and server-aware. It supports focused Server, Troubleshoot, Security, Moderation, Roles & Permissions, Music, and Modules modes, temporary follow-up context, and a Create Plan control that still sends changes through the normal review and approval flow.

Existing server context

Server analysis must be enabled for the saved provider before /chat can reason about current channels, roles, modules, permission structure, bot role hierarchy, or recent sanitized operation outcomes. Diagnostic reads reuse live/current data instead of creating duplicate server snapshots.

Temporary conversation memory

Discord /chat keeps only a small bounded context in bot RAM, expires it after six hours of inactivity, caps active sessions, and does not create a persistent transcript table. Use fresh:true or Clear Context to start over immediately. Dashboard chat remains browser-session state.

Search modes

Use /search for an explicit public-web query. /chat can use Auto, Force Search, or No Web mode depending on whether current public information is needed and the server's Web Access policy allows it.

Sources and page reading

ServoX can read eligible public HTTP(S) pages and returns clickable source links. Fetched page text is treated as untrusted reference material rather than instructions to the assistant.

Network safety

The page reader blocks localhost, private, link-local, reserved, and internal address space; validates DNS destinations; and re-checks destinations after redirects before reading content.

Short-lived storage

Web search/page cache is temporary only. Guild TTL is configurable from 6 to 18 hours, defaults to 12 hours, and expired entries are removed automatically. Deployment owners can clear the cache immediately from Owner Console.

Managed search

The managed deployment can run SearXNG privately on localhost with no user-provided search API key. A deployment owner can disable Web Intelligence globally at any time.

Phased execution

Large requests are split into phases so output is reviewable and does not depend on a single oversized provider response. Later phases are generated against the current live state.

Risk levels

• Low: routine additive changes.
• Medium: structural, permission, or automation changes that require stronger confirmation.
• High: destructive, lockdown, or owner-only operations that require the actual server owner and a fresh backup.

Immutable approval

ServoX hashes the exact validated action set. Changing actions, dependencies, parameters, warnings, or risk invalidates the old approval.

Partial failure

Completed actions remain recorded and are not blindly repeated. Review the failed action and create a focused replacement plan for the remaining work.

Role-based authority

Choose moderator roles, administrator roles, and the exact actions each tier can perform. Discord Administrator and the server owner retain full authority.

Ban request flow

A moderator can be allowed to request a ban without directly banning. Administrators can approve or deny the request after ServoX rechecks role hierarchy, permissions, protected targets, and current guild state.

Numbered cases

Warnings, timeouts, kicks, bans, nickname actions, and staff notes can create numbered cases with reasons, evidence, internal notes, summaries, history, revocation, and appeals.

Safety controls

• Protected users and roles cannot be targeted.
• Bulk actions respect configured confirmation thresholds and target limits.
• The bot cannot target the guild owner or itself.
• Role hierarchy is rechecked at execution and approval time.

Raid detection

ServoX evaluates join rate, time windows, minimum account age, and configured risk signals. Progressive response can escalate from alerting to quarantine and lockdown.

Anti-nuke monitoring

The module watches rapid channel, role, permission, webhook, moderation, bot-addition, server-setting, and AutoMod changes through Discord audit logs.

Containment and recovery

Depending on configuration, ServoX can alert, remove dangerous roles, kick, ban, quarantine, lock public messaging, save exact overwrites, and restore the latest protection lockdown.

Recommended rollout

• Start with Alert only.
• Configure the alert channel and trusted users, roles, and bots.
• Run safe simulations.
• Tune thresholds before enabling automatic containment.
• Keep optional /protection commands disabled unless staff need them.

What is scanned

• New and edited message content.
• HTTP/HTTPS links and suspicious host/path patterns.
• Known URL shorteners.
• Attachment extensions and Discord-provided content types.
• Discord tokens, webhook credentials, GitHub/OpenAI/AWS keys, and private-key headers.

Actions

Each threat type can independently alert, delete, DM-warn, or timeout. Start uncertain link detections in alert-only mode and reserve automatic deletion for high-confidence phishing, dangerous files, or credential leaks.

Privacy

Incident logs defang domains and redact secret values. The module does not intentionally repost an exposed credential into Discord logs.

Local-only behavior

The current scanner does not call an external reputation or malware API. It uses local rules, configured trusted resources, and filename/content-type inspection.

Tickets

Publish a panel that creates private support channels with staff claims, transcripts, close controls, and per-member open-ticket limits.

Modmail

Members DM the bot normally. ServoX relays the conversation into either one private channel per conversation or one private forum post per conversation. Forum posts lock and archive when closed.

Forms

Create reusable forms or applications with configurable questions, submission tracking, reviewer roles, and review destinations.

Do not overlap workflows

Twelve verification methods

• Button
• ServoX CAPTCHA
• Discord OAuth
• Code
• Math
• Custom Question
• Account Age
• Join Wait
• Staff Approval
• Adaptive Verification
• Sequence Challenge
• Rules Quiz

ServoX CAPTCHA

ServoX CAPTCHA replaces generic CAPTCHA providers with a rotating ServoX-hosted challenge pool. Distorted codes, icon counting, odd-one-out, color/shape, symbol-order, position, and target-match checks use one-time challenge IDs, expiry, attempt limits, and server-side answers before roles are applied. No Turnstile, reCAPTCHA, or hCaptcha key is required.

Delivery and fallback

Verification can run in the current channel, DMs, DM-preferred mode, or both. Failed DMs can fall back to a configured channel or an automatically created verification-help channel. Send Verification Again and Verify Here Instead let members recover without staff manually rebuilding a session.

Challenge-specific controls

Configure account age, join wait, code length, math difficulty, custom question/answer, sequence length, rules-quiz questions, session lifetime, attempt limits, and the Adaptive risk threshold from Verification Studio.

Adaptive verification

Adaptive Verification evaluates account-age and recent-join signals and can escalate higher-risk members to the ServoX CAPTCHA while allowing lower-risk members through a lighter check.

Auto Roles remains separate

Auto Roles assigns configured roles when humans or bots join. Verification 2.0 owns access verification, its panel, sessions, methods, and role changes; neither feature depends on the other being enabled.

Self-service roles

Use buttons, select menus, or reaction-role mappings for interests, notifications, regions, platforms, colors, and similar member choices.

Sticky and level roles

Sticky roles restore eligible roles after a rejoin. Level roles award configured roles from persistent XP progression.

Hierarchy rule

Member lifecycle

Welcomer supports join, leave, direct-message, embed, and placeholder messages. Welcomer Studio adds drag-and-drop avatar and text layers, templates, safe remote backgrounds, live preview, and a real test-send action. Invite tracker attributes joins and maintains active invite credit.

Channel automation

Statistics publishes live counters, Counting validates number sequences, Sticky messages keeps important content visible, and Starboard highlights community-selected posts.

Autoresponder

Create exact, contains, or validated regex triggers with cooldowns, channel/role restrictions, and text or embed responses.

Giveaways and events

Authorized staff can schedule giveaways and community events with announcement channels and management controls.

63-game catalog

Games v0.12 keeps the six core games and adds 57 titles across Strategy, Words & Trivia, Puzzles, Arcade, Cards & Dice, Adventure, and ServoX Originals. /games arcade shows enabled titles, while autocomplete on /games play and /games leaderboard keeps the larger catalog easy to use.

Solo and duel games

Every catalog entry declares whether it is solo or duel. Duel games use an accept/decline challenge flow. Complex board and party titles use compact Discord adaptations so they fit component and message limits without requiring an external game client.

Minesweeper Bomb Scan

Each Minesweeper round includes one Bomb Scan. Arm it, select a tile, and ServoX privately reports how many bombs are inside the selected 2×2 area.

Independent rewards

Games owns its own stats and works normally with rewards off. Server managers may separately enable Economy coin rewards, Leveling XP rewards, or both. If either destination module is disabled, ServoX skips that reward without disabling the game.

Anti-farming controls

Reward configuration includes minimum game duration, daily coin and XP caps, optional participation rewards, and a repeated-opponent cooldown. Core games retain per-game win values; expanded games use a separate configurable default win reward.

Channel and visibility controls

Managers can restrict games to selected text channels, control public multiplayer challenges, choose whether solo game messages are visible to spectators, set idle timeouts, and clean up finished game messages automatically.

Music

Search and resolve tracks, import supported playlists, manage queues and favorites, control playback, apply audio filters, and restore eligible sessions after a restart.

Temporary voice

A creator channel produces temporary rooms whose owners can rename, limit, lock, unlock, permit, or reject members. Empty rooms are cleaned up automatically.

Command visibility

Leveling

Message and voice activity can grant XP through configurable cooldowns, exclusions, multipliers, and fast, balanced, long-term, or custom curves. Rank cards support a custom title, accent, optional background image, and public/private responses. Leaderboards, level-up announcements, reward roles, staff XP controls, and archived seasonal resets are available without enabling Economy.

Economy 2.0

Economy supports wallet and bank balances, daily and weekly rewards, work, search, crime, adventures, configurable fishing/farming/hunting activities, jobs and mastery, shops, inventory effects, quests, achievements, marketplace sales, auctions, pets, businesses, properties, simulated investments, and prestige. Profiles, quests, achievements, and history are under /economy progress; activities are under /economy activity.

Player interactions

Admins choose Peaceful, Opt-in PvP, or Open PvP. /economy pvp rob, /economy pvp heist, /economy pvp duel, and escrowed bounties use account-age checks, member-age checks, cooldowns, daily victim-loss limits, passive mode, transaction logs, and protection items.

Official templates

• Minimal Economy
• Balanced Community
• Peaceful Progression
• Competitive Economy
• Chaos Economy
• Roleplay Economy

Optional integration

Economy actions may grant capped XP, level-ups may grant currency, and jobs or items may require levels. Each connection is separately configurable, so either module still works by itself.

Applying templates

Detailed audit logs

Server logs identify the actor, target, reason, readable action, Discord audit entry, and before/after changes when available. Deleted resources use cached metadata where possible.

Separate routing

• Moderation actions to moderation logs.
• Message edits/deletes to message logs.
• Joins, leaves, profiles, verification, and roles to member logs.
• Channels, roles, permissions, webhooks, and settings to server logs.
• Plans, executions, backups, restores, and module events to platform logs.
• Modmail events only to Modmail logs.

Live status

The status panel edits one persistent embed with bot, web/API, database, queue, latency, uptime, last-check time, and current version. A stale timestamp still signals trouble when the bot cannot edit the message.

Included

• Supported channels and categories.
• Roles and supported permission data.
• Channel permission overwrites.
• Discord AutoMod rules.
• Supported ServoX module configuration and role-panel settings.

Not included

• Ordinary messages or deleted user content.
• Members, ownership, or Discord audit logs.
• Third-party bot databases.
• Unsupported integrations or settings.
• A guarantee that every deleted Discord object can be recreated identically.

Safety workflow

Medium/high-risk approval creates a safety backup. Owner-requested restore jobs create another pre-restore snapshot before changing Discord.

Supported connections

ServoX supports OpenAI, Anthropic, Google Gemini, Groq, OpenRouter, Ollama, and compatible OpenAI-style endpoints.

Credential handling

Keys are verified before save, encrypted at rest, masked in the dashboard, and never returned in full after storage.

Optional sharing

A server owner can share one provider with trusted managers without exposing its key. Personal default providers take priority, and owner-selected daily request limits can cap shared usage.

Common provider failures

• 400: unsupported request shape, context, or model option.
• 404: wrong model or endpoint.
• 429: provider rate limit or exhausted free capacity.
• Unreadable plan: the model returned text that could not be normalized into supported actions.

Core and moderation commands

Core commands are registered globally. Moderation actions are filtered by the authority policy configured for the server.

Optional module commands

Games (/games and /g), Economy (/economy and /e), Leveling (/level and /lvl), Verification (/verify), music, voice, invites, forms, giveaways/events, protection, moderation, and Auto Roles commands are synchronized per guild and disappear when their module or command toggle is disabled.

Independent configuration

Each module has its own enable state and stored configuration. Disabling Message Protection does not disable Server Protection, and disabling a member module removes only its related runtime and optional commands.

Validation

The dashboard validates selected channels and roles against the current guild. Deleted, managed, missing, or wrong-type resources are rejected instead of being saved silently.

Commands are missing

• Confirm the related module is enabled in the dashboard.
• Confirm optional commands are enabled when the module has a separate command toggle.
• Make sure your account has the role or Discord permission required to use the command.
• Allow Discord a few minutes to refresh the server command list, then reopen the slash-command menu.
• Use /help to see the features currently enabled in the server. If the command is still missing, contact a server administrator or the support server.

Dashboard settings will not save

• Read the validation message shown below the form.
• Check whether a selected channel or role was deleted, renamed, or changed to an unsupported type.
• Refresh the dashboard data and select the channel or role again.
• Hard-refresh the browser or sign out and back in if the dashboard is showing stale server data.
• If the request still fails, send the visible error and approximate time to the support server.

Discord actions fail

• Move the bot role above every role it needs to create, assign, remove, or edit.
• Confirm the bot and approving user have the required Discord permissions.
• Check whether the target channel, role, or setting changed after the plan was approved.
• Create a focused replacement plan for unfinished work instead of rerunning actions that already completed.

Status is degraded

• A brief degraded result can occur during maintenance or a service restart.
• Wait about a minute and run /status again.
• Check the live status channel for the most recent service update.
• A stale Last checked value means the bot may be unable to refresh the panel.
• If the degraded state persists, report it in the support server with a screenshot and timestamp.