It's been quite some time since I've seen that message. Back in the earlier days of development of the BerZerker plugin I encountered that issue because MQ2BerZerker was hitting abilities too fast. So I slowed the plugin down to allow it to pass the use of the ability and let it register that it happened. Currently There are two delays built into the main loop of mq2berzerker. One is a pulse delay, and another is a delay based on time itself. The pulse delay is that mq2berzerker should only go through the main loop if it is the 5th pulse of the loop. The timed delay is based on a tick count, which isn't the same as a tick count in game (6 seconds) but rather a large number that ticks quite fast and returns a value in milliseconds with 10 to 16 milliseconds of actual time. There is a global skill reuse timer of 600 milliseconds, to prevent the berzerker from using abilities faster than once every 0.6 seconds which was slowed down from the previous 0.4 seconds.
Now...this is the fastest I could get it to fire off abilities without encountering the message you speak of. Perhaps it is possible that in a raid that there is some additional variance that should be taken into consideration based on the system that is using the plugin, graphical latency/internet connection etc could potentially cause a "backup" where time passes while your computer cannot pulse, or the commands are not sent, and thus once it finishes whatever jitter there may be then it subsequently floods the system with commands and causes the anomaly.
So I think there's some ways that you could attempt to counteract such an issue. First step would be to turn down the graphical settings on your system while raiding. Things like shadows in EQ are not CPU/GPU friendly. If you're limiting your framerates to below the refresh rate of your system then there could be delays cause that way as well because turning down your frame rate can affect the pulse rate (Does not apply to mq2eqwire) I'm referencing the ingame frame limiting tool in advanced options.
You could turn off hero forge, spell particles, new player models, etc.
The other option is I create an option in the INI that allows you to slow the plugin down. However, this should be a last resort as some people enjoy breaking things by altering the INI directly and then complaining about it. I'm looking at you
@kaen01
Users are used to having to edit INI's, and so they tend to go look inside the configuration settings for things to see if there is anything they can change. But manual change of the MQ2BerZerker INI could cause potential issues depending on what you're altering. So I'd start with the above list of things you could alter, and then see if there is an improvement. If not, message me directly so that we can speak about it in detail.
Discord is my preferred method of communication and you'll be able to get immediate notification of my responses, as well as I get a noise when I receive a message.
CWTN