Its been over a week with a list of complaints and bugs listed. It crashes every 2 hours. Can we get a fix sometime soon?
Well I posted this on the wrong thread. Anywho.. People who are complaining about the 2-3 hour crash please read this. 1. I ran it all night somehow but yes I have experienced the crashes, live with them. 2. They have more important matters like the new patch and Cataclysm to worry about. 3. Try a relogger.
Same here, crash every 2 hours. Last version of HB, no plugin, no cc, juste pvp call to arms. Windows 7 x64 bits
My 2 cents is that the Devs arent concerned with upgrading this for 2 days. They prob have a ton more on their plate with 4.0 coming next week.
Well, something has happened since I posted up the previous info, because before I was able to login and then I wasn't... now it's saying my e-mail doesn't exists, so I created a new account and can now log in. That being said, I would very much appreciate some assistance on gathering WoW related crashes. Meaning, when WoW crashes, where am I looking for a crash log, file names, etc. Also, do I also submit an HB log at the same time? I just want to be sure that instead of me doing it and getting something wrong, that I submit a bug in the correct way, so that information is valuable. I want to do everything I can to improve the functionality of the bot, and that starts with me submitting perfect bug reports. Thank you very much. PS I'm also seeing "Sync failed!" messages in the log. What are these related to? Is it a profile issue, or an HB core problem?
We will do a new release shortly. Hopefully in the next few days that resolves the issues with the crashing and the LUA problem.
When WoW itself crashes, you can find the logs (and dump files) that we need in C:\Path\To\WoW\Errors\. They're named by the crash date + time. A .txt and a .dmp. Just zip them up and send them to us. (The .dmp is important! It shows us some required memory addresses that the .txt file does not) Feel free to edit out your character name, etc from the .txt version. (The .dmp version doesn't show that info) For any, and all 'reports', we need your full log file. (Again; they're created by date + time, but for when you started HB. We need the one where the issue was showing itself.) Preferably, we'd like a 'time' when it happened, since some log files can easily be a few MB in size, and reading through all of it is quite a pain. So anything you can do to help narrow down where it is, would be helpful. Lastly; if you're still having issues with the bugtracker, hop in IRC and talk to me personally. I'll try and help you. (Sorry, but I rarely read my PMs on here anymore, as most of them are just people complaining about things that have nothing to do with HB, or anything I can look into!) As for the "Sync failed!" message, it can effectively be ignored. It's just a debugging message left in. The next release will have more concise error messages when things fail related to auth, so people should realize that it's not a bug, but an issue with contacting the server itself.
isnt that abit rude we try to give him details with logs to fix the errors i bet u have the crashing to do we need to call you an idiot to?
Loading Honorbuddy 1.9.6.2827 settings. Log file: E:\Honorbuddy\HB1.9.6.2827\Logs\11-10-2010_10_08 AM Log.txt Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Max sessions reached! Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. i hope this wall of text annoys you as much as it does me trying to log in to this fucking program that i PAID FOR!!!!!
o ok but stil it isnt nice to call people idiots who try to help the devs with the error problems to get it fixed
The people that posts logs.. and give their error are helping yes. People who give their error are not helping. People who just give a log.. are not helping. People who give a log, and error, but its the exact same thing as the person above you.. are not helping Stating known issues or partial information isnt helping much.
If you're unhappy, then stop using the program and go elsewhere. Nobody needs to deal with your bad attitude. As it's been stated many times in this thread; it's not a 'bug'. No matter how bad you want it to be.
just another(of many) paying customer that is sick of getting messed around, if you don't like the feedback don't do the program!!!
We love the feedback. But only if it's not the 5 millionth time it's been posted. We're aware of the 'issue'. All we ask is that you not waste our time when we're trying to find the bugs that actually matter. And ones we haven't already seen.
