From many bots Über YourBot

Open the dashboard, pick your server, and go to the Plugins page. Toggle any plugin on or off — the change takes effect immediately, no bot restart needed. Built-in plugins are free; marketplace plugins may require an entitlement before they're available to enable.

Go to /account and click Open billing portal. The Stripe portal lets you cancel any active plan. Cancellation takes effect at the end of the current billing period; you keep access until then. No refunds for partial periods.

Open the Discord Developer Portal, click New Application and give it a name and avatar. On the Bot tab, enable the Presence, Server Members and Message Content intents; YourBot needs all three for full plugin coverage. Copy the bot token (you'll only see it once) and paste it into the Custom Bot section at /bot. Done. Your custom bot is now managed by the YourBot platform.

A YourBot subscription is billed per bot. Each subscription covers one custom bot assigned to one server, and you can hold multiple subscriptions to cover multiple servers. Current pricing is on the Pricing page. Built-in plugins are free in every mode; marketplace plugins are billed by their developer per their own pricing.

Analytics tracks message activity, voice time, member joins/leaves, role rewards, and cohort retention for your server. It powers leaderboards, trend charts, and per-channel drill-downs in the dashboard at /p/analytics/. Counts and timestamps are stored — message content is not.

First check /status. If the platform is degraded you'll see it there. Otherwise open /bot. For a custom bot, check the connection status and click Restart if it shows Crashed. For the shared bot, the most common cause is a Discord permission change; re-invite the bot from /servers to refresh its access.

Stored: message metadata (timestamps, channel IDs, author IDs — used for analytics counts), member join/leave events, voice-session timestamps, plugin config you save, audit log of admin actions, and billing data. Not stored: message content (unless a plugin explicitly captures it for a feature you enabled — like ticket transcripts, where it's scoped to the ticket channel and tagged with retention). Each tenant's data is isolated by discord_srv_id at the database level.

Go to /dev and click New Plugin. You'll be asked for an id (lowercase, underscore-separated, becomes the URL slug), a display name and a description. After creation the plugin starts in draft state: you upload an artifact (zip) and the static scanner runs over it. Once you submit a version for review, our team checks it and either publishes or flags it back to you with notes.

Every submitted version lands in our review queue before going live. We check static-scan findings (no obvious malware or secret stealing), manifest accuracy (capabilities match usage) and the version delta since the last published version. Most reviews complete within 1-3 business days. You'll get a dashboard notification when reviewed.

Open /dev/earnings and click Connect with Stripe. You'll go through Stripe Connect onboarding (business details, ID verification, bank account). Once verified, every paid install of your plugin credits earnings to your developer balance and pays out to your Stripe account automatically. The platform fee is displayed on the earnings page; the rest is yours.

Default: 30 outbound HTTP requests per minute per plugin per server, enforced by a token bucket with a short burst allowance. If your plugin has a legitimate need for more, contact us through the dev portal or the support server and staff can raise the limit for your plugin within sane bounds.

Open /plugins, click the marketplace plugin's row and hit Uninstall. The plugin stops within a minute. Plugin data is retained for 7 days in case you reinstall (config intact). After 7 days the plugin's data is deleted. Paid plugin subscriptions are managed from the plugin's marketplace page or /account/licenses; cancel there to stop charges.

Open /bot and find the Custom Bot section. Paste the token from the Discord Developer Portal and save. Tokens are encrypted at rest and never displayed back in plaintext. If a token leaks, regenerate it in the Discord Developer Portal and paste the new one in the same place; your bot restarts with it automatically.

On a failed payment Stripe retries automatically for about two weeks. During retries your bot stays online. If the subscription cancels, your custom bot is stopped gracefully and the server falls back to the shared bot automatically. All plugin config, analytics, tickets and data are retained while the bot stays in your server. Re-subscribe and your custom bot comes back exactly where it left off.

From /plugins, toggle Analytics on. Data starts collecting immediately for new messages and voice sessions. Historical Discord activity (before the toggle) can be back-filled by running the Discord history import from the Analytics dashboard's settings tab.

Discord caches slash commands per-guild for up to an hour. If you toggled a plugin recently, wait; they'll appear automatically since the platform re-syncs commands itself. If commands look duplicated or stale, members can press Ctrl+R in the Discord client to reload its command cache. Still wrong after an hour? Open a support ticket with your server ID.

Current retention windows: audit logs are kept 2 years, then purged nightly. Analytics events, ticket transcripts and plugin data are kept while the bot is in your server. If the bot leaves or is kicked, all server data is retained for 30 days and then permanently deleted. Billing and invoice records are kept as long as legally required. Support-quality logs of FAQ questions are purged after 180 days.

The metadata dict in your plugin.py requires id (lowercase, underscore-separated), name and version. A description is strongly recommended. You can declare capabilities_required, slash_commands and proxy_domains_requested, but any capability your code actually uses is auto-detected and added on artifact upload, so a missing declaration never causes a runtime error. The declared-vs-detected diff is shown on the version page. See the plugin development docs.

AST and pattern based detection of: dynamic code execution (eval, exec, compile), foreign function interfaces (ctypes, cffi), raw network access that bypasses the proxy capability, code generation and obfuscation, anti-debug indicators and hard-coded secrets (tokens, API keys, private keys, high-entropy strings). Manifest cross-ref: every capability you use must be declared (auto-added if missing) and every domain you call must be listed in proxy_domains_requested. Findings are weighted by severity; high-severity findings send the version to human review.

Payouts are automatic. Earnings from a sale are held for about 30 days to cover the refund window, then settle to your connected Stripe account on Stripe's standard payout schedule. Refunds are deducted from your balance before payout. See your live balance and history at /dev/earnings.

Each marketplace plugin runs in a locked-down Docker container: 64MB RAM hard cap, 0.25 CPU core, --network none (HTTP only via the proxy capability), read-only filesystem with a 16MB /tmp scratch space, a non-root user, all kernel capabilities dropped and a strict process limit. Exceeding the memory cap terminates the container and it restarts automatically with backoff.

Open the plugin's marketplace page or /account/licenses and click Request Refund. You'll be asked for a brief reason. The request goes to the plugin's developer first; if they don't resolve it within 7 days our team steps in. Approved refunds are returned via Stripe to your original payment method. Subscription plugins can also be cancelled any time, with access continuing until the period ends.

The default invite requests Administrator so every plugin works out of the box without permission debugging. Prefer a tighter setup? You can remove Administrator after inviting and grant only what your enabled plugins need (for example Manage Channels for Voice Channels and Tickets, Manage Roles for Welcome auto-roles, Send Messages and Embed Links wherever the bot posts). Each plugin's page flags missing permissions rather than failing silently. Discord privileged intents are configured at the bot level; you don't need to enable anything in your server settings.

The shared bot is best when you want zero setup and don't care about the bot's identity. It's free and ready to go. A custom bot is best when you want your own name, avatar and presence, branded for your community. Custom bots require a YourBot subscription; the shared bot is free. Feature parity is identical: every plugin works on both.

Most servers leave defaults. The knobs that matter: Excluded channels and roles (skip bot or staff channels from counts), Exclude bots (bot messages are excluded by default; switch to Include Bots if you want them) and Role reward triggers (auto-grant a role when a member crosses an activity threshold). All on the Analytics settings page.

The toggle bouncing means the plugin failed validation on enable. Check the toast/error banner at the top of /plugins — common causes: (1) marketplace plugin without an active entitlement, (2) plugin requires a capability your tier doesn't grant, (3) plugin migration failed (rare; surfaces as a server-side error). Open the browser console for the exact error or contact support with the plugin name + your server ID.

Data deletion is handled by our team. Reach us in the support server or through the contact details on the Legal page and we'll remove your account, OAuth tokens, any custom bot tokens and personal audit-log entries within 30 days. Server-scoped data (analytics, tickets, audit logs that don't reference you personally) remains under the server owner's control.

On artifact upload, the static scanner walks your code and detects capability usage (e.g. proxy.request() implies proxy:http; kv.set() implies storage:kv). Detected capabilities are unioned with whatever you declared and saved as the effective set. This means you can't accidentally ship a version that fails at runtime because you forgot to list a capability. The diff (what you declared vs what was detected) is shown on the version page.

Open the version page — you'll see the scanner's findings list with severity per finding. Common reasons: (1) you used a capability without declaring it (auto-derived now, but pre-fix versions still flag); (2) a regex matched something that looks like a hard-coded secret (often a false positive in tests/fixtures — add a comment explaining and resubmit); (3) the artifact references a domain not in proxy_domains_requested. Fix and resubmit; review usually clears within a day.

Customers request refunds from the plugin's marketplace page. Requests go to you first: you have 7 days to approve or decline, after which our team steps in. Approved refunds are deducted from your developer balance automatically. Subscription plugins can also be cancelled any time (access continues until period end). Patterns of refund abuse lead to customer-side restrictions and patterns of poor plugin quality can lead to suspension.

KV (kv.get/set/delete) — small key-value items, low-latency, scoped to (plugin, server). Best for config-like data, short flags, deduplication tokens. SQL (sql.execute) — full Postgres queries inside a per-plugin schema, scoped to (plugin, server). Best for structured data with indexes/joins. Both are isolated per tenant — you can never read another server's data. Capability names: storage:kv and storage:sql.

Stripe retries failed payments automatically over about two weeks. During retries your subscription stays active and your bot and plugins keep working. Stripe emails you at each retry. If all retries fail, the subscription cancels: your custom bot is stopped gracefully and the server falls back to the shared bot with all data and config retained. Update your payment method any time via Open billing portal on /account.

If a plugin is suspended (security finding, policy violation, developer abandonment), it's frozen: existing installs keep running on the last known-good version but no new installs and no auto-updates. You'll get a dashboard notification with the reason. If the suspension is for security reasons, the plugin may be force-disabled server-side instead; in that case contact us for a refund and we'll handle it case by case.

Click Log in with Discord on any page, or go straight to /login. You'll be sent through Discord OAuth; approve the basic profile and guilds scope and you're in. We never see your Discord password. OAuth only gives us your user ID, username, avatar and the list of servers you can manage.

On the Bot page, use the Bot Mode selector. Switching from shared to custom requires an active YourBot subscription and a saved custom bot token. Switching from custom to shared stops your custom bot, removes it from the server and the shared bot takes over. Plugin config, audit logs and member data all stay intact; only the bot identity changes.

Analytics requires no extra Discord permissions beyond the default invite — it observes events the bot already receives. It does need the Server Members intent to track joins/leaves (enabled at the bot level, not per-server).

Three causes, most common first: (1) the bot doesn't have Manage Channels at the category level (server-level isn't enough — Discord enforces category overrides); (2) the category is at Discord's 50-channel cap — delete some old temp channels; (3) the lobby channel was moved out of the configured category. The Voice JTC settings page surfaces all three with red status pills.

