[Plugin] LogMeOut! - A World of Warcraft disconnecter !

Is it normal for this plugin to grey out the stop button?

Edit: It only does this with the beta version of HB. It works fine with release.

 

Hi there,

@prolifik: The plugin must be located within the folder Plugins/LogMeOut in your HonorBuddy installation.

@kris411: It would be great if you post a full log with the issue.

@Keldorn: Each time a trigger raises, a beep is emitted. In the case you enabled the stuck trigger, a beep is emitted each time HonorBuddy sends a stuck event.

@B00sted: For the trigger Spend some time in combat, the time is per mob. Each time the combat is finished, the timer is reset. If you are encountering this issue one more time, please join a full log.

@tumbum: Thanks for the report. I will perform some tests to improve the trigger.

@SomeBodyElse: Thanks for your log. Apparently, BuddyManager restarts HB (perform a stop/start). This is why Time Elapsed trigger is reset to its full duration. Unfortunately, there is nothing to do as this is the normal behavior of the plugin.

@jeremytyler662: LogMeOut! does not change the state of the stop/start button.

 

Thanks for your answer.
what i mean is, it would be very cool if you could implement a feature that allows the user to DISABLE the beep for each setting e.g. i want to disable beep for stucking triggers.
Just a feature request.

anyway THIS is one of the BEST plugins available here.

Greetings

 

Yes there is!

 

I know there is a "Kill HBRelog/ARLog option" but I don't want to stop my other toons, is there a way to just have LogMeOut make HBRelog cycle to the next task?

I'm trying to setup something similar to:
HBRelog starts up farmer account, which has LogMeOut running with a timer set for 3hrs. Once 3hr window is hit, LogMeOut is set to hearth, which it then exists the game client. But HBRelog still has the "Wait" task running, since it is hard to line them up perfectly, and brings the client back thinking it's crashed, and starts HB all over again with the 3hr timer on LogMeOut, but with time still on the HBRelog task. That task ends, and starts my "Idle" task, which has the game client logout wherever it is.

I'm trying to avoid having my toons just exiting without hearthing when running a combo of a relogger and LogMeOut.

 

Check the box, the first field is the number of times you want to loot the item and the second field is the actual item id (can get from wowhead.com).

 

What would be the luascript for LogMeOut to do this before disconnecting:
Leave the dungeon(instance) or teleport out of instance?

 

Possible to tigger a Logout for this kind of Situation? http://www.thebuddyforum.com/releases/140098-honorbuddy-v2-5-8690-707-a-4.html#post1333708

 

Indeed, happens to me to. Have to restart HB etc over and over again. Until this is fixed I really can't use logmeout :/

 

Looks like there is a Problem with LogMeOut. Stuck Count was set to 10. But my Toon was on 18 and i stopped HB.

Log starts at:

 

[LogMeOut!]: Stuck detected (X="-9465.888" Y="-1322.632" Z="44.79869"). Number of consecutive stuck : 4/20

Why do I constantly get stuck using HB I get logged out alot.

 

Does anyone know if its possible to change the sound of stuck alert since it happens so frequently now its annoying since i have to alt tab every 5 mins to make sure it isn't something else

 

Thanks so much for this brilliant plug-in! It's so nice. I wondered if I could make a small feature request; when running DungeonBuddy for example, I'd like it to log-out if the other bot suddenly drops group, so that it doesn't queue and attract real players. Any advice so solve it another way is also welcome. Thanks again for your great work.

 

Hi, there - just found your plugin and can tell it will be a lifesaver. I was recently farming for some rep afk when I noticed somebody had been chatting with me while I was afk. They weren't whispering, they were "saying." And I of course never responded because I was afk. Is there a way to create a trigger to log off if another player starts talking anywhere near my bot? Or pause for a little while?

 

Good news, I renewed my WoW subscription. I'm going to test this too-sensitive stuck trigger.

@wizardslayer: LogMeOut! actually can't communicate with reloggers, unfortunately. Nevertheless, I never used one, so I'm probably not the best person to ask for. Maybe someone else who already dealt with them can answer you.

@Macatho: Be default, the plugin keeps your character in the instance/battleground when a trigger raises. This behavior can be overrided in the Exception tab by unchecking the options called During an instance and During a battleground.

@tumbum: I added your idea to the wish list. Concerning your second issue (stuck), LogMeOut! waits that your character respawns. In the case he's stuck while he's a ghost, there's a timeout of 3 minutes after which WoW is exited. You can override this behavior by checking the exception Don't run to corpse when logging out.

@Macatho: Is it a stable version of HonorBuddy and are you using other plugins? LogMeOut! doesn't interact with the stop/start button.

@Sven: You can replace the the file beep.wav by your own. However, you have to replace it after each update of the plugin. The sound file is played twice.

@Kaelhoel: Do you mean detecting as soon as a member of the group leaves, because your group is full of bots ?

@Ragoza: The main problem in this situation is that there will be a lot of false-positive.

 

Some updates here. I pushed a new release to fix the too-sensitive stuck trigger. With the current implementation of this system in HonorBuddy, the trigger also catches stucks while the character is flying.

Also a clarification about the whisper trigger, it does not raise when a Battle.Net friend is whispering you.

[Changelog]

Code:

[FONT=Courier New]
[B]1.2.13[/B]  

[LIST]
[*]The trigger "X consecutive stucks" is no longer spammed, a delay of 6 seconds was added between stucking event
[*]The Trigger "X whispers received" only notify whispers when enabled
[/LIST][/FONT]

The update will be quickly available in the built-in update system.

Happy botting

 

In the exception list it lists being in an instance. What if we use dungeon buddy and want to log out if we're stuck/don't do anything/etc.? Will it work?

 

Great plugin! Is there anyway i can se why i got logged out? etc if a gm whisperd me i got stuck etc?

 

A good suggestion, for gathering profiles. I like to have Inactive Since really low, like 1-2 minutes. But if the player has Deserter, then the bot is AFK for 10minutes. Can you add an exception to not log out if the player has the debuff?

I want to keep it logging out at 1-2minutes inactive, EXCEPT when it has Deserter on the player. having to change it to 11minutes is just too long >_>

 

This morning, I got up and checked my Char to see if I got my bugs full of Ore and Herb and such, but it wasn't full. I checked the logs, and apparently for the last 10-20 mins It was fighting someone, then I saw this:

[05:09:14.145 N] I died!
[05:09:14.208 D] Activity: Releasing from corpse
[05:09:15.563 N] [LogMeOut!]: Starting logout process...
[05:09:15.563 N] [LogMeOut!]: Reason : The player was moved for about 318.7522 yards. Previous position: <2888.886, -971.0193, 256.2411>; Actual position: <2966.556, -662.783, 232.5589>
[05:09:15.563 N] [LogMeOut!]: The character is dead. Waiting respawn...

Did it LogMeOut because I got teleported over to the graveyard from clicking release spirit too quickly? Just would like to know.

Thanks!