I second all the compliments. I read about people getting banned AFK questing, and I wonder how many times this has saved my bacon!
Again, new update. LogMeOut! is now able to detect when the player entering and leaving an instance/battleground/raid, if the player is teleported due to a quest (when accepted) and if the player is teleported by another PNJ for a quest (after opening a Frame to discuss with it). I think I covered the most situations where the payer can be teleported due to the game mechanics, so the trigger is now stable. I also added a new trigger that checks if a specific achievement is completed, in which case, the player is disconnected. Enjoy
I love this plugin "litterly lol". Ive caught my bot getting stuck AFK questing soo many times its not even funny. I finally bumped into this addon and I never get stuck anymore and its even getting better over time.
Thx for this great plugin! I would like to have an extra dismount function, because often my bot got stuck into trees. So instead of Heartstone, first dismount.
No but its almost near the best plugin if you add it, also can you check teleports on zeppelins? i get DC all the time when using the boats
This looks awesome! i love the logout timer! but is there anyway it can log us back in? like play a few hours loggout for a few more then back in??
New update. The trigger that detects the teleportation no longer fires when the player is teleported using a meeting stone and transported by a zeppelin/boat.
Another great update, can you add when using the pay to fly services all around in wow to be ignored by teleport. Also can you add support for eUnstuck method? atm when using eUnstuck your plugin does not count it as consecutive stucks. Link for the plugin. http://www.thebuddyforum.com/honorb...nstuck-omg-new-unstuck-method-not-flying.html Last but not least, is it possible to fix so you can edit LogMeOut settings on the fly, without the need to stop then edit settings and start hb again???. If you dont stop it, you will 100% get an error message and hb will crash instantly. edit... Im having trouble updating, i update logmeout and restarts HB still says theres an update and im on 1.2.8, tried svn and the zip from this thread. Same thing.
As zepenelope said, LogMeOut always triggers a Update and say 1.2.8 => 1.2.9 If you push a Update, the Configuration Files for a Char are getting deleted?
I'd absolutely love to see a log file saved somewhere in the folder, so I could check what made it stop. I'm absolutely positive a lot of people have been wondering whether the but shut down because of a GM, too many stucks or the set time running out. Cheers, great plugin!
When i update the plugin manually or via update function it still shows me that i use 1.2.8. I deleted the Folder in Plugins and copied it from the zip... but still 1.2.8. Please fix it, that the teleport function will not log you out, when u die and got teleported to the Spirit Healer. I use the 100 yard setting, i can set it to 1000 yard but well thats not ideal. It would be nice if the plugin suppports the eUnstuck plugin. But well. Thx for the nice plugin.
Please please please add in the option to dismount if not moved for x time. So many times i get stuck under buildings and trees etc and there is no work around. Atm logmeout needs to be on the ground before it does anything. Just a simple dismount before action would fix this. Please please please <3!
Everyone, thanks for reporting the update issue. The bug is now fixed, I invite you to perform an update for the last time. @zepenelope: Thanks for your suggestions. I'm going to have a look about eStuck detection. Concerning the teleportation on taxi, did you experience some issues ? I could add it, but I need to be sure it's really necessary as each critter "slows down" LogMeOut! a little bit more. At the beginning, we could change the settings on the fly. I will inquire why it's no longer possible. @tumbum: The system that manages the save of the settings is written by the HonorBuddy developers. When I add/change the settings in LogMeOut!, the system is enough clever to just add the new property to the configuration file, but unfortunately, it may occurs the file cannot be just "updated". @andric1: The reason of the log out can be reviewed in the log file in your folder /Logs. This information is also available the next time you launch HonorBuddy with the same player LogMeOut! disconnected. @Xolotl: This should be no longer the case since the version 1.2.7 of LogMeOut!. Try this last one, and report here with a log if you still encountering the problem. @Mydruid: Unfortunately, when LogMeOut! is performing the Action before, the log out process is already engaged.
Yeah sometimes it will detect taxi as teleport same with deaths and spiritguards, sometimes it will detect it as teleport too. So it might not check 100% in some cases or?, also the teleport circels at Deathknights home when going to runeforge your weapon gets detected as teleport.