We haven't changed questing in ? very long time ALL the bots uses the behaviors in the grindbot. There's maybe 4-5 issues atm. causing all theese weird behaviors with the bot plus they are pushing 4.0.1 this and/or next week and we got a metric shit ton of stuff to update
STILL, i'm unable to use HB. Past weeks it loads up, and loads CC settings, says Activity: Downloading Mesh. Then doesn't download anything and i just end up standing around. Here's a log from what shows when i Start/Stop the bot.
We know your working hard (and appreciate it), I just question on the right things sometimes? If you haven't changed questing in so long why is it I still cant use HB2 for weeks now over night for a simple grind bot or for RAF? There is no stability for so long now I don't recall the last time I left the bot over night and came back to even a level or two, Coders and customers have such frustrations atm for very different reasons yet only the coders have the power to fix the situation. Dont you guys think this has gone on long enough? Profile creation is laborious, I cant click go and know it will still be working fine in 2 hours am I asking to much? Get the simple stuff working again please, make the bot easy to use (profile creation) then add petrol to the fire. You guys have the skill but I feel not the direction. (Posting in vain again I feel) Peace.
Did 1.9.5.5 ever get it's Auth servers updated? I'm trying to go back and use that build because it was the last build I've been able to use at all.
How do you know what they're working on? I haven't seen any updates to questing in a long time. Just saying ... I don't think it's eating up as much of their time as you might think.
The workplan should look like this imho: #1 Make the grindbot stable #2 Add stuff like PvP and Instances #3 Slowly add a advanced navigation system as long as it doenst interfere with 1-2 #4 Slowly add questing as long as long it doesnt interfere with # 1,2 & 3 #5 Profit Now its more like 1* Profit 2* Add a TON of stuff that makes the bot so unstable that nothing works for more then 2-4 hours top. And thats kinda sad, even with the simplest grinding profile I can never get it to run over nites etc any longer. HB used to be good.
Wow, Just went threw the past few pages and LOL! Questing is GREAT! and 1/2 of the reason I came back to HB. I know its still in beta and must be babysat and thats fine with me. I'm willing to bet that 95% of the problems people are crying about here are CC or Plugin related... That includes the default CC's (default pally CC makes my wow crash on loading screen). This is after all a hack program and it will never work 100%. Stick with HB1 if all you want is grind/pvp. Great work on this release. There are a few nav issues but nothing too major.
i know and the crashing isnt an isue really if bossland released his relogger then it just log back in
I have some problems also. When i start the grind bot the char just stands still. Its not moving at all. Ive tryed download HB again but it dosnt work. Ive tryed clearing the mesh folder but nothing happends. Anyone else got the same problem? Fixed the problem...
Sorry but I agree. I have changed all my leveling toons back to HB1, working well. HB2 is nice but too much freeze / errors... GB is working fine also.
if you can do it better and faster show us your way and your skills as a developer critisism is always welcome but next time do it without being rude
To all of you; we don't spend as much time on questing as you may think. At the current moment, we haven't really touched anything questing related in nearly 2 or 3 weeks. Any new features you may see, are 99% of the time added during our free time when we're bored and/or want to see something else. (Most of the time, it's a 5 minute job to add it [e.g. the CC selection window. It was bugging me not being able to have more than 1 CC of the same class in my folder]) The last few weeks have been nothing but searching down bugs, and attempting to fix them without breaking anything else. Unfortunately, with such a large codebase, and so much stuff going on, it's not exactly 'easy'. We're trying our best to make things stable (as seen in the latest release). Personally, I don't read anybody's issues with not being able to authenticate. I've already explained it quite a few times, and the issue isn't something on our end that we can handle any better than we already are. So please, if you can't login, wait 2 min and try again. You'll log in eventually. Trust me. As for stability issues with PVP, Nesox basically rewrote the entire SoTA handling to make it more stable (which it is). We've also been working hard on trying to get the 4.0.1 patch situation under control so we see as little downtime as possible. It's going to be a major release that breaks A LOT of stuff. Mainly due to game mechanic changes. (Even though I know we'll be to blame for CCs/Profiles/etc not working correctly. Because as you all know, if you don't understand the real issue, blame the people creating the product!) For those of you with the long lists of WoW crashes; I'm 99% sure I found the cause of the issue. It'll be fixed in the next release. [Note: this only addresses one of the types of crashes, as for the others, I haven't received enough information about them to really do much] You can tell if your bug is fixed by looking for "The instruction at "0x0071B7F0" referenced memory at" in the WoW crash log. (The part in bold is the important part, if it has another value, then send me the report.) Honestly, I'm tired of reading hi1674's replies. I've seen a proper bug report MAYBE 2 times, the rest are just constant bitching and hopping on the bandwagon. If you don't have anything meaningful to contribute, please, don't post. It makes it harder for us to get to the real issues when we have to filter through a bunch of pointless posts. For the rest of you, feel free to PM me with a DETAILED LIST of bugs so I can get through as many as possible tomorrow. P.S. this reply isn't meant to be a 'mean' reply. It's incredibly frustrating to try and provide support to people who refuse to accept it.
hi apoc here is a crash issue of mine many people have issue with it i think http://www.buddyforum.de/showthread...-is-the-logfile-i-gues-its-because-of-the-bot wel lets wait for the new release if its sure 99% i gues we wont have any issue anymore
Reuploaded the zip archieve Themyscira is the default warrior cc now, idk how TankWarrior ended up there
as off, it works as intended. no bugs, errors yet. Works perfectly fine with this setup. + Honorbuddy +Plugins: - QuickIrc - BuddyProwl 3.0 - AutoEquip +CC: - The One Suite (warrior) so far so good, tested on questing, grinding, pvp.
hope this helps apoc. the Memory moved for lua events (newEvents); skipped for now. seems to muck up things so slowly until it crashes. heres the log. says my crash log was last updated on 9/5 so i dont think its been saving right even though my bot crashes at least every hour and causes wow to crash as well. i included both logs though just to have them but not sure if the crash one is of recent crashes. edit: ya wrong crash log and dont see the one from the crashes before. the regular bot log though has all the memory errors im getting. hopefully that still helps.
Hmm, does anyone knows what this means? "An item with the same key has already been added"? That is my error and afterwards it shuts down.