Audit logs are visible to anyone with the owner or admin role in the dashboard for that server. Other roles see scoped subsets. Each plugin also has its own scoped audit log on the plugin page (e.g. ticket actions, sentinel cases). Platform staff access is limited to support and abuse handling, and every staff action is itself audit-logged.

Yes. On a plugin's settings page under GitHub Integration, link a public repo URL (or a private one plus a fine-grained PAT with read access). Pushes to your configured branch (main by default) trigger an automatic version draft: the artifact is fetched, scanned and queued for your review, or auto-published from public repos if you're a trusted dev. You can also click Pull from GitHub to fetch the latest state on demand.

Each install has an auto-update preference, on by default. When you publish a new version, installs with auto-update on switch over shortly after publication. Installs with it off stay pinned until the server owner manually upgrades from the plugin's marketplace page. Versions that request new capabilities or proxy domains always require the server owner to re-approve before updating, regardless of the preference. Updates never downgrade an install.

On a plugin's settings page, open the Plans tab. You can offer free, one-time purchase (single payment for permanent install) or subscription (monthly or annual recurring) plans. Pricing is set in USD and Stripe handles currency conversion. Servers pick a plan at install time and can switch plans later; switches prorate automatically.

Open your plugin's Logs page from the dev portal (/dev, pick the plugin, then Logs). You'll see structured log and crash events from the sandbox including stack traces. Common crashes: (1) missing capability (the SDK raises CapabilityError; capabilities are auto-declared on your next upload), (2) memory limit exceeded (the sandbox cap is 64MB), (3) unhandled exception in an event handler. The runner auto-restarts the container after crashes with exponential backoff.

