Automatic detection
The bot bridge reports the modules and guilds the runtime can actually serve.
Bot Modules
A control panel for every module your bot exposes.
BotForge reads the bot manifest, detects available modules and gives each one a clean configuration surface with health, logs and runtime status.
The operational problem
Discord bot capabilities often become difficult to discover and maintain once multiple bots and servers are involved. BotForge keeps each detected module attached to its owning bot and exposes the correct admin panel.
What the module controls
Every capability below maps to the existing BotForge and Discord workflow.
Dedicated admin panels
Complex modules open their own configuration surfaces instead of a generic placeholder.
Health and logs
Online state, sync freshness, activity and permission warnings remain visible.
Bot attribution
The module list shows which connected bot owns every capability.
Workflow
A predictable sequence keeps administrators and members aligned.
- 01Bot sends its manifest
- 02BotForge validates the workspace and guild
- 03Administrator opens the module panel
- 04Configuration and runtime state remain synchronized
Permissions and plan availability
Required access
Authenticated Discord workspace access
Owner or administrator rights for configuration
Viewer access remains read-only
Plan availability
Availability depends on the real module entitlement
Access remains enforced by the existing server-side entitlement and permission services.
Compare plansQuestions
Can two bots expose a module with the same name?
Yes. BotForge keeps the bot identifier in the module projection so each panel opens against the correct runtime.
What happens if a bot goes offline?
Saved configuration remains available while runtime health and stale-sync states show that live actions may be unavailable.