BotSupportHome

GORBOT SUPPORT

Commands, player help, characters, import/export, roleplay, server-owner setup, permissions, security, dashboard guidance, troubleshooting, and feature instructions in one place.

Choose a topic or scroll through the complete guide.

Start Here Player Guide Prefix Commands Slash Commands Characters Import & Export NPCs Roleplay Web Dashboard Server Owners Staff Commands Moderation Automation Permissions & Security Troubleshooting FAQ

About GorBot Contact Us

START HERE

The essentials for anyone using GorBot.

GorBot can be used through both Discord and the Web Dashboard.

For ordinary players, the quickest starting points are:

• use =help or /bothelp for help inside Discord;
• create a character, import an existing profile, or select one you already own;
• select the character you want as active before using active-character features;
• use =say <message> to speak as the active character;
• optionally configure a private Character Speaking Prefix such as [dyne on the character's Edit Character screen;
• use =profile to display the active character's populated profile in Discord;
• use the Character Library for full profile editing, import/export, public sharing, portraits, and active-character management;
• use the NPC Database for NPCs you own or eligible published NPCs you can browse;
• use Discord slash-command autocomplete to see currently enabled slash-command options.

GorBot also applies the server's current command-access rules. A server may designate a Blocked Command Role or Command-Silent Channels. These restrictions can prevent prefix and slash/application commands even when Discord still displays them in autocomplete. Buttons, select menus, onboarding controls, and reaction-role interactions remain available where configured.

The default GorBot message-command prefix used throughout this guide is:

=

A server owner can configure a different GorBot command prefix. If your server has done so, replace = in the command examples below with that server's configured prefix.

Character Speaking Prefixes are different. A speaking prefix belongs to one player's character and does not replace the server's GorBot command prefix.

↑ Back to Top

PLAYER GUIDE

The parts of GorBot most community members will use regularly.

Characters Create or import persistent roleplay identities, select an active character, maintain detailed profiles, configure an optional private speaking prefix, share public profiles, and speak through the character in Discord. See Characters & Profiles.

NPCs Create, browse, publish, share, or manage supported NPC identities according to the server's enabled features and your ownership rights. See NPC Database.

Web Dashboard Use larger forms and persistent pages for profile editing, Character Import/Export, NPC management, public share links, community tools, and other features that are cumbersome through commands alone.

Important: knowing the text of a staff command does not grant permission to use it. GorBot checks the Discord user, server authority, roles, ownership, and Discord permissions before protected actions are allowed.

↑ Back to Top

PLAYER PREFIX COMMAND REFERENCE

Examples below use GorBot's default prefix: =

Command	Who Uses It	What It Does
=help	Everyone	Opens GorBot's paged Discord help menu. This is the best live reference when a server has enabled or disabled command modules.
=Menu	Players	Opens the character-selection menu for your account.
=Menu 2 =Menu 3 ...	Players	Opens another page of the character-selection menu when your character list spans multiple pages.
=character management	Players	Alias for the character-selection/management menu.
=character management 2 ...	Players	Opens a later page of the character-management menu.
=1, =2, =3 ...	Players	Selects the numbered character shown in your current character menu. Use the number displayed by the menu rather than guessing a slot.
=characters	Players	Displays or enters the lightweight character/profile listing supported by the message-command system. Full profile management is available through the Character Library.
=name <name>	Players	Sets or updates the lightweight character name used by the message-profile system where that editing path is enabled.
=avatar <HTTPS image URL>	Players	Sets the lightweight character avatar URL where message-profile editing is enabled. Full image/profile management may also be available on the dashboard.
=about	Players	Opens or displays the lightweight profile/about information available through the message-command profile path.
=bio	Players	Displays the biography for your currently active character.
=bio <text>	Players	Replaces the active character biography with the supplied text. Biography length limits are enforced rather than silently truncating the text.
=say <message>	Players	Speaks through the currently selected character. GorBot posts the supplied text using the character identity through the roleplay webhook system.
=profile	Players	Displays the active character's populated profile. Large profiles continue across as many Discord embeds as needed instead of silently dropping populated fields. The portrait appears on the first embed, while biography/share information is placed at the end.

Extended player prefix-command families

Command Family	Current Uses
Profile fields	=title, =caste, =status, =homestone, =affiliation, =profession, =age, =height, =build, =haireyes, =distinction, =attire, =demeanor, =flaws, =gear, =weaponry, =currency, =hooks, =platform, =availability, =limits, =gender, =pronouns, =speech, and =tags. Use the command alone to inspect the field or supply a value to update the active character where permitted.
Inventory and currency	=inventory, =item <key>, =shop, =buy, =sell, =trash, =bal, =bank, =deposit, =withdraw, =give, =work, =daily, =weekly, =crime, and =timers manage the Discord roleplay economy—not the RunUO shard backpack or shard gold.
Scenes and relationships	=scene start, =scene join, =scene leave, =scene info, =scene end, =scene history, =scene archive, =relationship add, =relationship remove, and =relationships manage persistent roleplay scenes and character relationships.
Journal and lore	=journal add, =journal, =journal view, =journal delete, and =lore [search] maintain a character chronicle and search the server's curated lore/codex.
Events and contracts	=events, =event info, =rsvp, =contracts, =contract info, and =contract accept support scheduled gatherings, RSVP status, and roleplay quests/contracts.
Marketplace and trades	=market, =market sell, =market buy, =market cancel, =market history, plus =trade start, =trade item, =trade money, =trade status, =trade confirm, and =trade cancel. Direct exchanges complete only after both parties confirm and GorBot revalidates the offered property.
Equipment and progress	=equipment, =equip, =unequip, =achievements, =titles, and =reputation display or manage supported character equipment and progression.
Presence, LFRP, and rumors	=rpstatus, =who, =lfrp, =lfrp post, =lfrp close, =rumor, and =rumor submit advertise roleplay availability and interact with the moderated rumor system.
Dice and lightweight tools	=roll/=dice, =coin/=flip, =choose/=pick, and the =macro/=macros family provide tabletop rolls, random choices, and saved dice macros where enabled.

How =say behaves: GorBot should only remove the original =say command after the character webhook message is successfully posted. If the relay fails, the original message should remain so the player's roleplay text is not lost.

Character Speaking Prefixes are not GorBot commands. A player may optionally configure a private prefix such as [dyne for a specific character. GorBot checks the Discord author first and only uses that prefix when the matching owned character is active. Server command-prefix processing keeps priority.

↑ Back to Top

PLAYER SLASH COMMAND REFERENCE

Slash commands are discoverable through Discord's built-in autocomplete.

Slash-command availability can depend on the current GorBot release and which modules a server has enabled. Discord's autocomplete shows the subcommands currently registered on that server.

Command	What It Does
/bothelp	Opens GorBot's Discord help information.
/character register	Registers a new roleplay character when that subcommand is enabled. Character name is required; supported avatar/profile options can also be supplied.
/character edit	Edits a character you own using the currently available character fields.
/character switch	Changes your active character.
/character list	Lists characters associated with your Discord account.
/character delete	Deletes a character you own after the command's normal validation/confirmation rules.
/character say	Sends dialogue through your active character without requiring a visible =say command message.
/character profile	Displays the selected character profile, or the active character when no character is supplied.
/character setprofile	Updates a supported profile field for an owned character. Supply a field, value, and optionally a character; otherwise the active character is used.
/npc profile	Posts a published Global NPC Database profile selected through autocomplete or a serial/name lookup.
/npc list	Lists NPCs available to the current supported NPC interaction system.
/npc talk	Starts or enters a supported NPC conversation.
/npc end	Ends the user's active supported NPC conversation.
/talk	Starts or continues a supported conversational interaction using GorBot's current roleplay/conversation context.
/roles	Shows or uses the server's supported self-assignable role workflow.
/custom run	Runs a custom action that the server has specifically configured and exposed through GorBot.
/ticket close	Closes the current supported ticket when the user has authority to close it.
/poll create	Creates a poll using the supplied poll options.
/poll results	Displays results for a supported poll.
/poll end	Ends a supported poll when the user has authority to do so.
/poll list	Lists supported polls available to the user/server context.
/gornotify	Moves an eligible published server to the top of GorBot Server Discovery, subject to its current eligibility and cooldown rules.
Right-click → Apps → View Roleplay Characters	Opens GorBot's user-context character view for the selected Discord member where supported.
Message → Apps → Flag Conversation Oddity	Reports an unusual conversation response through GorBot's supported context-command feedback path.

Command Access Guard: Discord may continue displaying a slash command after GorBot has blocked its execution. If the member holds the configured Blocked Command Role or the command is used in a configured Command-Silent Channel, GorBot rejects the application command server-side. The Blocked Command Role takes priority even over Bot Commander and server-owner command authority.

↑ Back to Top

CHARACTERS & PROFILES

Persistent roleplay identities that belong to your Discord account.

The full character system is documented at Characters & Profiles.

A normal player workflow is:

1. create a character through the dashboard, import an existing profile, or use a supported /character command;
2. choose the profile style that fits the character;
3. fill in only the information you want to use;
4. add a portrait and up to 12 custom fields where desired;
5. optionally enable public profile sharing;
6. optionally configure a private Character Speaking Prefix;
7. select the character as active;
8. use =say <message>, /character say, or the character's configured speaking prefix for character speech.

A Discord account can maintain up to 150 characters. The full Character Library remains available for browsing and management even when a player owns many characters.

Active Character

Many roleplay actions use one selected active character.

On the Web Dashboard, the top-right active-character selector is intentionally compact. It shows up to the five most recently activated characters rather than trying to place as many as 150 characters into one dropdown. Use the Character Library when you need to activate a character that is not in that recent-five list.

Changing the active character also changes which private Character Speaking Prefix can respond for your account.

Profile Styles

GorBot currently provides 12 structured profile styles:

• Gorean;
• Standard RP;
• Fantasy RP;
• Tabletop D&D;
• Modern / Sci-Fi RP;
• Eryndor Drifter;
• Mad Tea Party;
• Supernatural;
• Tensei Slime;
• Furry;
• S&M / BDSM Safety;
• Custom / Freeform.

Gender and Pronouns are available across all profile styles. The Tabletop D&D sheet includes expanded identity, ability score, saving throw, skill, combat, proficiency, inventory, currency, feature, and spellcasting fields.

Profile values are stored by style so switching from one style to another does not intentionally erase the values previously entered for the other style.

Field-Specific Limits and Live Counters

Profile fields no longer share one broad generic text allowance. GorBot applies field-specific limits based on each field's purpose—for example, Age is intentionally short while Biography and other narrative fields can remain much longer.

Character and NPC editors show live character counters where supported. The same limits are enforced again by the server when saving, so bypassing the browser counter cannot store oversized data. If a save is rejected, shorten the named field rather than assuming GorBot silently truncated it.

Public Profile Sharing

Characters can be shared through a public profile link when sharing is enabled.

The Character Library provides supported share controls such as:

• Copy Share Link;
• Open Share Link.

New compact share links are supported, while existing legacy share links remain valid. Disabling sharing, rotating the share token, or deleting the character can invalidate the corresponding public link.

A public profile remains presentation-only. It does not transfer character ownership or edit authority.

Character Speaking Prefix

Edit Character includes an optional Character Speaking Prefix field.

Example:

[dyne Tal, traveler. What brings you to the city?

If Dyne is the message author's active character and Dyne owns the prefix [dyne, GorBot can relay the remaining message as Dyne.

Rules:

• the prefix belongs to that specific character;
• it works only for the Discord account that owns the character;
• it responds only while that character is active;
• the same player may store the same prefix on more than one character, but only the active character can respond;
• different Discord users may safely use the same prefix because GorBot checks the message author first;
• the field is optional; blank means no custom speaking prefix;
• prefixes are 2–24 characters and cannot contain whitespace/control characters;
• the server's normal GorBot command prefix is separate and keeps command priority;
• private speaking-prefix configuration is not displayed on the character's public shared profile.

The editor may allow you to configure the prefix while the character is inactive. It simply remains dormant until that character becomes active.

↑ Back to Top

CHARACTER IMPORT & EXPORT

Move profiles into GorBot without having to rebuild every field by hand.

The Character Library provides Import and Export JSON controls.

Supported import paths include:

• GorBot JSON — intended for the most complete GorBot-to-GorBot profile restore/copy workflow;
• Tupperbox JSON — recognizes the current Tupperbox export structure and maps useful roleplay profile values;
• Generic JSON — best-effort mapping for common profile field names;
• Raw Text — best-effort parsing of labeled profiles, headings, and common roleplay sheet formats.

Raw Text import can recognize common labels and can auto-detect supported profile families such as Gorean, D&D, Eryndor, Mad Tea Party, Supernatural, Tensei Slime, Furry, and S&M / BDSM Safety when the source text contains enough recognizable structure.

Always review the preview before saving an import.

Import intentionally uses a preview-first workflow because third-party and Raw Text profiles may use ambiguous labels.

Important protections include:

• imports create new character records rather than silently overwriting an existing character;
• duplicate-name warnings can be shown before creation;
• the source character owner identity is not reused;
• source public-share tokens are not reused;
• the character capacity limit is checked again before the import is committed;
• external avatar URLs must use supported HTTPS sources;
• a verified batch can create only a limited number of selected characters at once;
• native GorBot data preserves supported profile styles, profile/custom fields, proxy settings, privacy options, and Character Speaking Prefix data where present.

Operational third-party metadata that is not useful to the roleplay profile may be intentionally ignored.

Raw Text Tips

For the best mapping results, use clear labels such as:

Name: Dyne
Age: 27
Gender: Female
Pronouns: she/her
Species: Human
Personality: ...
Biography: ...

Formats such as Label: Value, Label = Value, labeled headings, and common Markdown-style headings are easier for the importer to interpret than an unlabeled wall of text.

Anything ambiguous should be reviewed and corrected in the preview before import.

↑ Back to Top

NPCs

Persistent non-player identities for recurring roleplay and shared world-building.

The full NPC management system is documented at NPC Database and NPCs & Shared Roleplay.

Depending on server configuration, ownership, and current capacity, users can:

• create and maintain NPC profiles;
• maintain NPC portraits and profile information;
• use the same expanded profile-style foundation available to characters where applicable;
• add up to 12 custom fields;
• clone owned NPCs;
• share supported public NPC profiles;
• publish eligible NPCs into the broader global NPC listing;
• browse/search eligible Published NPCs;
• use supported /npc commands for conversation-oriented NPC features.

A player's NPC collection can support up to 30 owned NPC records under the current NPC capacity model.

Sharing or publishing an NPC profile does not automatically give another user edit ownership. Draft/private NPCs are not part of the public/global published browser.

↑ Back to Top

ROLEPLAY THROUGH GORBOT

Use your selected character identity without changing your actual Discord account.

When you use character speech, GorBot can relay your message through a Discord webhook using the selected character's name and portrait.

Standard example:

=say Tal, traveler. What brings you to the city?

GorBot posts the supplied dialogue as the active character.

Your Discord account still remains the internal owner of that character. Character speech is fictional presentation; it does not make the webhook identity a separate Discord account.

Threads and forum posts: character speech can work inside supported threads when GorBot has the required channel and webhook permissions.

Tupper-style private Character Speaking Prefixes

Players who prefer a faster roleplay workflow can configure an optional prefix on each character's Edit Character screen.

Example account:

Dyne   → [dyne
Tarl   → [tarl
Marcus → [marcus

If Dyne is active:

[dyne Tal, traveler.

can relay the message as Dyne.

If the same player switches their active character to Tarl, [dyne becomes dormant and Tarl's configured prefix becomes eligible instead.

These prefixes are account-scoped, not globally reserved. Another Discord user can also configure [dyne for one of their own characters without causing a collision, because GorBot first identifies who sent the message and then checks that user's active character.

The server's normal GorBot command prefix remains separate. Character speaking prefixes do not take ownership of protected GorBot commands.

Large Discord Profiles

Using =profile with a heavily populated character can produce multiple embeds.

GorBot continues across additional profile messages as needed so populated fields are not silently lost. The character portrait is shown on the first embed only, and biography/public share information is placed at the end of the profile output.

↑ Back to Top

WEB DASHBOARD

Use the web interface when a command would be too small for the job.

The Web Dashboard uses Discord sign-in and applies the same ownership and server-authority rules as GorBot's other user-facing systems.

Players can use it for supported personal features such as:

• Character Library creation/editing;
• active-character selection;
• the recent-five active-character selector in the top-right dashboard area;
• Character Speaking Prefix configuration through Edit Character;
• Character Import and Export JSON;
• public Character share-link controls;
• NPC creation, ownership management, and eligible published NPC browsing;
• other personal/community tools exposed to their account.

Authorized server managers can use additional server-level pages for supported configuration, moderation, roles, automation, tracked content, and community features.

Current server-management additions include the Server Onboarder, Command Access Guard, Blocked Command Role, Command-Silent Channels, Permissions Doctor, Moderation Dashboard, Scheduled Operations, Global Audit Log, Server Health, configuration backup/restore/templates, welcome and goodbye controls, bot presentation, automations, polls, custom commands, timed messages, ticketing, reaction roles, social alerts, server statistics channels, and Server Discovery publishing controls where enabled.

Signing in identifies the Discord account. It does not automatically make the user a server administrator.

The dashboard also remembers supported view/position state within the browser session so returning to pages, tabs, forms, and the collapsible left menu can preserve context instead of repeatedly forcing the user back to the top of a long page or menu.

↑ Back to Top

SERVER OWNER GUIDE

The important things to understand before enabling every feature.

A server owner should begin with permissions and role hierarchy before troubleshooting individual commands.

Recommended Discord permissions depend on enabled features, but common GorBot requirements include:

• View Channels;
• Send Messages;
• Read Message History;
• Send Messages in Threads;
• Embed Links;
• Manage Webhooks for character speech;
• Manage Messages when message cleanup or command replacement requires it;
• Manage Roles only when GorBot is expected to manage roles;
• moderation permissions only when the corresponding moderation features are enabled.

Role hierarchy matters. GorBot's highest Discord role must be above any role it is expected to assign, remove, rename, recolor, or otherwise manage.

Avoid granting permissions GorBot does not need simply to make an error disappear. Use the permissions required by the features your community actually uses.

Suggested owner setup order

1. confirm GorBot is online;
2. confirm its role position;
3. confirm basic channel permissions;
4. test /bothelp;
5. test a player character;
6. test =say;
7. configure self-service/community roles where desired;
8. configure moderation roles;
9. configure automation only after its required roles/channels exist;
10. verify protected commands using an authorized staff account;
11. review the Web Dashboard for server-level configuration.

Server owners can also define trusted staff/Bot Commander authority for protected GorBot management without making every ordinary moderator a full server owner.

Command prefix vs. Character Speaking Prefix: the server owner controls the normal GorBot command prefix used for commands such as =help and =say. Individual players may separately configure private speaking prefixes on their own characters. Those player prefixes are account-scoped and active-character-only; they do not replace or globally reserve the server's GorBot command prefix.

Command Access Guard (2.7.1.0)

Feature Toggles includes two server-level command protections:

• Blocked Command Role — one configured role whose members cannot execute GorBot prefix commands or slash/application/context commands. This denial takes priority over moderator, Bot Commander, and server-owner command authority, preventing an accidentally assigned management role from bypassing onboarding restrictions.
• Command-Silent Channels — multiple configured channels where prefix and slash/application/context commands are unavailable to everyone.

Prefix-command denials are intentionally silent to keep onboarding areas quiet. Slash/application denials are ephemeral and explain why execution is unavailable. Discord may still visually list the slash commands. Buttons, select menus, onboarding components, ticket controls, and reaction-role interactions are intentionally outside the command denial gate.

Server Onboarder

The current onboarder can track pending members, an onboarding role, waiting time, access progression, ticket/channel state, completion, and configured automatic enforcement. Completion from role removal requires GorBot to have actually observed the role present and then absent; a role that was never seen does not falsely complete onboarding.

If an automatic kick succeeds but ticket cleanup cannot complete, GorBot retains the ticket reference and marks cleanup pending instead of losing the remaining cleanup state. Unresolved onboarding tracking defaults to a 1,000-row safety cap per server and can be configured from 100–5,000; finalized history remains bounded by the current retention policy.

↑ Back to Top

PROTECTED STAFF COMMAND REFERENCE

These commands are protected by GorBot authority checks. Knowing the command does not grant access.

Examples use the default prefix =. Protected commands are intended for the server owner, Bot Commander, or authorized moderation roles as appropriate to the command.

Command	Typical Authority	What It Does
=adminhelp	Owner / Bot Commander	Displays the protected administrative command help available to the authorized user.
=botadmin	Owner / Bot Commander	Opens or enters GorBot's protected Discord-side bot/server management command workflow.
=warn <member> [reason]	Authorized staff	Adds a warning to the target member, optionally recording the reason.
=warnings <member>	Authorized staff	Displays the warning history/state available for the target member.
=kick <member> [reason]	Authorized staff	Removes the target member from the Discord server. The member may rejoin unless another restriction prevents it.
=ban <member> [reason]	Authorized staff	Bans the target member from the Discord server when GorBot and the moderator both have the required authority.
=timeout <member> <duration> [reason]	Authorized staff	Applies a Discord timeout for the requested supported duration.
=untimeout <member>	Authorized staff	Removes a supported active timeout from the target member.
=npcadmin list	Owner / Bot Commander	Lists NPC-control entries available to the protected NPC administration command family.
=npcadmin place ...	Owner / Bot Commander	Places/configures a supported managed NPC presence when the relevant NPC feature is enabled.
=npcadmin inspect ...	Owner / Bot Commander	Displays protected information about the selected managed NPC/control target.
=npcadmin pause ...	Owner / Bot Commander	Pauses the selected supported managed NPC behavior.
=npcadmin resume ...	Owner / Bot Commander	Resumes a previously paused supported managed NPC behavior.
=npcadmin remove ...	Owner / Bot Commander	Removes the selected supported managed NPC placement/control entry.
=npcadmin clearscene ...	Owner / Bot Commander	Clears the supported NPC scene/control state targeted by the command.

Owner / Bot Commander utility commands

Command	Purpose
=addmod <role> =delmod <role> =listmods	Adds/removes server-specific moderator roles or lists the currently configured moderator roles.
=prefix [new prefix]	With no argument, shows the server prefix. With an argument, changes it to 1–8 non-whitespace characters.
=modules =module <name> =command <name>	Lists module state or toggles one supported module/individual command. Modules include utilities, moderation, automod, custom commands, roleplay, Living NPC, giveaways, tickets, timers, automations, and polls.
=ignorechannel <channel> =ignoreuser <user> =ignorerole <role> =ignored	Toggles ordinary command ignoring for a channel, user, or role and lists current ignored targets. This older ignore system exempts moderators/managers; use the newer Blocked Command Role or Command-Silent Channels when denial must also cover elevated authority.
=addrole <name> [color] [hoist] =delrole <role>	Creates or deletes a Discord role when GorBot has Manage Roles and sufficient hierarchy.
=rolecolor <role> <color> =rolename <role> <name> =mentionable <role> <on|off>	Changes the selected role's color, name, or mentionable state.
=nick [nickname] =setnick <user> <nickname>	Changes GorBot's server nickname or an eligible member's nickname.
=role add|remove <user> <role> =role all|humans|bots +|-<role>	Adds/removes a role for one member or performs the supported bulk role operation for all members, humans, or bots. Use bulk operations cautiously.
=purge [count] =purge <mode> [criterion] [count]	Immediately deletes matching messages from the current channel. See the detailed purge guide directly below.
=announce [everyone|here|role <role>] <channel> <message>	Sends a protected announcement, optionally mentioning everyone, here, or one resolved role.
=customs list =customs show <name> =customs enable|disable <name>	Reviews and enables/disables configured custom commands.
=giveaway create <channel> <winners> <duration> <name> =giveaway end <message> =giveaway reroll <message> [winner]	Creates, ends, or rerolls a reaction-based giveaway. Durations accept forms such as 30m, 2h, and 3d.
=addemote <name> <HTTPS image URL>	Adds a server emoji from a validated HTTPS image up to Discord's supported 256 KB limit.
=serverhealth, =serverbackup, =serverrestore, =servertemplate, =automationtemplate, =rpadmin	Protected health, configuration backup/restore/template, automation-template, and roleplay-administration command families. Restore and template operations use their built-in confirmation workflow; the dashboard is recommended for complex administration.

Detailed =purge guide — destructive and immediate

=purge 50 deletes up to 50 recent messages of any kind in the current channel. With no count, the default is 100. GorBot accepts 1–1,000 and clamps larger requested counts to 1,000.

Supported filter forms include:

• =purge bots 100 — messages by any bot;
• =purge humans 100 — messages by non-bot users;
• =purge gorbot 100 — only messages authored by GorBot;
• =purge user @member 100 — messages from one user;
• =purge match phrase 100 — messages containing the phrase;
• =purge not phrase 100 — messages not containing the phrase;
• =purge startswith phrase 100 / =purge endswith phrase 100;
• =purge links 100, =purge invites 100, =purge images 100, =purge mentions 100, =purge embeds 100, or =purge text 100;
• =purge after <message ID or link> 100 — messages newer than the supplied message.

Recent eligible messages are bulk-deleted in Discord-supported batches. Messages older than Discord's bulk-delete age limit are attempted one by one so a mixed-age cleanup does not fail as one batch. There is no trash/recycle bin: verify the channel, mode, criterion, and count before running the command.

=clean [count] is the moderator-side shortcut that removes GorBot-authored messages from the current channel.

Moderator command families

Commands	Purpose
=clean [count]	Removes GorBot-authored messages from the current channel, using the same bounded cleanup engine as purge.
=kick, =softban, =ban [save|noappeal] <user> [duration] [reason], =unban	Removes, softbans, permanently/timed-bans, or unbans members. Softban removes seven days of recent messages and immediately lifts the ban. A timed ban schedules automatic unban.
=mute/=timeout, =unmute/=untimeout, =deafen, =undeafen	Manages Discord communication timeout and voice deafen state. Timeout durations are capped by Discord's maximum supported timeout window.
=warn, =warnings, =clearwarn, =delwarn/=unwarn	Records, lists, clears, or deletes warnings and their corresponding moderation-case state.
=modlogs, =case, =reason, =moderations, =duration, =modstats	Reviews moderation history/cases, changes a case reason or active timed duration, lists active timed actions, and summarizes moderator activity.
=note, =notes, =delnote, =clearnotes, =editnote	Maintains private staff notes attached to a server member. These are moderation notes, not the player's private character Personal Notes system.
=rolepersist, =temprole, =members <role>	Persists a role across rejoin, applies/removes a timed role, or lists up to 90 members found with a role.
=lock [channel] [duration] [message], =unlock [channel] [message], =lockdown [message], =lockdown end [message]	Saves and changes the Everyone Send Messages overwrite, later restoring the prior state. Timed locks automatically unlock when due. Lockdown uses configured lockdown channels or the current channel as fallback.
=star <message ID or link>, =diagnose [module|command], =ignored	Counts star reactions, reports module/command configuration state, or lists ignored command targets for troubleshooting.

The NPC administration family is only useful when the relevant managed/Living NPC feature is enabled for the community. A command being recognized does not mean every server has that feature turned on.

↑ Back to Top

MODERATION & ADMINISTRATION

Community-level tools for trusted staff and server owners.

The full public moderation guide is available at Moderation & Administration.

GorBot separates ordinary members, moderators, and server managers.

Moderation features can include:

• warnings and disciplinary history;
• message cleanup;
• mute/timeout;
• kick;
• ban;
• voice moderation;
• slowmode;
• role persistence;
• moderator roles;
• server-level moderation configuration;
• supported automated safety controls.

A moderator command can still fail if Discord role hierarchy or permissions prevent GorBot from acting on the target.

↑ Back to Top

AUTOMATION

When this happens → perform the configured response.

See Automation for the full feature overview.

Automations are normally configured through the Web Dashboard because triggers, roles, channels, actions, and publishing state are easier to understand visually.

Possible workflow inputs can include supported events involving:

• messages;
• reactions;
• automation buttons;
• role changes;
• voice activity;
• other enabled community events.

Automations still obey GorBot authorization and Discord permissions. Automating a role action does not allow GorBot to manage a role above its own highest role.

↑ Back to Top

PERMISSIONS & SECURITY

Understanding who can do what is part of using GorBot safely.

Authentication Identifies the Discord account making the request. Dashboard sign-in uses Discord identity; GorBot never needs the user's Discord password.

Authorization Determines whether that user is allowed to perform the requested action based on ownership, server authority, trusted roles, and feature rules.

Discord Permissions Discord itself decides whether the bot can manage messages, roles, members, webhooks, or other server resources.

Command restrictions and precedence

GorBot can evaluate several independent command controls. A disabled command/module or an older ignored channel/user/role can stop ordinary command use. The newer Command Access Guard is stricter:

• the configured Blocked Command Role denies prefix and application commands even to Bot Commanders and the server owner;
• a configured Command-Silent Channel denies commands to everyone in that channel;
• Discord components such as buttons, select menus, onboarding controls, reaction roles, and ticket controls continue according to their own authorization rules;
• the normal progressive command cooldown targets ordinary player command abuse; confirmed server managers/owners remain exempt from that cooldown, but not from the explicit Blocked Command Role or Command-Silent Channel denial.

Never provide secrets to someone claiming they need them for a normal support request.

Normal GorBot users and server moderators should never need to reveal:

• a Discord account password;
• the Discord bot token;
• API keys;
• database passwords;
• OAuth application secrets;
• private server credentials.

If someone asks for sensitive credentials in order to use an ordinary GorBot feature, do not provide them. Contact the server owner or use Contact Us for support.

↑ Back to Top

TROUBLESHOOTING

Start with the simplest checks before assuming the feature is broken.

Problem	What to Check
= command does nothing	Confirm the server still uses = as its GorBot command prefix, try =help, confirm GorBot can read/send in the channel, and confirm the feature is enabled.
Slash command is missing	Type / and inspect GorBot's current autocomplete list. Slash-command availability can vary by release/module. If expected commands are absent, contact the server owner.
Slash command appears but GorBot refuses it	Discord can continue displaying globally registered slash commands. Check whether you hold the server's Blocked Command Role or are using a Command-Silent Channel. Slash denials are normally ephemeral.
Prefix command is silently ignored	Besides the configured server prefix and module state, check the Blocked Command Role and Command-Silent Channels. Prefix denials in these onboarding/security areas are intentionally silent.
=say says no active character	Open =Menu, use /character switch, or select the intended character in the Character Library, then retry =say.
Character Speaking Prefix does nothing	Confirm the message author owns the character, that exact character is currently active, the prefix matches exactly, the message is in a supported roleplay context, and the prefix field is not blank. Another player's identical prefix does not grant access to your character.
Recent-character dropdown does not show one of my characters	The top-right selector intentionally shows only the five most recently activated characters. Open the Character Library and activate another owned character there to bring it into the recent list.
=say cannot post	The server owner should verify View Channel, Send Messages, Manage Webhooks, Manage Messages, and thread permissions where relevant.
=profile is very long	This can be normal for a heavily populated profile. GorBot paginates populated fields across multiple embeds rather than silently dropping them.
Character image does not appear	Confirm the image is supported and accessible, or update the portrait through the Character Library.
Public Character share link does not open	Confirm public sharing is still enabled for that character and that the link was not invalidated by a share-token rotation or character deletion. Both supported compact and legacy links can remain valid when sharing is enabled.
Character Import maps a field incorrectly	Use the preview before saving. Raw Text and generic third-party formats are best-effort; clearer labels/headings improve mapping. Correct ambiguous fields in the preview/editor before committing the import.
Character Import reports a possible duplicate	Review the duplicate-name warning. Import creates new records rather than silently overwriting an existing character.
Cannot edit a character or NPC	Confirm you own the record and are signed into the correct Discord account. Public visibility does not grant edit ownership.
Role command fails	Check Manage Roles and make sure GorBot's highest role is above the target role.
Kick/ban/timeout fails	Check both the moderator's authority and GorBot's Discord moderation permissions/role hierarchy.
Dashboard shows the wrong permissions	Confirm you signed in with the intended Discord account and that the server still grants the expected owner/manager role.
Dashboard menu returns to the top	Portal 2.7.1.1 corrects the collapsible-menu layout/restore race. Hard-refresh once to replace cached JavaScript/CSS, then test navigation again.
Profile field will not save	Check the live counter and the field-specific limit shown by the editor. GorBot enforces the same limit server-side and does not silently truncate oversized profile text.
=purge deletes nothing	Confirm the command is being run in the intended channel, the filter mode/criterion actually matches messages, GorBot can Read Message History and Manage Messages, and the caller has owner/Bot Commander authority.
NPC command does nothing	Confirm the server has the relevant NPC interaction feature enabled and that the requested NPC is available to that workflow.
Automation does not run	Confirm the automation is enabled, its trigger matches the event, the configured channels/roles still exist, and GorBot has permission to perform the action.

If the problem continues after the relevant checks, use Contact Us and include the command or feature name, what you expected to happen, what actually happened, and any visible error message. Do not include passwords, tokens, API keys, database credentials, mailbox passwords, or other secrets.

↑ Back to Top

FREQUENTLY ASKED QUESTIONS

Common questions from players and server owners.

Do I have to use the Web Dashboard? No. Many features work directly in Discord. The dashboard is primarily for features that benefit from larger forms, browsing, Character Import/Export, sharing controls, and persistent configuration pages.	Is = always the GorBot command prefix? It is the default prefix used by this guide. A server owner can configure another supported GorBot command prefix.
Is a Character Speaking Prefix the same as the server command prefix? No. The server command prefix is used for GorBot commands. A Character Speaking Prefix is an optional private shortcut stored on one character and works only for that character's owner while that character is active.	Can two players use the same Character Speaking Prefix? Yes. GorBot checks who sent the message first, then checks that user's active character. A prefix such as [dyne therefore does not have to be globally unique.
Why does the top-right character selector show only five characters? A user can own up to 150 characters, so the compact selector intentionally shows the five most recently activated characters. The full Character Library is used to browse or activate the rest.	Can another player edit my character? Not simply because the character is visible or publicly shared. Character ownership and edit authorization are separate from public presentation.
Can I import a Tupperbox character? Yes. Character Import recognizes the current Tupperbox JSON structure and maps useful profile information. Review the preview before saving because third-party fields do not always have a perfect one-to-one GorBot equivalent.	Can someone edit a shared NPC? Sharing or publishing does not automatically transfer ownership or edit rights.
Why can I see a staff command if I cannot use it? Command knowledge is not authorization. GorBot still checks the user and Discord permissions before protected actions are allowed.	Where can I learn what GorBot is? See About GorBot for the project background, purpose, and relationship with Gor Ultima.

↑ Back to Top

Still need help?

Use the dedicated contact page for support that cannot be resolved by the guide above.

Contact Us About GorBot ↑ Back to Top

When requesting help, never include passwords, bot tokens, API keys, database credentials, or other private secrets.