[Plugin] LogMeOut! - A World of Warcraft disconnecter !
- Thread starter ZenLulz
- Start date
Teveel
Active Member
- Joined
- Sep 5, 2011
- Messages
- 2,144
- Reaction score
- 8
As a quick fix, open LogMeOut.cs and try to replace:
Code:InactivityDetector.ForceLogout(false); With: Lua.DoString("Logout()"); And InactivityDetector.ForceLogout(true); With: Lua.DoString("ForceQuit()");
I would post a edited file, but since this addon is still supported by its creator i'd rather not risk stepping on any toes. If abit of search+replacing inside LogMeOut.cs is too much for you, revert back to old hb until an official fix is released
Im unable to test this fix from where i'm at atm, so I haven't been able to verify it yet. GL
Nice one thanks.
As a quick fix, open LogMeOut.cs and try to replace:
Code:InactivityDetector.ForceLogout(false); With: Lua.DoString("Logout()"); And InactivityDetector.ForceLogout(true); With: Lua.DoString("ForceQuit()");
I would post a edited file, but since this addon is still supported by its creator i'd rather not risk stepping on any toes. If abit of search+replacing inside LogMeOut.cs is too much for you, revert back to old hb until an official fix is released
Im unable to test this fix from where i'm at atm, so I haven't been able to verify it yet. GL
This does the trick, thanks a lot !
Frana
New Member
- Joined
- May 5, 2012
- Messages
- 25
- Reaction score
- 0
As a quick fix, open LogMeOut.cs and try to replace:
Code:InactivityDetector.ForceLogout(false); With: Lua.DoString("Logout()"); And InactivityDetector.ForceLogout(true); With: Lua.DoString("ForceQuit()");
I would post a edited file, but since this addon is still supported by its creator i'd rather not risk stepping on any toes. If abit of search+replacing inside LogMeOut.cs is too much for you, revert back to old hb until an official fix is released
Im unable to test this fix from where i'm at atm, so I haven't been able to verify it yet. GL
It used for?
Because since the last update of Honorbuddy, LogMeOut no longer works even with SVN Update :/. LogMeOut no longer appears in the list of plugins
.
ZenLulz
Community Developer
- Joined
- Aug 17, 2011
- Messages
- 583
- Reaction score
- 98
Awwwh ! LogMeOut! is broken !
Seems the community is faster than me ! The changes recommended by Madman were correct (thanks to him). Bossland removed a function I used to perform the log out, so the LUA action must be manually sent. The new version of LogMeOut! was uploaded in the first post/on svn.
There is a lot of message since my last activity, so I'm trying to answer to all of you.
@stulee: No, it won't log out in the instance if you are stuck and if you checked the exception.
@risbonden: During the next launch on the bot, you can read a message explaining why you get disconnected the last time.
@RawrBlargh: Yeah sounds great. I add that in the idea of upcoming features.
@iPwnedUDude: There is a check to prevent that but it seems that HonorBuddy released your corpse to quickly. Let me know if you are still encountering the issue. That should be a rare case.
@HBL0V3: Please, provide a full log the next time. Your character was probably dead and HonorBuddy waited the respawn. To avoid this issue, you can check the exception Don't run to corpse.
@meoww: Sorry, I'm not sure to see the relation with your issue and the plugin.
@Kaelhoel: Could be nice. I add that in the list of ideas of upcoming features.
@kpow: There is an option in the tab Action After.
@magesticschu: I also really like this idea. Added in the upcoming features list !
@rawrasaurus: LogMeOut! was waiting that your character respawns. To avoid this issue, you can check the exception Don't run to corpse.
@BotOperator: Good idea, also added in the list.
@yanshu: Please post a full log of your issue.
@tumbum: Same, a full log please !
@User0828: LogMeOut! didn't have the time to log out your character after that the hearthstone was casted, but the next time your toon reached the ground, the plugin would disconnect it.
Thanks for your messages.
Zen
Seems the community is faster than me ! The changes recommended by Madman were correct (thanks to him). Bossland removed a function I used to perform the log out, so the LUA action must be manually sent. The new version of LogMeOut! was uploaded in the first post/on svn.
There is a lot of message since my last activity, so I'm trying to answer to all of you.
@stulee: No, it won't log out in the instance if you are stuck and if you checked the exception.
@risbonden: During the next launch on the bot, you can read a message explaining why you get disconnected the last time.
@RawrBlargh: Yeah sounds great. I add that in the idea of upcoming features.
@iPwnedUDude: There is a check to prevent that but it seems that HonorBuddy released your corpse to quickly. Let me know if you are still encountering the issue. That should be a rare case.
@HBL0V3: Please, provide a full log the next time. Your character was probably dead and HonorBuddy waited the respawn. To avoid this issue, you can check the exception Don't run to corpse.
@meoww: Sorry, I'm not sure to see the relation with your issue and the plugin.
@Kaelhoel: Could be nice. I add that in the list of ideas of upcoming features.
@kpow: There is an option in the tab Action After.
@magesticschu: I also really like this idea. Added in the upcoming features list !
@rawrasaurus: LogMeOut! was waiting that your character respawns. To avoid this issue, you can check the exception Don't run to corpse.
@BotOperator: Good idea, also added in the list.
@yanshu: Please post a full log of your issue.
@tumbum: Same, a full log please !
@User0828: LogMeOut! didn't have the time to log out your character after that the hearthstone was casted, but the next time your toon reached the ground, the plugin would disconnect it.
Thanks for your messages.
Zen
wanted a official fix. 
ZHEROMER
Member
- Joined
- Dec 29, 2012
- Messages
- 54
- Reaction score
- 0
That didnt work, but I read the quick fix and feel real proud of my self now that it works.
Sorry for not noticing that before now
I tried to this. It looks like the plug-in works. However, it doesn't "Force log out". Can you possible test it and see if everything is good? Even after a fresh install I don't get force log outs. No error or any thing significant but just the force log out feature doesn't work
Mr_Pibb
New Member
- Joined
- Oct 12, 2012
- Messages
- 398
- Reaction score
- 4
Hi, I have a strange issue I naver had before.
Everytime my toon dies (just tried it in questing mode) LMO will logg me out, because player was moved for more than 100 yards. I guess thats because the ghost is at the spirit healer which is more than 100 yards away from my last position. (I do not rezz at the spirit healer, my toon walks back to the corpse if LMO wouldn`t log me out)
Everytime my toon dies (just tried it in questing mode) LMO will logg me out, because player was moved for more than 100 yards. I guess thats because the ghost is at the spirit healer which is more than 100 yards away from my last position. (I do not rezz at the spirit healer, my toon walks back to the corpse if LMO wouldn`t log me out)