BotSupportHome

GORBOT SUPPORT

Commands, player help, 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 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 or select a character;
• use =say <message> to speak as the active character;
• use the Character Library when you want to edit a full profile;
• use the NPC Database for NPCs you own;
• use Discord slash-command autocomplete to see currently enabled slash-command options.

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

=

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

↑ Back to Top

PLAYER GUIDE

The parts of GorBot most community members will use regularly.

Characters Create persistent roleplay identities, select an active character, maintain biography/profile information, and speak through the character in Discord. See Characters & Profiles.

NPCs Browse, talk with, 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, NPC management, 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.

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.

↑ 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 link	Uses the supported character-linking workflow available in the current character system.
/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.

↑ 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 or 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 custom fields where desired;
5. select the character as active;
6. use =say <message> or /character say for character speech.

GorBot supports multiple profile styles so a community is not forced into one setting:

• Gorean;
• Standard RP;
• Fantasy RP;
• Tabletop D&D;
• Modern / Sci-Fi RP;
• Custom / Freeform.

Each character can also use up to 12 custom fields.

↑ 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 and ownership, users can:

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

Sharing an NPC profile does not automatically give another user edit ownership.

↑ 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.

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.

↑ 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 characters and NPCs.

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

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

↑ 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.

↑ 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.

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.

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 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.
=say says no active character	Open =Menu, select the intended character, then retry =say.
=say cannot post	The server owner should verify View Channel, Send Messages, Manage Webhooks, Manage Messages, and thread permissions where relevant.
Character image does not appear	Confirm the image is supported and accessible, or update the portrait through the Character Library.
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.
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, 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, and persistent configuration pages.	Is = always the prefix? It is the default prefix used by this guide. Server configuration can use another supported prefix.
Can another player edit my character? Not simply because the character is visible. Character ownership and edit authorization are separate from public presentation.	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.