You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a really common pattern for users (myself included) who have previously done .bomboff to:
.bomb nick
get rebuffed by the bot: Try again when you're bombable yourself
.bombon
.bomb nick again
Instead of this dance, would it make sense to just automatically perform an internal .bombon if an unbombable user bombs someone else? It would certainly reduce the boilerplate spam in channels where this module is used…
The automatic .bombon can be silent, send a NOTICE to the bomber, or send a public channel message; I'm not really bothered which at the moment. It can also be combined with the NOTICE already sent containing the wire color.
Also thinking about automatically running .bomboff again after the timeout elapses, but that'll be a separate feature if it even happens at all. That might make it too easy to stay unbombable most of the time while still bombing other users at will.
The text was updated successfully, but these errors were encountered:
It's a really common pattern for users (myself included) who have previously done
.bomboff
to:.bomb nick
Try again when you're bombable yourself
.bombon
.bomb nick
againInstead of this dance, would it make sense to just automatically perform an internal
.bombon
if an unbombable user bombs someone else? It would certainly reduce the boilerplate spam in channels where this module is used…The automatic
.bombon
can be silent, send a NOTICE to the bomber, or send a public channel message; I'm not really bothered which at the moment. It can also be combined with the NOTICE already sent containing the wire color.Also thinking about automatically running
.bomboff
again after the timeout elapses, but that'll be a separate feature if it even happens at all. That might make it too easy to stay unbombable most of the time while still bombing other users at will.The text was updated successfully, but these errors were encountered: