flows
a flow is arii doing something on its own when something happens, with no code: when someone joins, if they have no avatar, send them a dm. you build it from steps in the flows tab of a server.
how a flow reads
every flow starts with a trigger (someone joins, a message says a word, a button is pressed), can pass checks (only people with a role, only at night) and does actions (send a message, give a role, wait a while). paths can split, loop over a list, wait, or pick at random.
every flow also reads as a sentence, so you can check it at a glance. flow steps lists every trigger, check and action.
custom commands
a custom command is a flow too, made with a simple form: its name and other names, how it matches, what it answers, who may use it, and how long to wait between uses. for anything more, open the steps behind it in the flow editor.
recipes
- a role after a wait: trigger someone joins → wait 10 minutes → give or take roles.
- an auto-reply: trigger a message is sent, with words like "rules" → send a message, replying with your rules.
- a role button: in the message builder, a button that gives a role, and takes it back on a second press.
- a night-time touch: trigger a message is sent → check at certain times, midnight to 7 → react with 🌙.
when something goes wrong
the flow editor checks a flow as you build it and points at the step that needs a look. each run is kept for a while, with what every step did, so you can see why one stopped.