Discord Bot

BetaHub’s Discord bot transforms your community server into a powerful bug reporting and engagement platform.

Overview

BetaHub assigns a dedicated Discord bot for each project that can:

• Collect bug reports using the /report command
• Automatically capture bug reports from conversations
• Provide instant AI-powered support answers
• Broadcast new release announcements
• Facilitate community interactions about bug reports
• Request additional information from users

The bot proactively engages users through direct messages and threads, seeking further details about bugs and requesting screenshots, videos, or log files.

Quick Setup

1. Go to BetaHub
2. Choose your project
3. Select ‘Settings / Discord Bot’ from the left menu
4. Follow the three-step configuration process
5. Use /info to verify setup and /help for command list

Required Permissions

Basic Requirements (Always Needed)

• View Channels - Browse channels and identify bug report channel
• Send Messages - Post bug reports and messages
• Embed Links - Provide visual information to reporters

Optional Features

• Send Messages in Threads - Create and manage discussion threads
• Create Public/Private Threads - Organize bug report discussions
• Attach Files - Include screenshots in release announcements
• Mention Everyone - Notify about new releases

Bug Reporting Methods

1. /report Command

The primary method for intentional bug reporting:

• Opens dialog for detailed bug information
• Posts formatted report in designated channel
• Provides link back to BetaHub for editing
• Supports custom field validation

2. Listen Mode (AI-Powered)

Automatically detects bug reports in conversations:

Configuration:

Options:

• all - Detect bugs and support requests
• bugs_only - Only identify bug reports
• support_only - Only support requests
• off - Disable automatic detection

3. Mention-Based Reporting

Users can mention the bot with bug details in the same message for quick reporting.

4. Report Button

Pin a “Report a Bug” button to channels for easy access.

Suggestion Submission Methods

BetaHub’s Discord bot also enables community members to submit feature suggestions and improvement ideas directly through Discord.

1. /suggest Command

The primary method for submitting feature suggestions:

• Opens modal dialog for detailed suggestion input
• Validates minimum description length requirements
• Posts suggestion directly to your BetaHub project
• Provides confirmation with BetaHub link for tracking

2. Suggestion Buttons

Administrators can deploy interactive “Suggest a Feature” buttons for easy community access:

Setup Requirements:

• Manage Channels permission required
• Creates persistent button for user interactions
• Customizable button text and accompanying message

Alternative Setup: Use the /info command and click “Post ‘Suggest a Feature’ Message here” button for quick deployment.

3. Message Customization

Customize the suggestion experience with three key templates:

Suggestion Button Message:

• Customize the text displayed with suggestion buttons
• Default: “📝 Have ideas for improving our game? Click the button below to suggest a new feature or improvement!”

Dialog Title:

• Personalize the suggestion submission modal title
• Default: “Feature Suggestion”

Submission Confirmation:

• Modify the success message after suggestion submission
• Includes suggestion details and BetaHub tracking URL

Access customization through /info → “Customize Messages”.

AI-Powered Support Features

The Discord bot integrates with BetaHub’s Support Knowledge Base to provide instant AI-powered answers to common questions, reducing support workload and enabling self-service problem resolution.

Setup Checklist

Before users can get AI-powered help, complete these steps:

1. ✅ Enable Support Knowledge Base
   • Go to Settings / General in BetaHub
   • Enable Support Knowledge Base
   • Upload your game documentation
   • Complete setup guide →
2. ✅ Test Basic Functionality
   • Run /ask in Discord with a test question
   • Verify the bot returns an accurate answer
   • Check that feedback buttons appear
3. ⚙️ Customize Messages (Optional)
   • Run /info and click “Customize Messages”
   • Personalize dialog titles and answer templates
   • View customization options →
4. 📢 Announce to Community
   • Tell users about the new AI support feature
   • Share examples of good questions to ask
   • Monitor feedback in your dashboard

Ready? All methods work automatically once knowledge base is enabled. Choose how users will discover the feature below.

Three Ways to Get Instant Help

Choosing the Right Methods

Recommendation: The /ask command works for all users automatically. Add help buttons to support channels for visibility. Bot mentions work everywhere the bot can see messages.

1. /ask Command

The primary method for users to ask questions directly:

• Opens modal dialog for structured question input
• 30-500 character requirement ensures detailed questions
• Returns AI-generated answer from knowledge base
• Includes feedback buttons (thumbs up/down) for answer quality

User Experience:

1. User runs /ask command
2. Modal opens with text input field
3. User types question (minimum 30 characters)
4. Bot searches knowledge base and responds
5. Answer appears with “Was this helpful?” feedback buttons

2. Mention the Bot

Users can get instant help by mentioning the bot anywhere in the server:

How it works:

• User mentions bot (e.g., @BotName how do I reset my password?)
• Message must be at least 30 characters (excluding mentions)
• Bot automatically searches knowledge base
• Returns answer in the same channel

Example:

@BotName I'm getting a connection error when I try to join multiplayer. How can I fix this?

Benefits:

• Natural conversation flow
• No need to remember commands
• Works in any channel where bot has permissions
• Great for quick questions during discussions

