What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

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

Hey,

After some tests, I've encountered the stuck issue... I have to figure out how to detect it (since the Debug log disappeared, I cannot use the old way). Just turn this trigger off for the moment.

I'm also aware LogMeOut! does not kill WoW correctly.

I'm going to fix these problems at the end of the week.
Suggested Feature:

Logout when professions reach (x) skill level


i.e Logout when Mining reaches level 75
 
Here's another suggestion:

Don't really log me out, but beep the fuck out until you notice that I'm beeping!

:-)
 
[LogMeOut!]: Started successfully !
[LogMeOut!]: -------------------------------------------------
[LogMeOut!]: The bot will stop on the following triggers :
[LogMeOut!]: + On Stucks (30 max)
[LogMeOut!]: + On whispes received (15 max)
[LogMeOut!]: + On 4000 Honor points reached
[LogMeOut!]: -------------------------------------------------
[BGBuddy]: Queueing up for WSG
[LogMeOut!]: Stuck detected. Number of consecutive stuck : 1/30

etc

Bot just waiting for BG invite and stand still.

Disable the stuck trigger until a new version will be out.
 
Is there anyway to provide a check when your at a mailbox not to check if people are following you? Being logged out after 1 full bags makes me sad panda. Otherwise great plugin! Good work
 
is it posible to make a triger that kiles wow if no ton movement detected for x amount of time.?
 
The plugin is being too aggressive on forcing a WoW client to shut down. It doesn't even allow the process to save it's addon settings, every forced shut-down will corrupt at least one of my addon's saved variables.
 
I pushed an update that grow the max level in the Level trigger and disabled the stuck trigger until I find a correct solution.

The plugin is being too aggressive on forcing a WoW client to shut down. It doesn't even allow the process to save it's addon settings, every forced shut-down will corrupt at least one of my addon's saved variables.

Normally, you don't have to have plugin loaded with HB :D I execute a Lua /forcequit at the end. don't know if there is a cleaner method do to that.

is it posible to make a triger that kiles wow if no ton movement detected for x amount of time.?

There is a built in function in the HB settings for that :)

Does the whisper feature work for BattleTag friends too?

Honestly I think but i'm not sure.
 
I don't know if this is possible but I have a suggestion for an additional log out call..

Log out at a certain amount of item gathered. Require that the user gets the item ID number off wowhead and puts it in the field and the desired amount to log out at. I do not know if this is possible and if logmeout would be able to scan inventory for the item ID but it just just a suggestion I thought of while farming mats to level blacksmithing and engineering, being able to tell logmeout to trigger a log off after 600 Mirthril ore are gathered would be awesome that way I am not out there longer than need be. Just a suggestion but love your plugin and all the great work you have always done with it.
 
I don't know if this is possible but I have a suggestion for an additional log out call..

Log out at a certain amount of item gathered. Require that the user gets the item ID number off wowhead and puts it in the field and the desired amount to log out at. I do not know if this is possible and if logmeout would be able to scan inventory for the item ID but it just just a suggestion I thought of while farming mats to level blacksmithing and engineering, being able to tell logmeout to trigger a log off after 600 Mirthril ore are gathered would be awesome that way I am not out there longer than need be. Just a suggestion but love your plugin and all the great work you have always done with it.

Yes it's possible and this is a good suggestion ;)
 
The stuck trigger and cannot loot trigger have been disabled due to an event issue in HB
What is the event issue in HB? If I enable the stuck trigger, will something bad happen? :o
 
What is the event issue in HB? If I enable the stuck trigger, will something bad happen? :o

Finally I just make something wrong when I parsed the log of HB. Actually, LogMeOut! doesn't detect the stuck well.
To prevent that, you cannot activate it in the latest version to avoid a bad behaviour.

It will be fixed shortly.
 
It is possible an option for a certain number of minutes in the same place to create? whom virtually no longer responds questbot
 
Any Update for the Stuck Stigger? I think the last time i used this Option my Toon was going crazy all the time to unstuck himself, but there wasnt anything to unstuck. Someone told me to deactivate it till you pushed a fixed.
 
@tumbum: Yes ! I've planned an update that fixed this issue and add 4 new triggers in the evening ! :)

@Skadusch, @jchiera : I'm sorry but I don't understand what you're talking about. :/
 
LogMeOut! 1.2.2 is deployed !

Many new features inside this last version.
Firstly, I managed to fix the issue with the stuck and cannot loot triggers.I added 4 new triggers :

  • Quit on loot : You can specify a number of a specific item to loot
  • Quit on Aura : detect if the player received a specific aura
  • Quit on training skill : Detect if a profession reaches a level
  • Quit on durability : Check if the player's durability is not under x%

After so many requests, I finally implemented a function that don't log out the character when a trigger fired.

Also, LogMeOut! now shutdowns WoW gracefully ! (with the 20sec timer)

I hope you will like this update :P

Zen
 
D'oh ! I forgot to annouce a new exception too.

LogMeOut! can detect if a mailbox is nearby the player and allow you to avoid a disconnection. :)
 
Back
Top