Yes, thats the reason. Simply enter it even if you dont use it. Does Honorbuddy still say Warden Check in Progress? Yeah, I can and I will. But I dont have time to make bigger changes atm.
I had this problem when I used it for the first time yesterday where if it was running and I pressed "Stop", the relogger would stop responding and I would have to shut it down with task manager. In the middle of the night, I must've gotten disconnected, or it just stopped working, but when I came back throughout multiple times of the night, I would once again have to shut it down with task manager, and neither my WoW, nor honorbuddy were still open. It worked fine though when I first started it up. One suggestion, when I hit stop, can you change it so that it doesn't force close everything. Like if I hit stop when someone is near me watching everything I do and spamming botter, I'm going to want to stop it and say something back to him, but it looks very suspicious when I suddenly go offline because my WoW got force closed. Thank you and I appreciate all of the hard work you've put into this.
I made a new Version and uploaded it. Just to make clear how it works now: The Relogger does the same you would do to stop the Warden check (clear registry) because it checks the Tripwire page itself every second and shuts down properly if HB is detected. Going to throw in an Interrupt button or something like that. But you'll have to be patient as this isn't a 5min change. Ah and the fact that the relogger stopped working might be caused by a Warden check at night. I have never seen the Relogger simply stop working but ekimbo reported the same behaviour when a Warden check occured. The Warden check issue should be fine now. I hope
Okay, thanks for the quick response. I will try it again tomorrow night and update if it still does the same thing or if it's fixed for me.
Every time it joins a BG or leaves a BG it shuts down HB. Which over time causes a max sessions reached issue or HB sits there grayed out. It happens every time there is a loading screen.
That may be a BG thing? I was having the exact problem earlier but it was when I didnt even have the relogger loaded. I was just playing about to start HB up and running, and I clicked the BG info to select which BG to pick and HB crashed. Did this several times until I just hit start and selected the bg I wanted in game.
What? How is it possible that the Warden check occurs when the Registry entry is removed? Going to think about that again?
IDK. Wow gets error 132. Relogger crashes. I relog wow manually. I wanna restart HB manually, but it kicks me to website to wait 15 min---> warden check. So at WC it crashes.
Wrong. Warden Check occurs when Honorbuddy shuts down unexpectedly. So if YOU start Honorbuddy without clearing the Registry first your Honorbuddy will do a Warden check. What exactly happens in the situation you describe? I expect WoW to shutdown with an error and because of that Honorbuddy follows WoW to death with a Readxxx failed error. Is that right? If not, describe the situation yourself. If yes, what was happening when wow crashed?
How come people don't include the source code with stuff like this? I mean seriously, these problems could have been fixed by now if more than one person were working on it. I can't see how posting the code could hurt considering Blizzard's EULA does not prohibit and application such as this. Technically, a bot relogger has nothing to do with World of Warcraft and doesn't touch its memory space. All it does is start a program if it crashes for some reason. If Blizzard's EULA somehow encompasses this, then the Windows Operating System violates it. In fact the only people that could have a legitimate complaint is the developers of honorbuddy. Which reminds me, why isn't there an initial EULA that runs the first time your run honorbuddy and prohibits Blizzard employees and anyone working on behalf of Blizzard from running or even downloading the application. I know glider never had one of those either. I'm sure blizzards employees have purchased copies of honorbuddy (as they did glider) and reverse engineered it in some way to bolster warden's detection mechanisms. Plus, I would think it would be difficult for Blizzard to sue someone for violating their TOS/EULA if they violated someone else’s in order to gather information on how it worked. Listen to the Blizzard lawyer (in the MDY case) try to explain how warden works... he doesn't know what he's talking about. But from what I've read Blizzard developers know just about everything there is to know about glider? I would think a simple EULA would have prevented that.
Good points, first off: it actually does have something to do with wow since it reads its memory. Second: If someone likes to take a look into the code and has a good reason for that like "Hey, I'm a programmer and have a bug and want to help fix it." this person can write me a PM. But I wont release a highly unoptimized and "dirty" code for the public, because that sucks.
