You are not correctly understanding the current behavior. With the current behavior, when you unpause a timer, the command will only be executed if the full delay has transpired since the previous time that the timer's command was executed. It will never execute more than once immediately after an unpause.
Yes I am, when I said "if I get it right", I was talking about how you would use timers in your /play example, I thought you would have one timer per line and that you would pause them all once +m is set.
What I just quoted from you is true but isn't the reason of my report, unpausing a timer works correctly, pausing a timer doesn't (imo) : the delay doesn't stop decreasing.
Now maybe it's not a bug and all I need is a new switch, but I would be surprised if Khaled implemented it this way on purpose.
If your purpose is to ensure that the timer's command is never executed within 10 seconds of the previous time it was executed, this is good behavior.
This wouldn't be a problem if the delay wasn't decreasing
