Dispatch.IO doesn't only answer commands: it reacts to Fluxer events (a member joins, a message is sent, a reaction is added…) and to what is saved on the dashboard. This page lists these automatic reactions, in the order the bot handles them.
Every Fluxer event
What the bot does on each event.
| Fluxer event | What the bot does |
|---|---|
| The bot joins a community | Creates its settings (first time) or finds them again, and marks it active on the website |
| The bot leaves a community | Marks it missing on the website (settings kept), turns the aviation pack off |
| A member joins | Logs, anti-raid, captcha, welcome and welcome roles |
| A member leaves | Logs, goodbye message |
| A message is sent | See Each message sent |
| A message is edited or deleted | Message logs, anti-raid filters on edits |
| A reaction is added or removed | The "buttons" of the bot's messages: roles, tickets, giveaways, polls, suggestions, music player, pages, confirmations |
| Voice activity | Temporary voice channels, voice XP, flames, voice logs, music stopped when the bot's channel is empty |
| Channel, role, community, emoji, webhook or invite changed | Server category logs |
| Member changed (nickname, roles, timeout, avatar) | Member logs |
A member joins
The steps, in order.
- Join logs and invite used.
- Raid mode: a Dispatch.IO blacklisted account is reported to the staff.
- Join anti-raid: bot added, mass joins, too recent account. A kicked member stops there.
- Captcha, if on: the member must type the code.
- Welcome message (and a direct message with a custom message), then welcome roles.
Details are on Welcome and goodbye and Anti-raid and security.
Each message sent
The order of the modules.
For each message, the bot goes through this order:
A message deleted by the anti-raid gives neither XP nor a flame. Dispatch.IO blacklisted accounts trigger neither word reactions nor XP.
Reactions
Reactions are Dispatch.IO's "buttons" on Fluxer. When you react to a bot message, it finds what the emoji stands for (role, ticket, vote, page…), checks that you are allowed, does the action then, depending on the case, removes your reaction so the button stays clickable. See Buttons, forms and replies on Fluxer.
Voice activity
- Joining a voice hub: the bot creates the member's temporary channel and moves them into it.
- Leaving a temporary channel: owner change, or deletion 5 seconds after the last member leaves.
- Being in voice: voice XP every minute, day's flame validated.
- Leaving the bot's channel: once no member is left there, the music or radio stops and the bot leaves the channel (see Music player).
- Voice logs: connections, disconnections, channel switches, mic, sound, camera and screen share.
What the website sends to the bot
What changes on the bot when you save on the dashboard.
| Website page | What the bot does | Log |
|---|---|---|
| Any configuration page | Reloads the changed settings | Yes, in the Server logs channel |
| Welcome and goodbye (test) | Sends the real test message | No |
| Tickets (configuration) | Posts, updates or deletes the panel | Yes |
| Reaction roles | Posts or edits the panel, its legend and its reactions | Yes |
| Ticket handling | Sends, edits or deletes messages, closes, reopens, claims, renames, saves; applies the requested sanctions | Depending on the action |
| Message studio | Sends, edits or schedules messages (as embeds on Fluxer) | No |
Bot forms (/form/…) | Receives your answers and does the requested action | Depending on the command |
| Social networks, RSS (Check & send) | Runs an immediate check | No |
Changes reach the bot within seconds, without a restart. See Synchronisation with the bot.
What the bot sends back to the website
- Its presence in each community (Bot active / Bot missing).
- Its state for the website's status page (every 15 seconds) and its statistics (communities, members, commands).
- The dashboard's card previews (welcome, level, flame, bump), drawn by the bot itself.
- The live follow-up of tickets (new messages, state changes).