R8k0 Guardian Bot | R8K0 Mods

R8K0 Guardian - Master Website Documentation Complete Setup, Feature, Staff, and Administrator Guide Updated November 3, 2026 Customer-facing master guide reconstructed from Guardian v0.49.4, v0.50.1, and later November 2026 dashboard builds. CURRENT LEGACY / OPTIONAL PLANNED / EXPANSION CURRENT = confirmed in the v0.50.1 runtime or later completed builds. LEGACY / OPTIONAL = older or optional functionality. PLANNED / EXPANSION = requested roadmap items that should not be advertised as live until implemented and tested. Contents 1. About This Guide 2. What R8K0 Guardian Does 3. Initial Installation and First-Time Setup 4. Dashboard Login, Community Selection, and Access 5. Subscription and Entitlements 6. General Settings 7. Security 8. Verification 9. Welcome and Goodbye Messages 10. Logging 11. Moderation and Case History 12. Tickets - Overview 13. Tickets - Creating a Ticket Type 14. Ticket Hierarchy Builder 15. Ticket Panels and Ticket Duplication 16. Applications - Overview 17. Creating an Application 18. Application Button Panels 19. Hosted and Paged Application Forms 20. Workflow Forms - Staff Punishments, LOA, and Internal Requests 21. Staff and Member Actions 22. Self Roles / Role Panels 23. Announcements 24. Embed Creator 25. Information Panels and Document Links 26. Suggestions 27. Polls 28. Permission Studio / Permission Editor 29. Editing Category and Channel Permissions 30. Role Permission Editor and Role Organizer 31. Server Builder - Overview 32. Server Builder Migration Safety 33. Server Builder Modes Used During Rebuild Testing 34. Backups, Restore, Import, Export, and Reset 35. Diagnostics and Repair Tools 36. Server Statistics 37. Guardian AI Assistant 38. Documents, SOPs, and Google Docs Replacement/Integration 39. Marketing Center 40. FiveM Integration 41. Slash Command Reference 42. Recommended Full Server Setup Order 43. Common Troubleshooting 44. Website Documentation Structure Recommendation 1. About This Guide This is the master customer-facing documentation for R8K0 Guardian. It combines the older Guardian v0.49.4 documentation, the v0.50.1 permission and migration improvements, and the later dashboard builds through the application/ticket workflow work completed on November 2, 2026. Because Guardian changed quickly during these builds, every feature in this guide is marked as one of these statuses: CURRENT: Confirmed in the v0.50.1 code/runtime or later completed dashboard builds. LEGACY / OPTIONAL: Older functionality that still exists in the Guardian history but may be reduced or removed from the main product. PLANNED / EXPANSION: A feature requested for the next Guardian expansion and not safe to advertise as already available until it is implemented and tested. Guardian is designed to be dashboard-first. Most server owners should configure the bot from the web dashboard and use Discord slash commands mainly for quick actions, diagnostics, moderation, and fallback access. 2. What R8K0 Guardian Does R8K0 Guardian is a Discord server management platform. It combines moderation, verification, security, tickets, applications, forms, staff workflows, self roles, announcements, embeds, server layout tools, permissions, backups, diagnostics, and community management in one dashboard. The current Guardian runtime is a Node.js / discord.js application. The v0.50.1 runtime has been confirmed with 37 slash commands, a SQLite database, a web dashboard, Discord OAuth community selection, multi-community support, and an internal Discord API bridge. The dashboard is intended for server owners and authorized staff. A paid plan can unlock features, but the plan does not automatically give every person access. Dashboard access and Discord permissions still control what an individual staff member can do. 3. Initial Installation and First-Time Setup Use this order when adding Guardian to a new Discord server. Invite/install R8K0 Guardian into the Discord server. Confirm the bot is online. Move the R8K0 Guardian bot role high enough in the Discord role list to manage every role Guardian needs to assign or edit. Give Guardian the Discord permissions required for the features you plan to use. Role management, channel management, message management, moderation, and webhooks may be required depending on the module. Open the Guardian Dashboard and sign in with Discord. Select the community you want to manage. Open Subscription and confirm Guardian recognizes the correct plan. Use Refresh Access after a Discord subscription change. Open Settings and configure dashboard access roles, staff roles, server branding, and logging destinations. Configure Verification. Configure Logging. Configure Tickets. Configure Security. Configure Applications, Forms, Information Panels, Self Roles, Announcements, and Embeds as needed. Configure Permissions and Server Builder only after the basic server is working. Create a backup before any large migration, role rebuild, permission rewrite, or server layout change. Important: Guardian cannot manage a role positioned above the Guardian bot role. This is one of the most common reasons verification, applications, or self-role assignment appears to save correctly but does not actually give the role. 4. Dashboard Login, Community Selection, and Access Open the Guardian Dashboard and sign in using the Discord account that manages the community. After login: Select an authorized community where Guardian is installed. Use the left navigation to open the feature you want. If a page redirects to Subscription, verify that the Discord account has the required Guardian plan and press Refresh Access. If a feature is unlocked but a staff member still cannot use it, check the server's Dashboard Access roles and the person's Discord permissions. Recommended access model: Owner: full access, including destructive server-management tools. Administrator / Management: most server-management features. Moderator: moderation, reports, cases, and limited community tools. Department staff: only the operational pages needed for their department. Regular member: no management dashboard access unless intentionally granted. 5. Subscription and Entitlements CURRENT Guardian subscriptions are handled through Discord entitlements/subscriptions. The historical documentation contains these feature groups: Guardian Basic / Free: Moderation Tickets Logging Verification Welcome / Goodbye Suggestions Polls Public settings and subscription pages Guardian Plus: Everything in Basic Advanced Security Staff / Member personnel actions Applications Self Roles Announcements Embed Creator Guardian Premium: Everything in Plus Server Builder Backups Diagnostics Premium server-management tools Guardian FiveM Add-on: Historical/optional FiveM bridge features Use the Subscription page to view the resolved plan. After buying, changing, or restoring a Discord subscription, use Refresh Access. Do not confuse feature access with staff permission. A subscription makes the module available; it does not automatically authorize every staff member to use it. 6. General Settings CURRENT Settings should be the first configuration page used on a new server. Typical setup items: Server/community branding Dashboard access roles Staff/management roles Logging destinations Feature defaults General Guardian behavior Recommended setup: Add only trusted management roles to dashboard access. Add the roles Guardian should treat as staff. Configure log channels before enabling advanced workflows. Save settings. Test with a non-owner staff account to make sure access is neither too broad nor too restrictive. 7. Security CURRENT The Security module is the main protection area for the Discord server. Historical/current security capabilities include: Account-age protection Spam protection Anti-raid behavior Blacklist/security rules Bypass roles Enforcement actions Security status checks Basic setup: Open Security. Enable only the protection modules you want. Set bypass roles for trusted bots, owners, or staff where appropriate. Configure account-age or anti-spam thresholds. Choose the enforcement behavior. Save. Test with a controlled account before relying on the rule in production. Best practice: Avoid giving broad bypass roles to normal members. A bypass should only be used when a trusted role would otherwise be incorrectly affected by an automated protection. 8. Verification CURRENT Verification controls how new members receive server access. The later dashboard builds specifically fixed the add-role/remove-role behavior so verification can: Add the Verified role. Remove an Unverified or onboarding role. Apply both actions together. Setup: Create or identify the Discord role members should receive after verification. Create or identify any role that should be removed after verification. Put the Guardian bot role above both roles. Open Verification in the dashboard. Choose the verification channel and verification method/panel. Select the role to add. Select the role to remove, if used. Configure account-age protection if desired. Save. Test using a non-staff account. Expected result: A successful verification should change the member's Discord roles immediately and allow access to the channels that depend on the Verified role. Related commands: /verifysetup /verificationstatus 9. Welcome and Goodbye Messages CURRENT Guardian can send onboarding messages when someone joins and departure messages when someone leaves. Setup: Open Welcome / Goodbye. Choose the welcome channel. Enable the welcome message and enter the message content. Configure any welcome embed or onboarding information. Choose the goodbye channel. Enable and configure the goodbye message. Save. Test with a controlled join/leave if possible. The late dashboard fixes addressed situations where the configuration appeared correct but goodbye messages were not being sent. 10. Logging CURRENT Guardian logging records Discord and Guardian activity for staff review. Guardian can automatically provision a private R8K0 Guardian Logs category and related channels. Recommended log groups: Moderation actions Verification activity Ticket activity Application decisions Staff/personnel workflows Security actions Server Builder / permission changes Errors or diagnostics Setup: Open Logging. Choose existing log channels or allow Guardian to provision its log structure. Restrict the log category so only authorized staff can view it. Save. Trigger a test action and confirm it appears. Important: Discord API rate limits can delay automatic provisioning. Guardian's later permission/server builder work preserved serialized request handling and retry behavior for HTTP 429 rate limits. Related command: /logstatus 11. Moderation and Case History CURRENT Guardian moderation includes: Warn View warnings View a case Kick Ban Timeout Remove timeout Moderation history/case tracking Common commands: /warn /warnings /case /kick /ban /timeout /untimeout Recommended workflow: Staff selects the member. Staff provides a clear reason. Guardian applies the action. Guardian records the case. Relevant logs are written to the configured moderation log channel. Use case history instead of relying only on Discord's native audit log when your staff needs an organized record of warnings and prior actions. 12. Tickets - Overview CURRENT Guardian's ticket system grew from simple ticket creation into a full panel, intake, hierarchy, and workflow system. Core ticket features include: Multiple ticket types Ticket panels Ticket descriptions Opening messages Intake forms Staff access Dynamic categories Closed-ticket behavior Transcripts Ticket dashboards/statistics Ticket repair Staff hierarchy/escalation Hierarchy presets/default hierarchy Duplicate ticket types Multiple ticket panels Ticket commands: /ticket /ticketsetup /ticketstats /ticketrepair Dynamic categories: When enabled, Guardian can create the active category when the first ticket of a type opens, reuse that category for later tickets, and remove it after the last ticket closes when the category is empty. Transcripts can be archived automatically depending on the ticket configuration. 13. Tickets - Creating a Ticket Type CURRENT To create a ticket type: Open Tickets. Open Ticket Types. Choose Create Ticket Type. Enter the ticket name. Add a short menu description. Enter the opening message members will see after the ticket is created. Configure the intake form. Select the staff roles that can access the ticket. Configure hierarchy or load the default hierarchy. Configure escalation options. Select category behavior and transcript behavior. Save. Intake forms: Traditional Discord modal-based ticket intake should be kept to a maximum of five fields. Each field can be configured as short or paragraph text and can be required or optional. Examples that have been used with Guardian: General Support Player Report Staff Report Ban Appeal Bug Report Role Assistance Department Assistance Partnership Request Management Contact Command Assistance IA Complaint Training Request LOA Request Division Transfer Roster / Role Correction Promotion / Rank Issue Personnel Issue Report Assistance High Command Contact Guardian Support Dashboard Support Billing Support License Support Feature Request 14. Ticket Hierarchy Builder CURRENT - v54 lineage The Ticket Hierarchy Builder lets the server decide which staff roles receive a ticket and how the ticket escalates. Tickets > System includes a Default Ticket Hierarchy builder. Setup: Open Tickets > System. Use the searchable checkbox role selector to choose the default ticket staff roles. Add escalation levels in the exact order you want. Use Add Level, Up, Down, and Remove to arrange the hierarchy. Configure escalation behavior. Save the default hierarchy. New ticket types can automatically start with the saved default hierarchy. Existing ticket types can use Load Default Hierarchy. Supported escalation behavior includes: Ping the higher role Keep lower roles involved Skip levels De-escalation The later builder intentionally uses searchable checkboxes instead of Ctrl/Cmd-click multi-select controls. 15. Ticket Panels and Ticket Duplication CURRENT - later November 2 builds Ticket Panels determine how members choose which ticket they want to open. Panel setup: Create the ticket types first. Open Ticket Panels. Create a panel. Choose the channel. Add the panel title and description. Select the ticket types using searchable checkboxes. Save/publish the panel. Ticket duplication: Later builds added Duplicate Ticket Type. Duplicating should preserve: Intake questions Staff hierarchy Hierarchy preset Permissions Ticket behavior/settings Use Duplicate when several departments use almost the same ticket workflow. Rename the duplicate and change only the department-specific details. This prevents rebuilding long ticket forms and hierarchies from scratch. 16. Applications - Overview CURRENT - expanded significantly in v42 through v65 lineage Guardian Applications supports: Staff applications Department applications Whitelist applications LOA applications Custom application workflows Review channels Approval/denial Role assignment after approval Button-based application panels Private form flow DM flow Single-page and paged forms Open/Closed status Duplicate applications Multiple application panels The later dashboard work moved Guardian away from relying only on slash commands. Button-first application panels are the preferred member experience, while /apply remains available as a fallback. 17. Creating an Application CURRENT Open Applications. Create a new application. Enter the application name and description. Add the application questions. Choose the submission mode: - Private Form - DM flow - Hosted Single/Paged Form where enabled Choose the review channel. Configure who can review the application. Configure approval and denial behavior. Configure any role that should be granted after approval. Save Application. Add the application to an Application Panel. The late v44 dashboard build specifically added a visible Save Application action and replaced the older drop-down-first member experience with buttons/forms. 18. Application Button Panels CURRENT - v62 lineage Application Button Panels allow members to start applications by clicking buttons instead of typing commands. Capabilities: Multiple panels Custom panel channel Panel title Panel description Multiple application buttons Button styles Up to 25 buttons per panel Update/remove panel Existing form or DM flows behind the button Setup: Create and save all applications. Open Application Panels. Choose Create Panel. Select the destination channel. Enter the title and description. Add the applications you want shown as buttons. Set each button's style/label. Save/publish. Keep button names short and obvious, such as "Staff Application," "BCSO Application," or "LOA Request." 19. Hosted and Paged Application Forms CURRENT - v64 lineage The hosted form system was designed for applications that are too long for one Discord modal. Single/Paged Form behavior: Displays the full application in pages. Previous and Next buttons move between pages. Submit appears on the final page. Questions/settings are stored with the application. Use a paged application when the application has more questions than can be comfortably handled in a single Discord modal or DM sequence. Application duplication: Duplicate Application copies the existing application's questions and settings so the new copy can be renamed and edited. Open/Closed status: Applications can be set to Open or Closed. When closed, the application should not accept a new submission and should return the configured closed message instead. 20. Workflow Forms - Staff Punishments, LOA, and Internal Requests CURRENT/EXPANDED - v51+ lineage Guardian's workflow-form direction is designed to replace manual Google Form-style staff processes for common Discord operations. Examples: Staff punishment form Staff strike Suspension LOA request Promotion/demotion Hiring Personnel action Internal request Recommended workflow: Staff/member opens the form. Guardian collects the configured fields. Submission is posted into the configured review/log channel. Authorized staff review it. Approval or Denial actions are recorded. The final decision stays in the log for future reference. LOA example fields: Name / callsign Current rank Start date Expected return date Reason For staff punishment forms, include: Staff member Action type Reason Evidence/reference Issuing supervisor Effective date Duration, if applicable The goal is to create a permanent, searchable Discord-side record instead of relying on a form submission that disappears into a separate service. 21. Staff and Member Actions CURRENT Guardian supports personnel-management actions such as: Warnings Staff strikes Suspensions Hiring Promotion Demotion Roster/personnel workflows Use these tools with role-restricted access. Normal moderators should not automatically receive high-level personnel controls. Recommended setup: Create a dedicated management role or staff-action role. Restrict the personnel page to that role. Configure a personnel log channel. Require a reason for every action. Use the workflow form where a review/approval process is required. 22. Self Roles / Role Panels CURRENT Guardian can create self-role panels that let members choose roles without staff manually assigning them. Features: Button panels Select-menu panels Single-select or multi-select behavior Required-role gates Mutually exclusive role groups Panel management Setup: Put Guardian's role above every role the panel can assign. Open Self Roles / Role Panels. Create a panel. Choose the destination channel. Add role options. Choose button or select-menu behavior. Configure required roles if needed. Configure mutually exclusive roles where appropriate. Save and publish. Commands: /rolepanels /rolesetup 23. Announcements CURRENT - later dashboard redesign Guardian announcements support both immediate and scheduled publishing. Publishing options: Publish Now Schedule Later Scheduled announcements can include scheduling options such as timezone and repeat behavior where enabled. Setup: Open Announcements. Choose the destination channel. Create the announcement content. Select Publish Now for immediate delivery or Schedule Later. For scheduled delivery, choose the date/time and timezone. Configure repeat behavior if the current build exposes it. Save/publish. Commands: /announcement /announcementsetup 24. Embed Creator CURRENT The Embed Creator lets staff build branded Discord embeds without manually writing JSON. Typical use: Rules panels Department information Server notices Staff information Support information Links and resources Setup: Open Embed Creator. Choose the destination channel. Enter the title, description, fields, footer, links, and other supported embed content. Preview. Publish. Command: /embed 25. Information Panels and Document Links CURRENT/RECENT EXPANSION Information Panels were added to give servers a clean dashboard-based way to create structured information messages. Use Information Panels for: Department hierarchy Rules SOP links Training information Important links Application information Report information Staff resources The newer panel design direction uses clean searchable dropdowns/checkboxes for roles, channels, and categories, and supports emoji selection instead of forcing staff to manually paste awkward IDs. Document links can be used to point members to SOPs, policies, rosters, or other external documents. The planned Google Docs expansion described later in this guide is intended to take this further by reducing the server's dependence on external forms and scattered documents. 26. Suggestions CURRENT Guardian Suggestions allows members to submit ideas while staff manage the review process. Features: Suggestion channel setup Member submissions Staff review Status changes Staff responses Suggestion statistics Commands: /suggest /suggestionsetup /suggestionstats Recommended statuses: Pending Under Review Planned Approved Denied Completed 27. Polls CURRENT Guardian Polls lets staff create and manage community polls. Features: Create poll Configure poll channel/settings View voters Close poll Commands: /poll /pollsetup 28. Permission Studio / Permission Editor CURRENT - major v0.50.1 improvement The Permission Editor is designed to manage roles, categories, and channels without forcing administrators to use Discord's repetitive native permission screens. The current permission design includes: Separate Category Permissions and Channel Permissions Searchable selectors Visible checkboxes Clear selected state Selected-count behavior Select All Clear Multi-target selection Different permissions for each selected target Per-target permission matrix Role Permission Editor Permission presets Permission presets: Hidden Read Only View + Send Clear / Inherit Custom The editor prioritizes View Channel because visibility is the first requirement for most channel permission setups. Important: The later v0.50.1 work preserves Discord permission bits Guardian does not expose. Editing one permission should not wipe newer or unknown Discord permission flags. 29. Editing Category and Channel Permissions CURRENT Open Permission Editor. Choose Category Permissions or Channel Permissions. Search for the target. Check one or more categories/channels. Choose the role/member target whose permissions you are editing. Use a preset or Custom. Set each exposed permission to Allow, Neutral, or Deny. When multiple channels/categories are selected, configure each target independently as needed. Save. Allow: Explicitly grants the permission. Neutral: Does not explicitly grant or deny it at that target and allows inheritance/other Discord rules to decide. Deny: Explicitly blocks the permission. Do not use a broad Deny unless you intentionally want it to override lower-level permission grants. 30. Role Permission Editor and Role Organizer CURRENT/RECENT The Role Permission Editor manages server-wide Discord permissions on a role, such as: Administrator Manage Server Manage Roles Manage Channels Manage Webhooks Manage Events Membership-related permissions Text/thread permissions Voice permissions Other Discord role permission bits Role Organizer: The newer dashboard direction includes a role organizer so admins can change role order from Guardian instead of manually dragging roles in Discord. Important hierarchy rules: Guardian cannot move or manage roles above its own highest role. Managed/integration roles cannot be freely moved like normal roles. Permission changes should preserve Discord permission bits not directly exposed by the dashboard. 31. Server Builder - Overview CURRENT / PREMIUM Server Builder is Guardian's bulk Discord structure manager. It can be used to: Create categories Create channels Create roles Apply permissions Import templates Preview changes Compare a template with the live server Apply migrations Preserve matching channels/roles Rename or move matching structures Archive or delete unmatched structures depending on mode Restore from backups Repair a layout Use Server Builder carefully. It is the feature most capable of making large server-wide changes. 32. Server Builder Migration Safety CURRENT The later migration logic uses this matching order: Existing Discord ID Alias Normalized/decorated name matching When Guardian finds a match, it should preserve the existing Discord ID rather than unnecessarily deleting and recreating the object. Omitted template settings are preserved. If a template does not specify a channel topic, slowmode, NSFW state, permission overwrite, voice setting, or forum setting, Guardian should not reset that live value just because it was omitted. Bulk role creation skips roles that already exist, including case-insensitive duplicates. Rate limits: Guardian serializes Discord mutations and retries the exact action when Discord returns a 429 rate limit. 33. Server Builder Modes Used During Rebuild Testing CURRENT/ADMIN-LEVEL - use with extreme care During blank-server testing, Guardian used multiple migration/rebuild concepts: Safe Apply / migration: Preserve matching live objects and apply requested changes. Roles Only: Limit the operation to roles/role permissions without rebuilding the whole server. The confirmation phrase used during testing was "ROLES ONLY". Role Rebuild / Wipe Roles: Designed to delete editable roles, preserve protected/managed roles, recreate the hierarchy, restore assignments where supported, and repair permission overwrites. Permissions-only repair: Apply the desired permission model without rebuilding categories/channels. Closed-by-default permission models: The testing templates used @everyone with minimal/no access, then explicitly granted Verified/community, department, economy, staff, owner, moderation, ticket, and application access. Always create a backup before using destructive modes. 34. Backups, Restore, Import, Export, and Reset CURRENT / PREMIUM Guardian backup tools can be used to: Create a backup Restore a backup Export configuration Import configuration Clean up stored backup/config data Reset Guardian configuration Recommended rule: Create a backup before: Full server migration Role wipe/rebuild Large permission changes Server Builder cleanup Template replacement Major dashboard configuration changes Restore should be treated as an administrative action and restricted to the server owner or a very small trusted group. 35. Diagnostics and Repair Tools CURRENT / PREMIUM Diagnostics compares Guardian's saved configuration with the live Discord server. Use diagnostics to find: Missing channels Missing categories Missing roles Broken references Configuration objects that no longer exist in Discord Ticket repair is available through /ticketrepair. Staff recovery and Guardian reset commands also exist for administrative recovery: /staffrecovery /guardianreset Use reset only when you understand which Guardian configuration will be removed or rebuilt. 36. Server Statistics PLANNED / EXPANSION A Server Statistics section was requested for the next Guardian expansion. Desired statistics include: Total members Real human members Bots Online members where Discord allows the data Staff counts Verified/unverified counts Join/leave trends Ticket volume Application volume Moderation counts Security events A key requirement is to separate bots from real members so a server can see its true community size instead of a single inflated member total. Do not advertise this as a current live feature until the stats page is implemented and tested in the production dashboard. 37. Guardian AI Assistant PLANNED / EXPANSION Guardian AI was requested as a Discord support/triage assistant. Example desired behavior: A member asks in a general channel about a bug. Guardian AI recognizes that the question is a support/bug issue and replies with the correct next step, such as: Basic troubleshooting A link to the correct information/SOP "Open a Bug Report ticket" "Open a Guardian Support ticket" "Use the application panel" "Contact staff through the correct form" Recommended safety/management design: AI replies should be limited to approved channels. Server admins should be able to turn AI on/off per channel. The dashboard should contain approved knowledge sources and response rules. AI should route sensitive moderation, billing, appeals, and personnel cases into private tickets instead of trying to resolve them publicly. AI should identify when it is unsure and route the user to staff. AI actions should be logged. Do not advertise AI as already available until the feature is built, tested, and the server can control what information it uses. 38. Documents, SOPs, and Google Docs Replacement/Integration PLANNED / EXPANSION, with CURRENT document-link foundation Many communities use Google Docs for SOPs, department information, applications, and staff forms. Guardian's newer Information Panels and workflow forms already reduce part of that dependency. The requested expansion is a Documents / SOP area that can: Store or organize SOP links Show department documents in one dashboard section Publish clean document buttons/panels to Discord Tie documents to roles/departments Use Guardian-hosted forms for applications and staff requests Keep a central list of policies/resources Potentially integrate with Google Docs for communities that want to keep their existing documents Recommended website wording: "Guardian can centralize your server's SOP links, information panels, forms, and staff workflows. Deeper document hosting/sync features are under development." Do not claim full Google Docs synchronization until that connector/sync workflow is implemented. 39. Marketing Center CURRENT/HISTORICAL The formal Guardian guide includes a Marketing Center used for campaign/referral links where enabled. Use cases: Referral links Campaign tracking Guardian promotion Only show this page in customer documentation if the current production dashboard still exposes it. 40. FiveM Integration LEGACY / OPTIONAL Guardian historically included an optional FiveM bridge. The current product direction is considering reducing or removing the FiveM-server portion from the main Guardian experience so Guardian can focus more heavily on Discord management. Historical FiveM capabilities: Live players Admin actions AOP / Peacetime controls Weather/time synchronization Patrol tools Activity/crash information Configuration builders Authenticated server-key pairing Owner/legacy auto-pair Historical connection model: Activate the FiveM entitlement/add-on. Open Guardian Dashboard > FiveM Server. Copy the Guild ID and server key into server-side configuration only. Start the FiveM resource. Confirm heartbeat/live data. Security: Never expose a server key, bot token, bridge secret, or other private credential in client Lua, NUI JavaScript, public GitHub, screenshots, or Discord messages. Website recommendation: Move this section into "Legacy / Optional Integrations" unless you decide to keep FiveM as a primary Guardian product feature. 41. Slash Command Reference CURRENT v0.50.1 runtime Public: /ping /botinfo /guardian Moderation / Basic: /warn /warnings /case /kick /ban /timeout /untimeout /verifysetup /verificationstatus /suggest /suggestionsetup /suggestionstats /poll /pollsetup /logstatus /setup /ticket /ticketsetup /ticketstats /ticketrepair Plus-era commands: /announcement /announcementsetup /applications /applicationsetup /apply /embed /rolepanels /rolesetup /securitystatus Premium-era commands: /serverbuilder /serverconfig /templateimport /staffrecovery /guardianreset The dashboard is preferred for complex configuration. Commands are useful for quick setup, status, moderation, member actions, and recovery. 42. Recommended Full Server Setup Order Use this exact order for a clean deployment: Phase 1 - Foundation Install Guardian. Position the bot role. Confirm dashboard login. Refresh Subscription. Configure Settings and dashboard access. Phase 2 - Onboarding Configure Verification. Configure Welcome / Goodbye. Configure Logging. Test a new-member flow. Phase 3 - Support Build ticket types. Configure Default Ticket Hierarchy. Build ticket panels. Test open/close/transcript behavior. Phase 4 - Staff/Department Operations Build Applications. Build Application Button Panels. Build workflow forms for LOA/personnel actions. Configure Staff/Member Actions. Configure Information Panels and document links. Phase 5 - Community Tools Configure Self Roles. Configure Announcements. Configure Embed Creator. Configure Suggestions. Configure Polls. Phase 6 - Security and Structure Configure Security. Review Role Permissions. Review Category Permissions. Review Channel Permissions. Use Role Organizer if required. Phase 7 - Advanced Create a backup. Use Server Builder/template migration. Run Diagnostics. Test with owner, staff, verified member, unverified member, department member, and normal member accounts. 43. Common Troubleshooting Guardian cannot assign a role: Move Guardian's bot role above the target role. Confirm Manage Roles permission. A feature redirects to Subscription: Confirm the correct Discord account is logged in. Confirm the subscription/entitlement. Use Refresh Access. Staff can see the dashboard but cannot use a feature: Check Dashboard Access roles. Check feature-specific roles. Check Discord permissions. Goodbye message is not sending: Re-save the Goodbye configuration. Confirm the channel still exists. Confirm Guardian can send messages/embed links in that channel. Ticket category does not exist: If dynamic categories are enabled, it may not be created until the first ticket opens. Ticket or application selector is hard to use: Current newer builds should use searchable checkboxes instead of native Ctrl/Cmd-click multi-select. Permission changes did not match the expected result: Check category inheritance. Check channel overrides. Check role hierarchy. Check explicit Deny values. Use Neutral when you want inheritance. Discord API 403 Missing Permissions: Guardian is missing a Discord permission or is below the role/object it is attempting to manage. Discord API 429: Discord is rate limiting requests. Later Guardian request handling is designed to queue and retry mutations instead of blasting the API. Dashboard/service crashes after a permission or layout action: Review the service log for the first Discord API error. Fix the missing permission/hierarchy issue before repeating the operation. 44. Website Documentation Structure Recommendation For the public R8K0 website, split this master guide into shorter pages: Getting Started What Guardian Is Install Guardian First-Time Setup Dashboard Login Subscriptions Community Setup Verification Welcome / Goodbye Logging Self Roles Information Panels Support & Staff Tickets Ticket Hierarchy Applications Application Panels Forms & LOA Staff Actions Management Moderation Security Announcements Embeds Suggestions Polls Advanced Server Management Permission Editor Role Organizer Server Builder Templates / Migration Backups Diagnostics Reference Slash Commands Troubleshooting Permissions/Role Hierarchy Legacy FiveM Integration Coming Soon / Roadmap Guardian AI Server Statistics Expanded Documents / SOP tools This keeps the customer site easy to understand while preserving the complete master manual internally.