Discord does not revert anything automatically when a bot leaves. Every channel, role, permission overwrite, and message the bot created stays exactly as-is — Discord owns that data, not the bot. To clean up before uninstalling, use the optional cleanup steps in the uninstall confirmation dialog (accessible from the server selector).

When the bot is re-invited, on_ready runs a full recovery sequence for every server it joins.

What happens depends on which channel was deleted and whether the bot is currently running.

Sources are external accounts the bot actively monitors. When new content is detected (video, tweet, email, game update, RSS post), a notification embed is delivered to the Discord channels mapped in Routing.

1. 1Go to Sources → click + Add Account
2. 2Select a platform and fill in the required identifier (Channel ID, App ID, username, or feed URL)
3. 3Save — the source card appears with a status indicator
4. 4Go to Routing and create a rule linking this source to a Discord channel. Without a routing rule, no notification is ever delivered.

Reddit embeds are kept up to date automatically. Every day at midnight the bot fetches the latest score and comment count for every Reddit post it delivered in the last 7 days and edits the Discord embed in-place. The last line of each embed (💬 X comments • ⬆️ Y) is replaced with the fresh values. Posts older than 7 days are dropped from the update queue.

By default the bot delivers a Discord embed with title, 300-char description and a thumbnail URL. Each source can opt into Repost mode (Edit Source → Repost section) for richer delivery:

Trigger search fields: any subset of Title, Body, Tags / flair / hashtags. Empty keywords + empty patterns = always match. If a downloaded file exceeds Discord's 25 MB upload limit, the bot silently falls back to the standard embed for that post. YouTube (videos too large) and Twitch (live streams) cannot upload their primary media — the dashboard warns when these modes are picked for those platforms.

Discord channels eligible to receive source notifications. A channel must exist here and have a matching Routing rule to receive any messages.

1. 1Go to Channels → Notification tab → click + Add Channel
2. 2Pick a Discord channel from the dropdown (fetched live from your server)
3. 3Toggle the channel ON to activate it, then create a Routing rule

Channels auto-created in a New Member category. New members can only access these channels until they pick a role via Role Gate. This is also where the welcome message is sent.

When a member posts in #anonymous or runs /anon, the bot deletes their original message and reposts it with a 💬 Anonymous header. The member's real identity is never shown in public — only visible in #anonymous-log (System channel) for moderation. This is by design.

Hidden management channels auto-created under a MAMA NUI System category. Only the configured Admin Role can see this category.

Set via System tab → Admin Role dropdown. Only members with this role can see the MAMA NUI System category. Without an Admin Role set, the category is visible only to server administrators (Manage Server permission).

Routing rules are the bridge between a Source and a Discord channel. Without a routing rule, no notification is ever delivered — there is no default fallback. Each rule maps one source to one or more notification channels.

1. 1Add a source on the Sources page (e.g. a YouTube channel)
2. 2Add a Discord channel on Channels → Notification tab and toggle it ON
3. 3Go to Routing → click + Add Rule
4. 4Select the source and the target channel(s) → Save
5. 5Ensure the rule toggle is ON to activate delivery

Each routing rule has a Send Latest Post button. Clicking it fetches the most recent item from that source and delivers it immediately to the mapped channel(s) — identical to an automatic notification, including any configured ping role. The item is also marked as seen so the bot will not re-post it on the next check.

Define server rules as sections (header + content). The bot posts them to the #rules channel. The #rules channel must be enabled in Channels → New Member tab.

An embed message sent automatically when a new member joins the server. Supports two placeholders: {user} mentions the new member, {server} inserts the server name.

Word and phrase rules that trigger automatic moderation actions when a member's message matches.

Customizes the modal fields shown when a member runs /submit. Up to 5 fields, each with a label, placeholder, and optional required toggle. Completed submissions are posted to #submissions (must be enabled in Channels → System tab).

Rate-limits message sending in specific channels. Certain roles can be exempt so moderators are never throttled.

Notification Roles let members self-subscribe to @mention pings for specific content types (e.g. coupons, game updates). Members click a button in Discord to opt in or out — no commands needed.

In Settings → Default Messages, each platform (YouTube, Steam, Twitter, etc.) has its own ping roles list. Every notification from that platform automatically @mentions the configured roles — no trigger word needed.

All three tabs (Button Roles, Role Gate, Notification Roles) post to #roles-picker and store a message_id to track the live Discord message. The behavior differs per tab in edge cases.

Slash commands available in Discord. Built-in commands cover bot status and moderation. Custom commands let you define your own keyword triggers.

Override the default Discord permission with a specific role requirement. If set, only members with that role can run the command, regardless of their native Discord permissions.

Create your own slash commands with a custom name and a bot response (plain text or embed). Useful for FAQs, server info, or pinned announcements triggered on demand.

Two log streams — Bot activity and Dashboard changes — displayed in a real-time viewer with level filters and date navigation.

Records every configuration change made through the dashboard (who changed what and when). Kept forever — never rotated or deleted.

Bot logs rotate daily. The date picker shows up to the last 7 days of history. Logs older than 7 days are automatically deleted. "Today" always points to the current live log file.

Community profile cards for your server members. Each member registers a profile with stats, collection info, and a customizable Armory — rendered as a Pillow-generated PNG card. Achievements are auto-assigned based on activity milestones.

