Doesn't detect stucks in build 655? I sent you a donation! get to work lmao.. donate to this guy, youd be banned without him.
I love the concept of this plugin. It really is amazing. I have a few questions; however. Currently my bot is getting "stuck" running in a corner and I had used your plugin to hearth him out; however, when he gets stuck running in a corner over and over again (behind an instance) it seems it doesn't hearth/log out. Does the "inactivity logout" not work if he is constantly running in a corner? Thanks in advanced
Okay, found some hours to work on LogMeOut!. I published the release 1.2.11 with some bugfixes and a new exception. Here is the changelog : Code: [FONT=Courier New] [B]1.2.11[/B] [LIST] [*]The trigger Loot x items is now in the correct section [*]The trigger "Quit on teleportation" won't detect anymore when the player is standing next to a quest giver and is teleported [*]The trigger "Quit on teleportation" won't detect anymore when the player is transported by a Zepplin [*]The trigger "Quit on teleportation" won't detect anymore when the player is teleported by the NPC "The Uncrashable" (Id: 48708) [*]Don't run to corpse when logging out exception added [*]When a whisper is received, it explicitly indicates if the sender was a GM [*]No longer try to cast the hearthstone at the graveyard when the player is dead [*]No longer displays a negative timer when the trigger "Quit on time" is enabled and the plugin is disabled after the user started the bot [/LIST] [/FONT] I could reproduce the bug with the negative timer when I disabled the plugin when HonorBuddy was working. I don't know if it was this situation that caused your issue, but I fixed that. The plugin now should correctly handles the Zepplin ! When someone whispers you, it displays if this person is a GM (or not !). And finally, you can check an exception if you don't when LogMeOut! seeks the corpse of your character when he dies and a trigger was activated. @Nexic: The trigger called "inactivity logout" does not signal when your character is moving. Your stuck issue should be handled by the HonorBuddy stuck detection :s
Great plugin!! use it quite often But it would be great if you add a function that he would logout if a certain XP % isn't reached within the hour... For example logout if xp per hour is less then 25% per level... the main problem is that the xp/hour of honorbuddy itself is fluctuating alot if the toon moves from area to another
You have an option that will not allow logouts if near mailbox. Is it possible to add an option that will prevent logouts if on a transport?
@Foba: The percent your get per hour really depends on what is your level and what your character is doing, making very hard for users to use it correctly. What's more, you pointed an issue using this kind of trigger. If the bot performs some additional but necessary tasks that don't give XP, the trigger will be activated. Maybe your trouble can be detected differently. What behavior do you want to detect ? @Jacan: Yes, it is. Are you encountering a problem with a trigger while you are on a taxi ?
The problem is people target you the entire time while on a boat or waiting for it. I cant increase the wait timer for player targeting or else it would be useless.
Well for me its more a AFK safety... i tend to keep my pc running when i am away(it's not a great idea.. but that's another issue) ... so it's more a "if you can't reach X% amount of xp/hour stop" since it doesn't pay off to keep it running without me watching the toon. I ment a function that you can log it of if it doesn't reach the bare minimum of X xp/hour. For example: 200%xp per hour on lvl 1 and scale it to 15%xp per hour on level 90 (that's with heirlooms). Doesn't matter what the issue was.. if it can't reach that.. stop... then i can look into it when i get back... (maybe it's just a flight skill that he needs to get or w/e) ...rather safe than sorry I think it would be usefull... but if i am the only one who thinks this way.. well then it's not worth your time
This is one of my favorite plugins. Would it be possible to implement a function to log out after x number runs in a dungeon or a battleground?
Could this plugin be updated please, its not detecting stucks and whispers for me since patch 5.4 and ive barely botted because of it. I got 2 whispers while alt tabbed because of being stuck in a leveling zone and didn't respond for 20 mins whereas usually i get on it immediately after i get the warning noise.
Thanks for the report guys. Can someone of you throw me a log when a stuck is not correctly handled by LogMeOut! ? Would be helpful to solve the issue.
Good plugin pal but can you log me out when this happens: Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Mounting: Spectral Gryphon Bot keeps trying to mount under some rock/tree or something. Can you add the option to log me off when this constantly mounting happens one after another?
Here's my log from a few days ago, i tried doing a fresh download of honorbuddy and logmeout but it still wouldn't detect stucks. I'm surprised that not allot of people are being bothered by this, i wouldn't even think of botting without logmeout, i cant alt tab while questing without worrying if its stuck.. and afking is completely out of the question. I had to connect a 2nd monitor to watch the bot while questing which is bothersome.
Thanks for the log Sven. A quick question though: are you using a custom stucking handler or something ? If this is not the case, HonorBuddy writes a new message in the log "We are stuck!!". I will deploy a patch when I have time. Cheers
Yeah sorry, i was trying out a new unstuck plugin at that time but removed it and don't use that anymore but i still get the same error. and as i said i tried a fresh install of honorbuddy and logmeout but it still didn't work, its probably a problem with honorbuddy's new unstuck system since patch 5.4