Documentation

Emerald connects community activity, role rewards, moderation and games. Use Discord commands for member actions and the website for server configuration. You can enable each feature independently; start with one, test it, then add more.

Set up your server

1. Invite Emerald.

   Use Add to Discord on the home page. Choose a server you are authorized to manage and review the permissions.

2. Open your dashboard.

   Sign in with Discord and choose your server. An installed server opens its settings; a dimmed card opens the bot invitation.

3. Set General preferences.

   Choose the server timezone, prefixes, permitted prefix-command channels and moderator roles. Check the Free or Premium status displayed here.

4. Enable one system.

   For example, open Welcome, select a text channel, write a greeting and save. Check that Emerald can view and send messages in that channel.

5. Test as a member.

   Use a normal member account or ask a member to try the feature. Administrator permissions can hide channel-access problems.

Where to go next

Read Dashboard access before granting staff permissions, then Saving and synchronization before changing reward rules. The command directory links each command to its relevant chapter.

Server owners and administrators can manage their server dashboard. Administrators can appoint Dashboard Manager Roles in General. Manage Server by itself does not grant website access. The bot owner can access server dashboards for operation and support.

Give staff the access they need

1. Open General as a server administrator.
2. Choose Dashboard Manager Roles, or configure module grants for more specific access.
3. Select read-only or view-and-edit access where supported, then save.
4. Ask the staff member to sign in using the correct Discord account.

Read-only access allows inspection; the server also checks permissions before accepting a write. Existing manager roles without scoped grants retain broad dashboard access. Global administration belongs to the separate operator portal.

Discord role hierarchy still applies

Emerald needs Manage Roles and a highest role above every role it assigns or edits. Managed booster/integration roles can be observed as conditions, but cannot be assigned by the bot. A selected role may become unavailable after deletion or a hierarchy change.

Audit and troubleshooting

General includes dashboard audit logs showing the acting account, time and action for the last 30 days. If a server is missing, check your account, live membership, Administrator permission and appointed roles. If a role action fails, check both the manager’s permissions and Emerald’s hierarchy.

Changes to ordinary settings stay in the current page’s draft until you choose Save changes. The save bar counts pending sections. Discard restores the last captured values and brings back removals that were only staged.

A predictable editing flow

1. Open a role or channel selector. Search by name or ID; role names use their Discord color.
2. Choose the required items. Optional selectors allow None or clearing the selection.
3. Add or edit list rows where the feature provides a builder.
4. Choose Save changes and wait for the result before leaving.
5. Run Sync if the feature needs existing members or channels to be reconciled.

Enabling, posting, deleting and other immediate actions may have their own button or confirmation. A success message means that action was accepted or saved. Background jobs show their own progress and can finish with errors even after configuration was saved.

Lists and interruptions

Paginated records use Previous, Next and Go to page controls while preserving filters. Sync changes to Cancel sync during a scan; cancellation keeps completed Discord changes. The dashboard retains failed drafts in the open page, but reloading or closing the tab can lose them. A timed-out save may have completed on the server: inspect the saved result before trying again.

Text, voice and reaction XP can be enabled independently. Activity statistics and XP are different: message counts may be recorded even when a member earns no XP because of a filter or cooldown. Reaction XP contributes to the text activity totals shown to members.

Configure leveling

1. Enable the activity types you want.
2. Review channel and role filters independently. A blacklist excludes selected items; a whitelist permits only selected items. An empty whitelist permits no XP.
3. Add text and voice reward thresholds. Choose stacking if members should keep multiple eligible rewards.
4. Configure announcements, DMs, the rank-card background URL and opacity.
5. Save, then synchronize level rewards to check existing members.

Premium permits custom XP ranges, cooldowns, voice eligibility, maximum level and formula settings. The dashboard shows which controls the current plan permits. Role and channel multipliers change awards where their conditions apply.

Announcements and safeguards

Use the variable picker for member, level, XP and rank fields. Premium level-up images are optional and begin disabled. XP safeguards can reject normalized repeated messages, self-reactions and duplicate reaction awards, and can enforce a configured daily cap. Check /level, /day_track and /history when diagnosing unexpected progress.