Right-click any member → Apps → View Profile Card — delivers their card as an ephemeral message visible only to you.

If a commands channel is set in Card → Settings, all /card commands only work in that channel. Members attempting to use them elsewhere get a silent ephemeral error.

Browse all registered member profiles for the selected server. The count is shown next to the tab label.

Runs the achievement evaluation logic across every profile in the server. Useful after adding new achievement definitions or changing thresholds — auto-assigns the best earned badge to each empty slot without waiting for the daily loop.

Define the achievement badges members can earn. Each achievement has a condition type and a threshold value. Achievements are evaluated on profile save, on the daily midnight loop, and when "↻ Re-check All" is triggered.

Each profile has 6 badge slots mapped to these condition categories: server_booster · logins · streak · stars · collection · undecided. When multiple achievements qualify for the same slot, the one with the highest threshold value is used.

Customize the fields shown in the template members fill in during /card register and /card edit. Toggle individual fields off to hide them from the template.

Sets the denominator for the collection progress bar on the profile card. For example, if Taimanin max is 42, a member with 20 shows 20/42. Used for display only — does not gate registration.

Toggle individual /card sub-commands on or off globally. Disabled commands return an error to members — useful for temporarily locking registration while migrating data.

Every midnight (server local time) the bot increments total_logins +1 and login_streak +1 for every registered profile. If a full day was missed (the last loop ran more than ~24 h ago), the streak resets to 1.

After incrementing stats, the daily loop re-evaluates all achievement conditions for every profile and auto-assigns newly earned badges — same logic as "↻ Re-check All" in the dashboard.

An escrow system that runs entirely inside Discord. Any server member initiates a trade by calling /mm_rmt, selects the buyer, seller, and middleman, and the bot creates a private thread for all three parties. The bot DMs the buyer with payment instructions and the seller requesting their bank details. All confirmation flow happens through buttons inside the thread.

The middleman provides static bank/e-wallet details or a static QRIS image URL. Payment transfer and fund forwarding are done manually by the middleman.

1. Bot DMs buyer with the middleman's bank account or QRIS.
2. Bot DMs seller asking for their bank/e-wallet receiving details.
3. Buyer transfers money to middleman, then clicks Payment Sent to Middleman.
4. Middleman verifies receipt, then clicks Forward Payment to Seller.
5. Seller receives funds, then clicks Payment Received from Middleman.
6. All three parties click Close Transaction → thread archived.

1 hour. If the buyer does not confirm payment before expiry, the transaction is marked expired and the thread is archived automatically.

The middleman configures a Xendit or Flip API key (per middleman, not shared). The bot generates a dynamic QRIS or Virtual Account and sends it to the buyer. Webhook callbacks auto-detect payment receipt.

1. Bot generates QRIS/VA via API and DMs the buyer.
2. Bot DMs seller asking for their bank/e-wallet receiving details.
3. Xendit/Flip webhook fires → bot auto-announces payment confirmed in thread.
4. Buyer and Middleman both click Forward Payment to Seller to release funds.
5. Bot calls the disbursement API automatically if amount < configured threshold. Otherwise, admin clicks Disburse in dashboard.
6. Seller + buyer click Transaction Complete → thread archived.

24 hours from transaction creation.

Configurable per middleman. Transactions below the threshold are disbursed automatically via API. Those at or above the threshold are flagged pending_disbursement and require admin approval in the Transactions tab.

Select which channels allow /mm_rmt. Leave empty to allow the command everywhere.

Copy these URLs into your Xendit or Flip dashboard as the callback/webhook URL. Requires WEBHOOK_BASE_URL to be set in .env.

Add any server member as a middleman. Per-middleman settings:

View all escrow transactions for the selected server. Filter by status. Click any row to see full detail (bank info, confirmation flags, disbursement ID).

Appears on pending_disbursement rows. For automatic mode, calls the Xendit/Flip disbursement API using the seller's bank details captured via DM. For manual mode, simply marks the transaction as disbursed (admin did it physically).

Click Resolve on a disputed transaction. Choose Refund Buyer (cancels transaction) or Pay Seller (moves to pending_disbursement for manual disburse). Does not move funds automatically — admin must handle the actual transfer for refunds.

Discord-native support ticket system. Each ticket is a private text channel under a "Tickets" category, visible only to the opener, configured support roles, and the bot. Configured in the Ticketing dashboard page — no JSON editing required.

Member clicks Open Ticket → modal asks for a subject → bot creates a private channel → welcome embed + Close Ticket and Claim buttons posted. Support roles are pinged in the same message (configurable).

Full transcript (no limit). Posted to the log channel as a code block (≤1900 chars) or a .txt file. Close embed includes: subject, opener, closer, claimer, message count, open time, and optional reason.

Set auto_close_hours > 0. The bot checks every 30 minutes using Discord snowflake timestamps (no extra API calls). At hours − 1, it warns the opener; at hours it closes automatically.

Post a plain-text message to any Discord channel on a schedule. The bot checks every 60 seconds for due schedules across all guilds.

Each schedule stores a last_run timestamp. Daily and weekly schedules will not fire more than once per calendar day, regardless of bot restarts.