Support Notice Commands And Workflow
Commands And Interactions
| Command / Interaction | Notes |
|---|---|
/tnotice | Detected from command builders, config names, or interaction IDs in source. |
/set | Detected from command builders, config names, or interaction IDs in source. |
/notice | Detected from command builders, config names, or interaction IDs in source. |
/duration | Detected from command builders, config names, or interaction IDs in source. |
/level | Detected from command builders, config names, or interaction IDs in source. |
/view | Detected from command builders, config names, or interaction IDs in source. |
/clear | Detected from command builders, config names, or interaction IDs in source. |
Workflow
- Staff run the notice workflow or the plugin posts the configured notice.
- The bot formats the support state using language strings.
- Updates replace or refresh the notice so one current message remains visible.
- Customers use the notice to decide whether to open a ticket or wait.
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.