Yes, well, pkick works best for these kinda people, but also you can tell them
to do delay to their rip_action. For exsample ~@~@rip_action set grep -q
vyhasf ivyasf<delim>grep -q vyhasf ivyasf<delim>barb burn

Amd LORD hates autolooters too.

I've been annoyed, when leading, that my rip_action wasn't executed first in
the party (another party member's was).. would be nice if leader action,
followed by their 'next' was always done first before others in the party. It
seems kinda random whose goes off first.

I have done this as well in the past. The real problem is that the rip_action
command doesn't properly allow you to control order. Despite using the next
command and trying to set up the proper order it is still impossible in some
cases for the leader to go first, so the barb who is burning needs to add
something to his rip_action to delay it (grep makes the most sense since it
works effectively and doesn't create any additional spam for the user).

The issue of the "idle" barb makes no difference if that person is idle or
actively participating, the point that matters is that the leader can't have
their rip_action come first and this should be addressed or people will
continue to find hackish ways around this like the grep fix.

Val