Members use /invite to create a personal invite. Emerald compares available invite information when members join. Original invites represent recorded first joins; active invitees count invited members who are still present. These are different measures and can produce different reward totals.

Set up invite rewards

1. Choose the invite reward mode and optional starting date.
2. Add roles and their thresholds, then choose stacking behavior.
3. Save the rules and run invite reward synchronization.
4. For Premium, configure the weekly Invite MVP and its destination.

Rejoining eligible members are checked for reward roles when they are not jailed. Sync scans pause for actual Discord role changes rather than every member. A scan may report individual failures when a role is deleted, too high or unavailable.

Check the evidence

/invites, /inviter, /invitees and /invite_leaderboard expose different parts of the record. The website’s recorded-join list supports a From date and pagination. Vanity links, deleted invites, unavailable permissions or simultaneous joins can make attribution uncertain; a missing record is not proof that a member never invited anyone.

/profile combines member activity and available profile controls. Profiles show lifetime totals, current weekly/monthly totals and the most recent 30 days of daily activity. Daily voice figures use minutes. Achievement categories group unlocked tiers and completion details.

Read a leaderboard

1. Select Text or Voice.
2. Choose lifetime, weekly or monthly activity.
3. Use the shared page controls to move through results or jump directly to a page.
4. Open a member’s profile to inspect the underlying activity.

Lifetime levels describe accumulated progress; a weekly XP ranking describes activity during a period. A member can therefore have a high lifetime level and a low weekly position. Current-member filtering can also change which records appear.

Premium tracking

Ping, emoji and sticker tracking have their own enable switches and period filters. Repeated direct mentions of the same user in one message count once, and self-mentions do not count. Emoji/sticker rankings reflect the supported items recorded by the tracking feature.

Use /pingstats user-stats, /pingstats leaderboard, /emoji stats and /emoji leaderboard in Discord. Tracking reset tools clear the selected statistics for the server; review the confirmation before proceeding.

Custom roles let eligible members choose a personal role name, color and supported icon. Configure a trigger role, an anchor role and an optional log channel in Custom Roles. Emerald places personal roles beneath the chosen anchor, subject to its own hierarchy and Discord permissions.

Configure and test

1. Select the eligibility trigger and anchor.
2. Check the current plan’s custom-role limit and edit cooldown.
3. Save, then grant the trigger to a test member.
4. Have the member open the newest DM create panel.

Regaining the trigger or running /customrole sendpanel replaces a pending creation panel. Old panels and their open forms become inactive. The command requires the permissions enforced by Discord and the bot; members cannot use it to bypass eligibility.

Member actions

Use /customrole edit to edit an owned role after its cooldown and /customrole delete to delete it. A restore panel can reuse saved appearance only when a saved record exists. A member receiving a shared role through Custom Role Plus does not become its owner and cannot edit it as if they owned it.

Name filtering applies where configured. The dashboard’s custom-role list shows the owner and role appearance, offers color details and lets authorized managers delete a role. Deletion is a live action; it does not wait for a later reward sync.

Custom Role Plus is separate from basic custom-role eligibility. An owner needs both their own custom role and the configured Plus trigger role. Set the Plus trigger and Friend Change Cooldown in Custom Role settings.

How an invitation works

1. The owner runs /customrole friend in the server.
2. They choose an eligible server member.
3. The friend receives a private confirmation with a five-minute expiry.
4. After acceptance and a successful role assignment, the friend-change cooldown begins.

A pending or declined invitation reserves the selection until expiry. If the DM fails, the owner can choose another member immediately. Free servers permit a 3–7 day configured cooldown; Premium permits 1–28 days. The actual value comes from your server settings.

Eligibility and one-owner linking

A member can be linked to only one owner per server. Pending invitations reserve that member until the five-minute deadline. Jailed members and members who own an active custom role cannot accept. Having a trigger, pending creation panel or saved appearance alone does not count as owning a role. These checks run again when the invitation is accepted.

Manage a linked friend

The friend panel remains available during the change cooldown. Remove Friend opens a private confirmation with Confirm Removal and Cancel buttons. Sharing is cleared only after the owner confirms; cancellation or expiry leaves the link unchanged. The original friend-change cooldown is preserved. A departing friend is marked Left and remains linked; rejoining restores the shared role only while the same link, owner eligibility and recipient eligibility remain valid. Removing, leaving, recreating a role or changing settings cannot shorten an already running friend-change cooldown.

Ownership and persistence

Sharing grants membership in the role, not editing ownership. Invitations, assignments and cooldowns survive restarts. Losing Plus access suspends sharing and locks the command; regaining it restores a valid unchanged friendship. Deleting the owner’s custom role by any route clears the friendship and pending invitations while retaining the cooldown. A friend who creates or restores an owned custom role loses the incoming shared link without resetting the original owner’s cooldown. Edit, deletion, confirmation and unlink logs include the affected friend.

Timed Roles observes whether a member continuously has or lacks a source role for a chosen number of days. Once the duration is met, Emerald assigns the target role. When the condition stops being true, Emerald removes the target managed by the rule and resets its observation.

Build a timed rule

1. Choose a source role, including a managed booster/integration role if needed.
2. Choose Have or Does not have.
3. Enter the duration and an assignable target role.
4. Select Add to stage the row, then Save changes.

The table shows the source, condition, duration, target and actions. Edit permits changes to the condition, target and duration. To change an existing source role, remove the rule and add another. Changing the condition resets the timer; duration/target edits retain relevant continuous observation and queue reconciliation.

Jail and role synchronization

Jailed members are skipped by level, invite, server-tag, connection, timed-role and other automatic role reconciliation. Timed-role timestamps stay saved and time continues to elapse. After release, Emerald verifies current eligibility before reconciling roles and deferred cleanup. Temporary jail stripping does not reset timed-role observations or permanently delete a custom role.

Observation and restarts

Timers begin when Emerald observes the condition; past role history is not reconstructed. Timers persist in MySQL. A role removed and restored entirely during downtime cannot be inferred from Discord’s current state.

/temprole instead grants a role for a fixed duration and can extend/reset a timer. Its optional persist setting controls rejoin behavior and defaults to false. It is useful for temporary access independent of a continuously held source role.

A Role Connection manages one main role according to conditions. AND requires every condition; OR requires at least one. Emerald assigns the main role when the rule matches and removes it when the rule stops matching, subject to paused rules, permissions and hierarchy.

Create a connection

1. Choose the main role.
2. Add condition roles and choose has or does not have.
3. Choose AND or OR and review the explanation.
4. Save, then run the connection sync to reconcile existing members.

Premium activity conditions

Premium adds text/voice levels, messages, voice minutes, recorded invites and active-day thresholds. Supported activity conditions can use lifetime, the last seven days or the last 30 server dates. Mix activity and role conditions and choose at-least or at-most where offered.

Gateway role updates and periodic reconciliation work together. Activity changes may be applied during a periodic scan rather than immediately after each message. On Premium expiry, unsupported activity rules pause and preserve roles instead of silently interpreting a different rule.

Review and repair

Connection cards show the main role first. Expand a card to inspect conditions. Deleted roles, circular dependencies, role hierarchy and plan caps can pause a rule; correct the reported problem and synchronize again. Cancellation keeps role changes already completed.

Welcome messages can send channel greetings or member DMs, within the current server plan’s message-slot limit. Free normally has one message across the available targets; Premium normally has two. The Premium comparison shows the operator’s current limits.

Write a welcome

1. Choose a channel or DM target.
2. Write text, a rich embed, or both using the available fields.
3. Use Insert Variable for member names, server details, join information and supported invite information.
4. Review the preview, save and test delivery.

A preview uses sample data; the real member’s avatar, names and invite information can differ. Avatar and image fields require direct public HTTPS image URLs. Channel delivery needs View Channel and Send Messages, plus Embed Links for embeds.

Mentions and unavailable DMs

Welcome delivery permits user, role, everyone and here mentions in message content, subject to Discord permissions and notification settings. Use those deliberately. A failed DM can reflect the recipient’s privacy settings or a block; it does not prove the saved template is invalid. Channel-specific permission overwrites can also prevent delivery even when Emerald has server-wide permissions.

Message Embedder supports text-only messages and rich embeds. A saved template is reusable content; a sent Discord message is a separate published result. Editing one does not necessarily update the other.

Compose and send

1. Build content and optional embed sections: title, description, author, media, footer and fields.
2. Review the Discord-style preview and character counters.
3. Choose a server channel or a webhook you control.
4. Save a named template for reuse, or send the current draft.

Content supports 2,000 characters. An embed supports a 256-character title, a 4,096-character description, up to 25 fields and 6,000 combined text characters. Image URLs must point to public HTTPS images. Webhook URLs contain credentials and must remain private.

Update an existing message

Supply the Discord message link where the editor requests it. Emerald can edit its own supported channel messages when it still has access. Webhook-sent messages cannot be updated through that channel-message editor.

Schedule delivery

Save a template, then create a once, daily or weekly schedule with a destination, timezone and first send time. Recurring schedules retain their chosen wall-clock time across daylight saving changes; nonexistent local occurrences are skipped. After downtime, an overdue occurrence may be delivered before the next future occurrence is calculated.

Cancel a schedule independently of its template. Uncertain delivery receipts are retained for review to avoid blindly sending duplicates. These messages permit all mention types in content, subject to Discord permissions.

Standard Giveaways has its own dashboard. Enable it, choose a channel, prize, host, winner count and end time, then configure eligibility and publish. Templates save reusable options. Flash Giveaways is a separate feature in Miscellaneous.

Define eligibility

Rules can include any/all required roles, blocked roles, bypass roles, Emerald text levels, calendar message counts, server boosting and bonus entry roles. Disabled or empty requirements are omitted from the giveaway message. Rejections identify the blocking role or show current progress against the requirement.

Fixed Entry

Fixed Entry is enabled by default and required on Free. With it enabled, accepted entries remain fixed under ordinary eligibility changes. When editing requirements, use Recheck Eligibility if offered to evaluate existing participants against the updated rules. Premium can disable Fixed Entry so relevant member role changes recheck entries and notify removed members.

Participation and management

Enter checks eligibility and records the entry. Clicking Enter again opens a private Leave giveaway control. Administrators and configured Giveaway Managers can inspect participants and remove selected entries; removed members receive a DM attempt. Managers can edit, cancel, end or reroll supported giveaways. Drops award the first eligible entries.

Winner selection

Free uses Default Random. Premium adds Shuffle Draw, Random Score Draw and Seeded Hash Draw for standard and flash giveaways. All methods respect the effective entry weights, select distinct members and exclude previous winners on rerolls. Standard giveaways keep their existing bonus-entry rules; Flash gives each eligible participant one entry. Seeded Hash Draw retains its seed, candidate weights and result for replay. Choose the method before the giveaway starts; started events keep it through rerolls and Premium expiry. Templates save the selection. First-come drops retain their original behavior.

Premium controls

Premium adds supported reaction entries, custom emoji, account/membership age, server tags, confirmation DMs, schedules/repeats, duplication, temporary winner roles, claim deadlines and thread controls. Check the categorized comparison for current caps. /giveaway_reroll replaces selected current winners. Claiming acknowledges a win; the host remains responsible for delivering the prize.

Flash Giveaways

Enable Flash Giveaways in Miscellaneous and configure its entry, blacklist and logging roles as needed. Authorized staff use /flash to prepare an event. Flash runs independently of the standard giveaway editor and keeps its own running state and history.

Members with at least 150 recorded messages on the current server date can be auto-entered by the Flash system. Eligibility still follows the feature’s supported rules. Server-tag checks use recorded equipped time where configured; a newly equipped tag does not immediately satisfy a six-hour rule.

Set up suggestions

