Members mark themselves away with a command and a reason. The next message they send clears it and says how long they were gone, and anyone who pings them meanwhile gets told they are AFK and since when. Reading another member's AFK state is what the third rule demonstrates. Note: a returning message that itself contains the AFK command is not treated as a return.
The trigger and the actions it runs. Values in grey are what you'll pick when installing.
{user.mention} is now AFK: {vars.reason}{message.content} does not contain AFK command — otherwise the rule stops here{vars.afk.exists} is true{user.mention} — you were away {vars.afk.value:relative}{mentions.first.id} is set — otherwise the rule stops here{mentions.first.id}{mentions.first.id}{vars.their_reason.exists} is true{mentions.first.mention} is AFK: {vars.their_reason.value} — since {vars.their_since.value:relative}What members type to go AFK. Keep it short and unlikely to appear in normal chat.