Event System Commands And Workflow
Commands And Interactions
| Command / Interaction | Notes |
|---|---|
/event | Detected from command builders, config names, or interaction IDs in source. |
/create | Detected from command builders, config names, or interaction IDs in source. |
/manage | Detected from command builders, config names, or interaction IDs in source. |
/cancel | Detected from command builders, config names, or interaction IDs in source. |
/id | Detected from command builders, config names, or interaction IDs in source. |
/reason | Detected from command builders, config names, or interaction IDs in source. |
/list | Detected from command builders, config names, or interaction IDs in source. |
/test | Detected from command builders, config names, or interaction IDs in source. |
/type | Detected from command builders, config names, or interaction IDs in source. |
/info | Detected from command builders, config names, or interaction IDs in source. |
/duplicate | Detected from command builders, config names, or interaction IDs in source. |
/save_template | Detected from command builders, config names, or interaction IDs in source. |
Workflow
- Staff create an event through the configured command or workflow.
- The plugin posts event details using configured language strings.
- Members interact with the event according to the available controls.
- Staff manage or close the event when it ends.
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.