1. Enable Suggestions in Miscellaneous.
2. Choose the destination and moderator role; set the cooldown.
3. Save the settings to post the persistent panel in the destination channel. Select each submission type on the panel to test it. Use Post / refresh panel to update or repair it.

General suggestions require multiline text and accept up to four optional screenshots. Emoji/Sticker suggestions require a name and exactly one square image. Supported static uploads become PNG; animated uploads become GIF.

Suggestions post with the submitting member’s display name/avatar through the feature’s reusable webhook. Vote counts appear in the buttons. Accepting or rejecting records the moderator and status, disables voting and removes the decision controls. Votes and decisions survive restarts. Suggestion text and attachments are public in the selected destination; use an appropriate channel.

Birthdays are optional and server-scoped. Emerald asks only for day and month, not a birth year. Open your own /profile and use Configure Birthday to submit a date for that server.

Member controls

A member submits the date once. It cannot then be edited directly. Only a server administrator can remove a member’s submission through /profile; after removal, the member can submit a new date. The private panel can hide or show the date on profiles.

Server configuration

1. Open Birthdays in Miscellaneous.
2. Choose the wishing channel and birthday role independently. Either may be None.
3. Check the timezone in General, then save.

At local midnight, Emerald combines the day’s birthday members in one wish. The temporary role expires at the next local midnight, including daylight saving days. Roles members already held are preserved. February 29 is celebrated in leap years. Very large groups may require a configured birthday role so a single mention fits Discord’s message limit.

Removing a date affects future participation; it does not retract wishes already published in Discord. Resetting the module’s staff configuration preserves submitted dates.

Temporary Voice has its own dashboard. Members join a creator voice channel to receive an owned room. The current plan limits the number of setups; both plans share the supported room customization tools.

Create a setup

1. Add a creator channel and choose the room category or fallback categories.
2. Set the room name, user limit, bitrate, region, privacy and permission inheritance.
3. Review owner controls and any role restrictions in Permissions and Moderation.
4. Configure the shared interface and optional greeting, companion chat, waiting room or temporary member role.
5. Save, enable and leave/rejoin the creator to test.

Emerald needs the relevant View Channel, Manage Channels, Move Members and permission-management access. A setup check reports missing permissions. Discord administrators retain their platform-level access.

Room controls

Authorized room owners can rename, lock/show, set limits, trust or block members, transfer ownership and use the other controls enabled by the setup. Trust admits a waiting member. Claim succeeds only when the owner is absent. Deleting a room requires confirmation and disconnects its members; linked companion channels are also removed.

Votes and persistence

Vote kick is optional. It requires at least two eligible votes and protects owners, administrators and bots. Only eligible members present at the start can vote. Saved owner preferences and vote state support restart recovery. Empty rooms are cleaned up after the configured delay. Pausing creation stops new rooms; cleanup of existing rooms continues. Jailed members cannot create rooms or receive access grants.

Starboard highlights eligible messages when a configured reaction reaches the server’s threshold. Open Starboard in Miscellaneous, choose a destination, set the reaction and threshold, and select source channels where the feature should listen.

Prepare the channels

1. Allow Emerald to view the source messages and read their history.
2. Allow it to send messages and display supported media in the destination.
3. Save, then react to a test message in an allowed source channel.

The published highlight keeps a link to the original message and the author. A stored snapshot supports later updates. Moderation/dismissal and message deletion can affect what is republished.

When a highlight is missing

Check that the feature is enabled, the original channel is included, the reaction matches and the threshold is met. Confirm source and destination permissions separately. Reactions on inaccessible or deleted messages cannot always be recovered. Avoid choosing a destination whose audience should not see the source message’s content.

Jail

Set the jail role, authorized staff roles and log destination. Create Jail Role can make a dedicated role; saving or synchronizing applies the feature’s channel restrictions. Review View Channel, Send Messages, Add Reactions and Read Message History overwrites.

/jail add-user requires a reason and supports durations from one minute to 28 days. Notify User defaults to enabled. Active punishments survive rejoins and keep their expiry. Emerald attempts to remove other roles after the relevant rejoin/screening flow, skipping roles Discord does not allow it to remove.