Open /account and click Open billing portal. The Stripe portal lists every invoice with PDF downloads and handles payment method, billing address and tax ID changes. Stripe also emails each invoice automatically when payment succeeds; check the address Stripe has on file if you're not receiving them.

Open /marketplace. Browse by category (moderation, fun, utility, integrations, etc.), price (free / one-time / subscription), or rating. Each plugin page shows the developer, description, screenshots, capabilities required, version history, and reviews. Click Install on server and pick which of your servers to install it to — the plugin is configured per-server from there.

Go to /servers and click the server you want to manage. From that point on, every plugin page (Plugins, Access, Logs, etc.) operates against that server until you switch. You can switch any time by reopening the server picker — your selection is stored in your session, not globally, so two browser tabs can manage two different servers in parallel.

/bot shows the live status: Running, Stopped or Crashed. Behind the scenes the orchestrator restarts crashed custom bots automatically with exponential backoff. The /status page shows platform-wide health. If your bot keeps showing Crashed, check that its token is still valid and its intents are enabled in the Discord Developer Portal.

Three common causes: (1) the Excluded channels list includes channels you didn't realize were excluded; check the settings tab. (2) Bot messages are excluded by default; flip Exclude bots off if you want them counted. (3) Historical messages from before the plugin was enabled are not retroactive unless you run the Discord history import from the settings tab.

