Translator Commands And Workflow
Commands And Interactions
| Command / Interaction | Notes |
|---|---|
/translate | Detected from command builders, config names, or interaction IDs in source. |
/text | Detected from command builders, config names, or interaction IDs in source. |
/to | Detected from command builders, config names, or interaction IDs in source. |
/from | Detected from command builders, config names, or interaction IDs in source. |
/auto | Detected from command builders, config names, or interaction IDs in source. |
/user1 | Detected from command builders, config names, or interaction IDs in source. |
/language1 | Detected from command builders, config names, or interaction IDs in source. |
/user2 | Detected from command builders, config names, or interaction IDs in source. |
/language2 | Detected from command builders, config names, or interaction IDs in source. |
/stop | Detected from command builders, config names, or interaction IDs in source. |
Workflow
- A user runs the translator command with text and language options.
- The plugin validates input and requests translation through the configured provider or library.
- The translated result is posted in Discord.
- Errors are returned through language-configured messages.
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.