Use the remove-user, user-details and view subcommands to release or inspect records. Premium expiry does not automatically release existing jailed members. New records can be blocked while the active total is over the current cap.

Name filtering

Miscellaneous contains comma-separated blocked words and supported Discord AutoMod selections. The shared filter checks custom-role creation, editing and restoration; suggestions and emoji/sticker suggestion names; confessions; voice-channel names and temporary room statuses; AFK statuses and messages for AFK members; Intel Imposter clue submissions; Rogue Roulette table chat; every option in a random choice; profile ID submissions; and Flash Giveaway items and notes. Blocked submissions are rejected before saving or posting, while voice names use the configured replacement character. Flash content is checked again when published.

Admins can bypass word filters is off by default. Enable it to let the server owner and members with Discord's Administrator permission bypass Emerald's submission checks. Manage Server, Dashboard Manager roles and bot-owner status alone do not grant this bypass. Discord's own AutoMod enforcement is separate. Select the rules deliberately, save and test a harmless matching example. A name filter supplements server moderation; it is not a guarantee that every abusive expression will be recognized.

Staff responsibility

Discord channel overwrites, administrator permissions, hierarchy and integration-managed roles still apply. Review logs and setup checks when an action partially succeeds. Do not repeatedly issue the same destructive action while a job is still running.

AFK

/afk set starts an AFK session with a message; /afk clear clears it. Clearing someone else’s status requires the relevant staff permission. Server settings control ignored channels, blocked roles, ignored mention roles and supported automatic clear/delete timers.

AFK notices use the configured mention behavior for the replied-to message or user. The current AFK list can open the saved text in a dialog. Timer limits depend on the server plan and are shown in the dashboard.

Confessions

Configure the confession destination, moderation access, cooldown, optional discussion threads, thread slowmode and automatic locking. Use the posted feature interface to submit rather than placing private information in a public support request.

Confessions are not anonymous to every possible party. Feature records and authorized moderation/audit access can connect a submission to an account. The configured channel’s members can see the published content, and Discord may retain messages independently of Emerald.

Report or remove content

Contact server staff for a moderation decision and the Emerald operator for a privacy request. Removing a database record does not necessarily remove a Discord message, an attachment copy or a screenshot someone already saved. Never submit passwords, access tokens or sensitive personal information in either feature.

The UID registry stores member-provided identifiers in categories configured by server staff. Categories are server-scoped and can represent supported games or other identifier types. A saved identifier is information supplied by a member; it is not automatically proof of account ownership.

Configure categories

1. Open UID settings and create a category with its supported format.
2. Review the current plan’s category limit.
3. Save and use the member interface to test submission and display.

On a downgrade, existing categories and entries are preserved, while adding categories may be blocked until the total is below the active cap.

Supported external lookups

/uid bgmi and /uid coc require Premium and query supported game information. The BGMI command can process multiple identifiers with progress. External services can be unavailable, rate-limited or return changed player names. A lookup result describes the service response at the time it was requested.

Review the destination and feature visibility before submitting. To correct or remove saved records, use the available management interface or ask authorized server staff. Questions about an external game account itself belong with that game’s operator.

Each counting channel is configured independently on the website. Choose Whole Numbers, Binary, Roman, Alphabets or Mathematics Expression. The preview explains the next sequence before you save.

Set up counting

1. Select a channel and number system.
2. For an expression, enter the supported expression and review its preview.
3. Check View Channel, Send Messages, Read Message History, Manage Messages and Manage Webhooks.
4. Save, then test with two members taking turns.

Incorrect values and consecutive counts from the same member are deleted. Accepted values are reposted by the feature’s webhook with the member’s name/avatar. Alphabet input is case-insensitive; reposted letters use uppercase.

Reset choices

Reset count keeps scores. Reset count and leaderboard clears both. Removing a configured channel clears its settings and scores. Changing the number system retains the current sequence position, so review the next expected value after an edit.

/counting_leaderboard shows a channel’s rankings, next count and last correct counter. Channel limits differ by plan. If counting appears inactive, check webhook permission and whether the selected system expects a different representation of the next value.