Discord only lets a bot assign roles below its own role in the role list. Open Server Settings → Roles, drag the bot's role above any role it needs to manage (welcome auto-roles, sentinel timeout-replacement roles, ticket staff-team roles), and save. Re-run the action — the error should clear. The relevant plugin pages flag mis-ordered roles in red.

A self-service export isn't available yet. Contact us in the support server and we'll compile your server's data (analytics, audit logs, plugin config, ticket transcripts) for you. Ticket configuration can also be exported directly from the Tickets dashboard.

On the plugin's GitHub Integration page, choose Private repository. Generate a fine-grained Personal Access Token scoped only to the plugin's repository with Contents: read permission. Paste the PAT; it's encrypted at rest and never displayed back. Test the link by clicking Pull from GitHub. If a version draft appears, you're done.

Trusted dev status is granted manually by our team to developers with a clean track record. Trusted devs' versions from public GitHub repos can skip the review queue and publish directly. The static scanner still runs and high-severity findings still route to human review. Trusted-dev status can be revoked for any policy violation.

On a plugin's version page, click Install on my server — this is a dev install, free, only available to the plugin's owner(s), and only on servers you manage. You can iterate on the artifact, re-upload, and the dev install auto-refreshes. Dev installs don't appear on the public marketplace, can't be installed by other servers, and skip the review queue. Switch to a published version when you're ready to ship.

Each YourBot subscription covers one custom bot assigned to one server. To run custom bots on several servers, hold one subscription per server; you can buy as many as you need and assign each to a server from /account/byo. Marketplace plugins are licensed per server per their developer's pricing.

Developers can offer multiple plans for a single plugin (e.g. free with limited features, paid for advanced ones). You can switch plans any time from the plugin's marketplace page. Switching prorates: Stripe credits the unused portion of the current plan toward the new one.

Every plugin has its own page under /p/<plugin>/ — for example, the Tickets plugin lives at /p/tickets/, Sentinel moderation at /p/sentinel/, Voice Channels at /p/voice_jtc/, and so on. The main Plugins page is the on/off toggle list — once a plugin is enabled, its dedicated page is where the real config happens. The sidebar surfaces enabled plugins after toggling.

Yes. Open /bot and click Restart. The orchestrator stops the running process, waits for a clean exit and brings up a fresh instance with the latest config and plugin set. Restarts usually complete in seconds. Plugin state, queues and member data are unaffected; restart is safe to run any time.

Announcements lets you schedule one-off and recurring messages (daily, weekly, monthly) to any channel. Timezone-aware with graceful catch-up if the bot was offline at the scheduled fire time. Manage via /p/announcements/ or the /announce slash commands.

