Knowledge Base
Find answers, guides, and tutorials for ShotcallBridge.
Getting Started
1. Choose Your Plan
Decide which plan from our pricing page best fits your needs and features.
2. Prepare Details
Click "Get Started" to open our setup form and provide your server's configuration IDs.
3. Receive Invites
We'll contact you to finalize everything and send your custom bot invite links.
Command Reference
Command | Description |
---|---|
/start | Starts the broadcast from your current voice channel and begins logging attendance. |
/stop | Stops the broadcast and automatically posts the attendance log to the configured channel. |
/status | Shows the current status of the broadcast, including active channels and duration. |
/ping | Checks if the bot is online and reachable. |
/restart | Restarts the entire bot application (Admin only). |
Advanced Features (Pro Tier)
Secure Channel Mode
When enabled, the bot constantly checks who is in the listener channels. If a user without a designated "authorized" role joins a listener channel, the broadcast to that specific channel is automatically muted until the unauthorized user leaves. This prevents sensitive information from being leaked.
Web Dashboard
The web dashboard provides a user-friendly interface to manage all bot settings. Instead of using text commands for configuration, you can use the dashboard to assign speaker/listener channels, manage authorized roles, and view session history.
Attendance Protocol
The attendance log is generated and automatically posted to your configured log channel every time a session is ended with the /stop
command. It's the perfect way to fairly distribute loot or track participation. The output will look similar to this:
Log Types
You can customize the output of the attendance log via the "Attendance Log Type" dropdown in the setup form. The options are:
- Detailed: Only the detailed protocol with all join/leave/move events for every user.
- Summary: Only the TL;DR summary with the total presence time per user.
- Both: The full, detailed protocol followed by the TL;DR summary in one message (as shown above).