That normal, that's when LogMeOut! closes the WoW client. HonorBuddy needs to realize it is really closed (in your case 8 seconds).
From your last log, I can see your player was disconnected because someone followed you.
Thanks for your report. In this case, your log was really useful for me.
In its actual implementation, each time the plugin is "pulsed" by HonorBuddy, LogMeOut! checks the actual position of the player and compares it to the last saved. The time between Pulses are variable and really depends on your other plugins.
Here, I'm pretty sure the action "[ShutUp - AIML]: update FriendsList .." took a while and this is why LogMeOut! thought your player was teleported.
I will change the implementation of this one in my next release to be independent of the Pulse for this trigger, as it needs a real precision.
ZenLulz
Unfortunately, we cannot disconnect a player instantly in the game, unless it's in a sanctuary. This is why all triggers have the same behavior.
When I'm referring "someone following you", it's any player around you. They don't have to target you (the real follow mode is covered under "someone targeting you", as you need to target someone to enable the follow mode).
Is it possible to kill one session for relogger not whole aplication? In case if I have one relogger for couple accounts.
hi lulz why by the B-net wispers not triger any sound only from non frineds thx
ok thxBecause B-net friends are not a part of whats being triggered as a warning and should not be, this is not a trigger mod for chat when your not looking on the character.
It would be a nonsense for LogMeOut! to avoid log out, isn't it?
Also, I don't plan to implement feature related to HBRelog since this program is not safe with the latest version of WoW.