YourBot uses the Message Content intent for sentinel automod, analytics keyword tracking and ticket transcripts. Without the intent enabled at the bot application level, those features fall back to event-only detection (joins, reactions) and silently skip content-based rules. For the shared bot, this is already enabled. For a custom bot, enable it in the Discord Developer Portal under your app's Bot tab.

Draft — you uploaded an artifact (or GitHub fetched it). Static scan runs. You can preview, edit metadata, and test-install on your own server (dev-installs are free). Submitted — you click Submit for Review. Our team checks the scan + manifest. Published — version goes live on the marketplace; existing installs auto-update if they opted in. Flagged — submission was rejected with notes; address and resubmit. Trusted devs skip the review step and go draft → published directly.

The bot joins your server and registers its slash commands (takes up to an hour for Discord to propagate). You're auto-granted the owner role inside the dashboard, plugin config defaults are seeded, and you're handed the server picker. Nothing is enabled yet — no welcome messages, no moderation, no surprises. You opt into each plugin from the Plugins page when you're ready.

Yes. Open /account/byo, unassign the subscription from its current server and assign it to the new one (you need Manage Server on the target). Your custom bot leaves the old server and joins the new one with the new server's config. Old-server data stays in place in case you move back. There's no charge for moving.

Toggle on from /plugins. Click New Announcement in the plugin dashboard, pick a channel, write the message (markdown + embeds supported), and set the schedule. Or use /announce now channel:#general message:... for a quick fire-and-forget post.

Discord rate-limits bots per-guild and per-route. YourBot's action queue smooths this automatically — bursts pause instead of failing. If you're seeing user-facing rate-limit messages, you've usually triggered a plugin loop (e.g. an automod rule that fires on its own warn message). Check the plugin's audit log; raise the rule's cooldown; add bot/staff exclusions to the rule.

Every YourBot subscription includes the full feature set for one custom bot on one server, so there are no feature tiers to downgrade between. If you no longer need a subscription, cancel it via Open billing portal on /account. It stays active until the end of the billing period, then the server falls back to the shared bot with all data retained.

Recurrence is configured per announcement. Choices: once (fire at a specific datetime), daily (HH:MM each day), weekly (HH:MM on selected weekdays) or monthly (HH:MM on a specific day-of-month, 1-28). Each announcement also has its own timezone (UTC by default).

Nothing is lost. Re-invite the bot from /servers (your server still appears as a managed server). All plugin config, audit logs, analytics, tickets, and member data remain in place. Once the bot rejoins, slash commands re-register within an hour and every plugin resumes exactly where it left off. Re-invite within 30 days to keep all data; after that, idle servers are scheduled for cleanup.

Capability: discord:send_message. The bot needs Send Messages in the target channel, plus Embed Links if the announcement uses embeds. The plugin will skip and log a warning if either permission is missing rather than crashing.

Weekly schedules use ISO weekday numbering: 0 = Monday, 6 = Sunday. If you picked the wrong index, the announcement fires on the wrong day. Also check the announcement's timezone: schedules are stored against the timezone set on that announcement (UTC by default), and the dashboard shows a next-fire preview.

Beacon schedules guild events (raids, guild nights, PvP sessions) with class/spec slot signups, waitlists, recurring events, polls, reputation tracking, rich embeds, and auto-reminders. Manage at /p/beacon/ or use /beacon create, /beacon list, /beacon cancel.

Toggle on from /plugins. Pick an announcement channel in the Beacon settings (where event embeds get posted), then run /beacon create from any channel — a modal walks you through name, time, role slots, and reminder timing.

Common settings: Announcement channel (where embeds post), Reminder lead time (default 30 min before event), Default role slots (Tank/Healer/DPS/Flex counts), Allow waitlist (when slots fill), and Reputation tracking (mark no-shows; track reliability over time).

Capability: discord:send_message. The bot needs Send Messages + Embed Links in the announcement channel and any channel where event embeds get posted. No special role permissions required.

Signup uses buttons on the event embed. If members can't sign up, check that the bot still has Send Messages and Embed Links in the announcement channel and that the event hasn't been cancelled or already started. If the embed was deleted, repost the event from the Beacon dashboard. When a role's slots are full, new signups go to the waitlist instead.

