Product capability
Commands and aliases
Decide which commands a server offers, where they work, and what staff can type to reach them.
abhi.gg
Public surface
operations context
Dashboardready
Docslinked
Statusclear
$status public-checkServer owner outcome
Fit the command surface to how your staff already talk instead of retraining them on canonical names.
The dashboard and Discord commands complement each other; availability still follows the server plan, enabled modules, Discord permissions, and current service state.
Staff workflow
- 1Open the command catalog
- 2Enable or restrict the command
- 3Add or retire prefix aliases
- 4Save and confirm the recorded change
Supported operations
- Per-command availability
- Channel and category routing
- Custom prefix aliases
- Built-in alias overrides
Verified command examples
Examples are selected from the generated command inventory. The dashboard may also expose workflows that are not command-shaped.
Permission boundaries
- • Manage Server to change command configuration
- • Discord permissions still decide who may run a command
- • Alias capacity follows the package limit
When something is unavailable
- • Alias collisions name the command that already owns the wording
- • Concurrent edits are rejected with a version conflict
- • Reaching the alias limit blocks additions, not edits
Build the workflow
Start with the module your team needs now.
Install Abhi, verify permissions, and enable only the operating areas your server will use.