3. Instant Help Button

Administrators can deploy persistent help buttons in channels for easy user access:

Setup:

• Requires Manage Channels permission
• Posts customizable message with clickable button
• Opens same modal dialog as /ask command
• Ideal for pinning to help or support channels

Alternative Setup: Use /info command and click “Post Instant Help Button” for quick deployment.

User Experience Flow

When users request help through any method:

1. Searching Message - Bot shows “🕒 Searching for an answer. Please wait…”
2. Answer Found - Displays AI-generated answer with:
   • Customizable introduction message
   • Knowledge base answer
   • Optional footer with additional resources
   • Feedback buttons (thumbs up/down)
3. No Answer Found - Shows customizable “no answer” message directing users to alternative support

Rate Limiting

To prevent spam and manage costs:

Default Limits:

• 10 questions per user per hour
• Limits reset on a rolling hourly basis
• Separate limits for each user

User Experience:

• Clear message when limit reached: “You’ve reached the question limit. Try again in X minutes.”
• Limit doesn’t affect bug reports or suggestions

Adjusting Limits: If default limits don’t fit your community needs, contact support to discuss custom limits for your project.

Message Customization

Customize the support experience through /info → “Customize Messages”:

Available Templates:

• Dialog Title - Customize the modal title for /ask and instant help button
• Answer Introduction - Message shown before the AI answer
• No Answer Message - Displayed when knowledge base can’t help
• Button Label - Customize instant help button text (default: “💡 Get Instant Help”)

Example Customizations:

Dialog Title: "Ask Our AI Assistant"
Answer Intro: "Here's what I found that might help:"
No Answer: "I couldn't find an answer. Please contact support at #help-desk"
Button Label: "🤔 Need Help?"

Feedback and Improvement

All knowledge base interactions include feedback collection:

• Thumbs Up/Down Buttons - Users rate answer helpfulness
• Feedback Tracking - Monitor in BetaHub dashboard
• Gap Detection - Identify missing information
• Continuous Improvement - Add content for frequently asked unanswered questions

View feedback data in your BetaHub dashboard →

Advanced Configuration

Device Information Field

Control device info collection in bug reports:

Options:

• optional - Shows field, users can leave empty
• loose - Required field, no format validation
• strict - Required field with validation
• off - Hide device info field

Minimum Description Length

Set quality standards for bug descriptions:

Suggestion Length Requirements

Control the quality of feature suggestions by setting minimum length requirements:

Benefits:

• Ensures detailed, meaningful suggestions
• Reduces low-quality submissions
• Improves developer understanding of requested features
• Default setting: 70 characters minimum

User Experience:

• Users receive immediate feedback if description is too short
• Clear guidance on minimum requirements
• Validation occurs before BetaHub submission

Thread Mode

Create organized discussions for each bug report:

Benefits:

• Dedicated space for each bug discussion
• File uploads and additional information
• Reduced channel clutter
• Private or public thread options

Thread Channel Configuration

Control which channel is used for creating threads:

Options:

• #channel-name - Use specific channel for all threads
• true - Use first available bug channel (default behavior)
• false or disable - Disable thread mode

Benefits:

• Separate thread discussions from main bug reports channel
• Better organization with dedicated thread space
• Maintains backward compatibility when not configured

Status Display: The /info command shows your thread configuration:

• Explicitly configured: Shows which channel will be used
• Using fallback: Indicates automatic selection from bug channels

Thread Participants

Auto-add team members to bug report threads:

Management:

• Add users: +@user1 @user2
• Remove users: -@user1
• List participants: list
• Clear all: clear

Notification Methods

Control how users are notified about their bug reports:

Options:

• public - Reply in the channel
• dm - Send direct message
• dm_with_fallback - DM first, fallback to channel
• channel - Use dedicated notifications channel

Channel Configuration

Bug Reports Channel

Designate where bug reports are posted:

Support Channels

Add additional support-only channels:

Notifications Channel

Separate channel for bug notifications:

Releases Channel

Announce new releases automatically:

Features:

• Automatic release announcements
• @everyone notifications
• Attached release images
• Auto-updates when releases are edited

Welcome Channel

Send welcome messages to new members:

User Management

Ignored Users

Exclude specific users from automatic detection:

Useful for:

• Excluding other bots
• Filtering out problematic users
• Preventing false positives

Permissions

Only users with Manage Channels permission or server owners can:

• Execute /set and /info commands
• Modify bot configuration
• Access sensitive settings

Message Customization

Available Variables

Customize bot messages using template variables:

User Variables:

• {{user.mention}} - @username mention
• {{user.username}} - Discord username

Bug Report Variables:

• {{issue.title}} - Bug report title
• {{issue.description}} - Full description
• {{issue.priority}} - Priority level
• {{issue.url}} - Link to BetaHub report

Other Variables:

• {{thread_mode}} - Thread mode status
• {{issue.potential_duplicate.url}} - Duplicate bug link

Customization Process

1. Use /info command
2. Click Customize Messages
3. Select message type
4. Edit template with available variables

Integrations

Support Knowledge Base

The Discord bot integrates with BetaHub’s AI-powered Support Knowledge Base to provide instant answers through multiple channels:

Three Ways Users Get Help:

• /ask command - Users open a dialog to ask questions directly
• Bot mentions - Users @mention the bot with their question in any channel
• Instant help buttons - Clickable buttons posted to channels by admins

Automatic responses also work with Listen Mode detection of support requests.

Features:

• AI-powered answers from your documentation
• Feedback collection via thumbs up/down buttons
• Rate limiting to prevent spam
• Fully customizable messages and templates
• Category-based responses (Technical vs Gameplay)
• Canned responses for common questions
• Footer messages with additional resources

Learn about Discord AI support features →

Configure Support Knowledge Base →

Roblox User Verification

Automatically capture Roblox usernames and player IDs when users report bugs. This helps you track which Roblox players are experiencing issues and enables better player-specific debugging.

Supported Verification Services

BetaHub Discord Bot supports two Roblox verification providers:

• Bloxlink - Popular verification service with free and premium tiers
• RoVer - Alternative verification service with reliable API

You can configure either service individually, or enable both for automatic fallback (recommended for maximum reliability).

Setup with Bloxlink

Bloxlink is a widely-used Discord bot that links Discord accounts to Roblox profiles.

Setup Steps:

1. Visit Blox.link Developer Dashboard
2. Create a server key for your Discord server
3. Configure in Discord:
   /set key bloxlink_key value YOUR_SERVER_KEY

Requirements:

• Bloxlink bot installed in your Discord server
• Bloxlink account
• Valid server API key

Setup with RoVer

RoVer is an alternative Roblox verification bot with a robust API.

Setup Steps:

1. Visit the RoVer dashboard and obtain your API key
2. Configure in Discord:
   /set key rover_key value YOUR_API_KEY

Requirements:

• RoVer bot installed in your Discord server
• Valid RoVer API key

Using Multiple Providers (Recommended)

For improved reliability, configure both Bloxlink and RoVer. The bot will automatically handle fallback:

1. Bot attempts to fetch Roblox data from Bloxlink first
2. If Bloxlink returns no data or encounters an error, bot tries RoVer
3. First successful result is used

Setup both providers:

/set bloxlink_key YOUR_BLOXLINK_KEY
/set rover_key YOUR_ROVER_KEY

This ensures maximum uptime - if one service is unavailable, the other serves as backup.

What Information Gets Captured

When a user with a verified Roblox account reports a bug, the following information is automatically added to the bug report:

• Roblox Username - The player’s Roblox display name
• Roblox User ID - Unique numeric identifier for the player

This data appears in the bug report details and helps you:

• Identify which Roblox players are affected
• Track recurring issues from specific accounts
• Provide player-specific support and debugging
• Cross-reference with server logs using Roblox IDs

Disabling Verification

To disable a verification provider:

Troubleshooting

No Roblox data appearing in bug reports:

• Verify users have linked their Discord accounts with Bloxlink or RoVer
• Check that your API key is valid using /info command
• Ensure the verification bot (Bloxlink/RoVer) is installed in your server
• Confirm users have verified their Roblox accounts through the verification bot

API key errors:

• Double-check your API key for typos
• Verify the key is for the correct Discord server
• Regenerate API key if needed from the provider’s dashboard

Integration not working:

• Run /info to verify your integration status
• Test the integration by having a verified user report a bug
• Check that the verification bot has proper permissions in your server

Best Practices

Channel Management

• Enable Slow Mode on bug channels to encourage detailed reports
• Use clear channel descriptions explaining reporting procedures
• Pin instructions for using the bot effectively

Community Guidelines

• Set clear expectations for bug report quality
• Provide examples of good bug reports
• Moderate discussions to stay constructive

Performance Optimization

• Configure ignored users to reduce noise
• Use thread mode to organize discussions
• Set appropriate minimum description lengths

Troubleshooting

Common Issues

Bot Not Responding:

• Check basic permissions (Send Messages, View Channels)
• Verify bot is online and properly invited
• Ensure Discord slash commands are enabled

Can’t Create Threads:

• Verify thread-related permissions
• Check channel-specific permissions
• Confirm bot role hierarchy

Missing Permissions:

• Run /info to check current permissions
• Review role assignments in server settings
• Contact server admin for permission updates

Suggestion Issues:

Project Token Errors:

• “Project not found” - Verify project token is correct using /set project <token>
• “Project not set” - Configure project token before using suggestion features

Suggestion Button Problems:

• Button not responding - Check bot permissions in the channel
• Cannot post button - Ensure Manage Channels permission for admin commands

Validation Failures:

• “Description too short” - Check min_suggestion_length setting (default: 70 characters)
• User guidance unclear - Review minimum length requirements in project settings

Submission Failures:

• BetaHub API errors - Verify project exists and token is valid
• “Processing failed” - Check network connectivity and BetaHub service status

Getting Help

If you encounter issues:

• Use /info to diagnose permission problems
• Check the FAQ for common solutions
• Join our Discord server for support

Next Steps

• Advanced Features - Explore AI-powered capabilities
• Integrations - Connect with external tools
• Core Features - Learn about the platform foundation