Giveaway runs random-winner giveaways with weighted entries, prize tiers, requirement gates (account age, server tenure, required/excluded roles, message count), auto-end scheduling, reroll and a public animated spectator page at /g/<public_id> for live drawings. Manage at /p/giveaway/.

Toggle on from /plugins. Run /giveaway create for a quick start, or open /p/giveaway/ for the full editor (requirement gates, weighted entries, prize tiers, public page settings).

Common knobs: Required roles / excluded roles, Account age minimum (anti-alt), Server tenure minimum, Booster multiplier (Nitro boosters get N× entries), Per-role multipliers, Prize tiers (top 3 get prize A, next 5 get prize B), and Dedup window (block farming across multiple giveaways).

Capability: discord:send_message. Plus Add Reactions + Manage Messages in the giveaway channel for reaction-entry giveaways. Button-entry giveaways need only Send Messages + Embed Links.

Two common causes: (1) the requirement gates filtered out every entrant — check the eligibility audit on the giveaway detail page; (2) the bot lost permission to post in the giveaway channel between create and end. Check the audit log on the detail page; you can manually re-trigger the draw with /giveaway end <id> once permissions are restored.

Group Finder is instant LFG (Looking For Group) for MMO/gaming servers — role-based slots, activity presets, difficulty tags, cross-server discovery, and a dashboard hub at /p/group_finder/. Members run /group create, /group quick, /group browse, /group join.

Toggle on from /plugins, then visit /p/group_finder/templates to configure activity presets (e.g. "Mythic+ Dungeon", "Ranked LFG", "Raid Night"). Members can immediately start creating groups via /group create or the in-dashboard wizard.

Common settings: Templates (activity presets — name, default role slots, difficulty tags, expected duration), Cross-server discovery (allow your groups to appear on the public LFG board at /p/group_finder/board), Saved alerts (members get pinged when matching groups open up), and Auto-close stale groups (close after N hours with no activity).

Capability: discord:send_message. The bot needs Send Messages + Embed Links in the channel where group listings get posted. No special role/channel-management permissions are required.

Cross-server discovery is opt-in per server. Open the Group Finder settings page and enable Allow listings on the public LFG board. Once on, your groups appear at /p/group_finder/board and can be joined by members of any server with the plugin enabled. Channel posts remain server-local.

Sentinel is the moderation control center: an automod engine with 15 conditions (mass mentions, link filters, message rate, caps, duplicate messages, phishing links and more), warning points, rule templates, mod insights dashboard, auto-setup wizard, raid protection and full case management. Manage at /p/sentinel/.

Toggle on from /plugins. Click Auto-Setup in the Sentinel dashboard for one-click sane defaults (block obvious spam, warn on caps, raid-mode on join floods). For fine-tuned rules, open the Rules tab and add conditions + actions individually.

Per-rule knobs: Conditions (any of 15 types: mass mention threshold, link domain allow/block, message rate and more), Actions (delete message, warn, timeout, kick, ban), Warn points (cumulative; configurable thresholds trigger escalation), Excluded roles/channels and Cooldowns to prevent action storms.

Capability: discord:send_message. Sentinel also needs Manage Messages (delete spam), Moderate Members (timeout), Kick Members, and Ban Members depending on which actions you've enabled. Missing permissions are flagged on the Sentinel dashboard with a fix button.

Check the Insights and Reports tabs: they show which rules fired, who triggered them and what action ran over your selected time window. False positives almost always come from too-aggressive thresholds (e.g. caps-lock at 30%) or missing role exclusions (e.g. moderators triggering link-spam rules). Add the offending role to the rule's Excluded roles or raise the threshold.

Social posts new content to Discord when feeds you subscribe to publish: Twitch live alerts, YouTube uploads, RSS and Reddit feeds, Steam news, GitHub releases and patch notes for games like League of Legends, Valorant, Apex, Fortnite, Minecraft, Guild Wars 2 and FFXIV. A curated game catalog gives one-click setup. Manage at /p/social/.

Toggle on from /plugins, then click New Subscription in the plugin dashboard. Pick a source type (Twitch, YouTube, RSS, etc.), enter the channel/URL/feed, pick the Discord channel to post to, and (optionally) add a role-ping. Polling starts on save; new items post within a few minutes of publication.