Enable games

Open Miscellaneous → Games, select Roulette, Imposter and/or Tic Tac Toe, then save changes. Each checkbox controls that game's availability independently. New servers start with games disabled unless the bot owner has changed the default policy. Bot-wide maintenance or a global game pause can temporarily override a saved selection.

Imposter

/imposter creates a Classic or Intel lobby for 3–12 players. Follow the private word/clue instructions and the public game interface. The separate Imposter rules page explains modes and the round flow in detail.

Tic Tac Toe

/tictactoe opens an interactive two-player board inside Discord. Use the game’s join and turn controls; only the appropriate participants can make moves.

Rogue Roulette

/rogueroulette launches a shared Discord Activity from a server voice channel. Remember shell information, use items and follow turn notices. Fast, Medium and Slow modes show notices for five, six and seven seconds respectively. Read the game guide before your first match.

Staff recovery

A member with Manage Server can run /endgame in the affected channel to close the current game or lobby. This is available as a recovery action even when normal game features are paused. All game commands are server-only.

Activity availability can depend on the Discord client, voice-channel access and launch configuration. If an Activity fails to open, confirm those prerequisites and report the visible error. In-game rewards or giveaway prizes are governed by the host’s published rules, not an automatic promise from Emerald.

General sets the server timezone for supported date-based features. Daily activity follows local calendar dates. Weekly periods begin on Monday at local midnight; monthly periods begin on the first day. Changing timezone does not rewrite dates already stored.

History versus totals

Detailed XP history retains the last 14 days. Daily activity records can remain for lifetime totals and active-day achievements. Profile tables show the latest 30 days; that display window is not a promise that older rows are deleted.

Persistent operations

Supported role timers, jail records, custom-role sharing, giveaways, votes and message schedules store state for restart recovery. Recovery still depends on the database being available and Emerald retaining Discord access. Events that occurred entirely while the bot was offline may not be reconstructable.

Backups and resets

Authorized operators can back up supported databases. A configuration export covers supported settings, not every member record or every external Discord message. Read a reset action’s description: disabling a feature, resetting configuration and deleting member data are different operations.

For data categories, visibility, retention and request routes, read the Privacy Policy. Removing Emerald from a server does not automatically erase every stored row.

General holds the server plan, timezone, prefixes, staff roles and access settings. Dedicated feature pages handle Levels, Invites, Custom Roles, Role Connections, Timed Roles, Message Embedder, Giveaways, Temporary Voice, Counting, UID and other available tools.

Miscellaneous

Miscellaneous groups Server Tag Role, Birthdays, Confessions, Starboard, Suggestions, Flash Giveaways, Name Filtering and Games. Temporary Voice has a separate page. Each available module has its own controls; a reset may preserve submissions or history even when it clears configuration.

Free and Premium

Premium belongs to a server, not to every server a member uses. The Premium comparison groups features and reads the current configured plan limits. The server’s actual entitlement appears in General.

On expiry, Free caps apply. Some over-limit or Premium-only automation can pause. Existing jail punishments are preserved, existing UID categories are retained and unsupported Role Connection activity rules pause rather than releasing roles. Review the affected feature instead of assuming all modules react identically.

Member versus manager actions

The command directory separates member-facing actions from staff tools and dashboard configuration. Discord can further restrict a command through server integration settings. A button being visible does not override its server-side permission check.

Server error history

Activity and Error Logs lists server errors for 14 days, with occurrence times in the server timezone. Select a reason to see the feature, attempted action, available user and resource details, missing permissions and a suggested repair. Deleted-resource and role-hierarchy checks also report skipped automation. Feature status is in Configuration; rank-card previews are under the background URL and opacity in Levels.

Start with a small check

1. Run /ping for response, gateway and MySQL latency.
2. Confirm the feature is enabled and the server plan supports it.
3. Review Activity and Error Logs checks and the visible error.
4. Test once in a permitted channel with a normal member.

Visit the support server for help. Use the operator contact in the Privacy Policy for personal data requests, and server staff for local moderation decisions.