Family Tree Commands And Workflow
Commands And Interactions
| Command / Interaction | Notes |
|---|---|
/adopt | Detected from command builders, config names, or interaction IDs in source. |
/user | Detected from command builders, config names, or interaction IDs in source. |
/children | Detected from command builders, config names, or interaction IDs in source. |
/disown | Detected from command builders, config names, or interaction IDs in source. |
/child | Detected from command builders, config names, or interaction IDs in source. |
/divorce | Detected from command builders, config names, or interaction IDs in source. |
/spouse | Detected from command builders, config names, or interaction IDs in source. |
/familysize | Detected from command builders, config names, or interaction IDs in source. |
/forceadopt | Detected from command builders, config names, or interaction IDs in source. |
/parent | Detected from command builders, config names, or interaction IDs in source. |
/forcedisown | Detected from command builders, config names, or interaction IDs in source. |
/forcedivorce | Detected from command builders, config names, or interaction IDs in source. |
Workflow
- A member starts a relationship action with another member.
- The target accepts or rejects when the flow requires confirmation.
- The plugin stores the relationship and updates the family tree.
- Members can view their own tree or another member tree through commands.
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.