Per-subscription: Source type, Source ref (Twitch username / YouTube channel ID / RSS URL / Steam app ID), Target channel, Role ping (optional), Filters (e.g. RSS title regex, YouTube duration min). Polling interval is platform-managed (~5 min for most sources).

Capability: discord:send_message. Embed Links required for rich previews; Mention Everyone if you want to ping a role with @everyone permissions (rare; most use a subscriber role instead).

Two common causes: (1) the streamer toggled their stream as unlisted or private — Twitch's API hides those from polling; (2) Twitch's webhook had a brief outage. Polling catches up within ~5 min normally. If it's been longer, check the subscription's last poll timestamp on the settings page — if it's stale, the channel name is likely misspelled.

Tickets is a full Discord-native support operations system: panels, intake forms, staff teams, SLA policies, private channels/threads, claim workflows, internal notes, transcripts, CSAT surveys, analytics and audit logs. Members open tickets from a panel button; staff work them in the dashboard at /p/tickets/ and with the /ticket commands.

Toggle on from /plugins. Build your first panel at /p/tickets/panels: pick a category for ticket channels, an intake form and a staff team. Use /tickets panel to post the panel embed in a public channel; members click the button to open a ticket.

Per-panel: Category (where ticket channels are created), Channel template (ticket-{user} etc.), Intake form (custom fields), Staff team (who's notified + can claim), SLA policy (time-to-first-response targets), Auto-close after inactivity, and CSAT survey on close.

Capabilities: discord:send_message, discord:manage_channels. The bot needs Manage Channels (creates per-ticket channels), Manage Permissions (locks tickets to staff + opener), Send Messages, and Embed Links. Missing perms are flagged on the Tickets dashboard.

Almost always permissions on the ticket category. The bot needs Manage Channels in the category, not just at the server level — Discord enforces category-level overrides. Check the category's permissions tab and grant Manage Channels + Manage Permissions to the bot's role.

Voice JTC automatically creates a personal voice channel when a member joins a designated lobby voice channel, and deletes it when they leave. Members get private temp channels without staff overhead. Configure at /p/voice_jtc/.

Toggle on from /plugins, then visit /p/voice_jtc/. Pick (or auto-create) a Lobby channel + Category for spawned channels. Save. Tell your members to join the lobby — a personalized voice channel spawns instantly.

Settings: Lobby channel, Category for spawned channels, Name template (default 🎧 {display_name}), User limit, Bitrate, Delete when empty (default on) and Auto-create category/lobby (off by default; the dashboard can create them for you).

Capability: discord:manage_channels. The bot needs Manage Channels + Move Members in the category. Connect is optional — the bot doesn't actually join the voice channels, just creates/deletes them.

Three common causes: (1) the bot doesn't have Manage Channels at the category level — server-level isn't enough; (2) the category is at Discord's 50-channel cap; (3) the lobby channel was deleted or moved out of the configured category. The plugin dashboard surfaces all three with red status pills.

Welcome greets new members with custom messages, image cards, auto-roles, DMs, milestone celebrations (100th member, 1000th, etc.), welcome quests, first-message celebrations, server highlights, and smart channel recommendations. Manage at /p/welcome/.

Toggle on from /plugins, then run the auto-setup wizard at /p/welcome/setup for sensible defaults (welcome channel + a default message + a welcome card). For fine-tuned setup, open /p/welcome/settings and configure each subsystem individually.

Subsystems: Welcome message (markdown + variables like {user}, {server}, {member_count}), Goodbye message, Welcome card (image + name + member number), Auto-roles (grant on join), DM welcome (sent to the new member), Milestones (member-count announcements at 100, 250, 500, 1000 and up) and Welcome quest (gamified onboarding).

Capabilities: discord:send_message, discord:manage_roles. Manage Roles is needed for auto-roles. The bot's role must be above any role it's assigning — Discord enforces role hierarchy. The plugin shows a clear warning when this is misconfigured.

Discord's role hierarchy: the bot can only assign roles below its own in the role list. Open Server Settings → Roles, drag the bot's role above the auto-role, and save. The plugin's settings page shows the bot's current role position and flags any auto-roles that are above it with a red Above bot badge.