VIP Commands And Workflow
Commands And Interactions
| Command / Interaction | Notes |
|---|---|
/vip | Detected from command builders, config names, or interaction IDs in source. |
/vipmanage | Detected from command builders, config names, or interaction IDs in source. |
/give | Detected from command builders, config names, or interaction IDs in source. |
/user | Detected from command builders, config names, or interaction IDs in source. |
/duration | Detected from command builders, config names, or interaction IDs in source. |
/unit | Detected from command builders, config names, or interaction IDs in source. |
/remove | Detected from command builders, config names, or interaction IDs in source. |
/removebyid | Detected from command builders, config names, or interaction IDs in source. |
/userid | Detected from command builders, config names, or interaction IDs in source. |
/list | Detected from command builders, config names, or interaction IDs in source. |
/page | Detected from command builders, config names, or interaction IDs in source. |
/rolelist | Detected from command builders, config names, or interaction IDs in source. |
Workflow
- Staff manage VIP status through configured commands or config-backed actions.
- The plugin applies configured roles or perks.
- Members receive VIP responses or access based on their state.
- Logs or language strings explain success and failure states.
Expected Discord Behavior
- The bot should respond only in channels where it has the needed view, send, embed, attach, or role-management permissions.
- User-facing messages come from the language config when one exists.
- Staff-only actions should be protected by the plugin permission settings and AthenaBot role permissions.