Crashed 8 times so far.. Really really horrible.. What is going on with Honorbuddy lately? How come the last 4 releases crash, freeze or just plain wont work?
Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. Authenticating.. Authentication failed. this is getting old
i think it had to do with the ddos and w/e was done to get to better or different servers but thats just from what ive speculated.
Thx for mentioning me Apoc. that atleast shows you guys are reading I don't know why we should sit and post log after log when things that was working clearly was ruined in later releases. Form up a testing crew of lets say 10 ppl that can test the releases for 24hrs be4 throwing them out. dif. rig setups can generate dif. crashes errors etc etc. I agree that i might have been bitching too much but what the hell. You can't even leave the bot for a visit to the toilet or going for a soda w/o it 3 times out of 10 getting stuck in an infinite loop running back and forth between 2 hotspots , getting stuck in water , standing still on a mount getting killed. etc etc. I also understand that you guys might not be the blame for everything , that some thing are to blame on the CC's. Also English is not my main language so that barrier might make me even more of a bitch and that's sad because i'm really a nice guy. Will pull my act together and provide accurate bug reports w. logs etc etc.(even tho if the function was 100% working in a prior release) This also goes towards the CC-developers regarding bugreports. thank you for listening.
Possible to pass the word to whoever mesh, to remake the mesh of valiance keep inn, as its so ugly made that the bot cannot go up the stair and jump off the window when you manualy go up insteand of using stair and such......it is really ugly messhed and cause the bot to jump on the first floor....not really bot friendly. Zuruss
ok, i posted my log when my bot crashed on the last page. i had the game and bot crash again. this time i got the WoW crash log. here it is. i hope it helps. edit: as you can see in the log, the memory error that lead to the crash was The instruction at "0x0085CAEC" which is not the memory error you said was hopefully fixed. again, i hope this helps it happens almost like clockwork after the bot runs for about an hour and the memory spam in the bot starts Same memory error as Mezz0 is having according to his log he posted on the previous page.
Valiance keep dock mesh is bad too....the bot keep trying to rech the dock by the water ( which even if jumping cannot be reach ) , when it should use the rock a little to the right, there is quest and such that we need the dock mesh properly, the dock and the inn are totaly ugly and add a babysitting at each quest they are needed so around 11 ......think about it 11 darn quest where the toon jump in place being stupid......plz fix mesh. Also pershap a little anti stuck wouldnt hurt, i been asking for it, more ask for it, everyone that eventualy use questing mode will ask for it, the bot can stuck forever in a edge of a building stair without being able to unstuck via your current click to move unstuck feature which seem bad at first in lots of case.... One recent case of the need of a better unstuck is when my bot when into water, going toward havest a chest for objectif, the chest is into a ship wreck, the bot had some fun stucking on something and all it was doing is overclick the chest , pershap he tough he would magicaly go through the obstacle? it somehow worked, he drowned. Zuruss
problems with authenticating i bought today the account, hb 1 year... and i recieved the email from honorbuddy saying that the payment was done.but i cant login with my account in hb prog
You simply need to use your shopping information to log in, not the forum info, the info you used to log in the shopping account. One more mesh problem found, when doing the trident quest in borean the bot stuck while going turn in to the snake npc, it cant get out of the water ( the mesh should make it go out 2-3 inch by the left.....) The mesh maker REALLY should use a quest profile alliance to know the problem with mesh coz there is a shit loads so far, it getting ridiculous, if you want us to make good profile so poeple switch from aion quest bot to hb quest side......you really need to mesh better borean tundra, i will keep posted the spot where the bot bug, but seem to be going to be tons of them so far, valiance keep inn being VERY urgent. -Bug found, when a mob is engaged by another mob, the bot get in aggro mode but stand there til the target is dead or come to him, making it so on the beach the snake mob being engaged ( they take about 20 min to die ) cause a massive slow down on the bot. Zuruss
problems with authenticating i did that though it isnt working it says something like response from hb servers: N/D
Becuase waiting a few sec's longer is SO hard. Atleast they did something bout the DDoS, ive seen many a bot be fucked over by mimic and not do anything. And FYI, i have the same problm as you, but i just sit and wait, but your time must me worth alot more then mine, if you cant sit infront of a computer for a few more sec's.
any idea what this means just crashes wow saying honorbuddy has encountered a problem in the box it says "an item with the same key has already been added". Using instancebuddy latest and latest version of hb also using convalesence beta 5 let me no if you need any more info
Mesh problem updated. Borean zone -inn not meshed properly not able to do the 12 quest in it without the char being stuck on first floor jumping, cannot find way to second floor ( urgent ) -Dock, mesh giving access from water to the dock, not able to complete 2 quest from it, he should mesh from water, to the rock and then to the dock. -trident quest turn in, cannot access to the snake npc from the water....bot stuck, mesh 3-4 feet to the left would solve this. -amber ledge area, the mage tower the floor arent meshed properly or at all, causing the bot to not being able to go up on the second and third floor ( 2 quest failing) -About any quest that go in water, the bot stuck to go back on the land ( most of the quest...) Zuruss
There are numerous Behaviour Tree errors occuring where there should not be, these errors were not occuring on the last build. I'm doing all I can to resolve these issues on my side (CC) but when these kind of errors occur for no apparent reason it gets rather frustrating.
does the corpse retrieval use the mesh when it walks around looking for a safe spot to rez? cause it just walked off of hellfire like 3 times in a row
@Dev's: Im having an issue with the bot looting quest items, as in, im doin the zep quest where i have to pick up parts in hellfire, what information would you like, to help with this? Its fairly hit and miss, sometimes i see him standing there, so i loot it for him, but he just ran up to two and looted them himself (These two were directly infront of him) Is there a log i can post that will help you guys fix this?
As I said; It's a pain to have to read everything and pick out the useful information when 80% of it is pointless, or completely off-topic. (Yes, I read nearly everything.) The reason we ask you to posts logs is mainly due to the fact that we're not aware of it being broken again. I've been running the current release for 14hrs straight now, and I've only ran into 1 issue having to do with chain-dying. Please do me a favor and disable all your addons. When it crashes again, either post the crash log, or PM it to me. The crash your having is odd, as HB doesn't touch anything in that area of memory. (I only took a quick look, so take that statement with a grain of salt) I'll look more into this one in the morning. [Hopefully for EU users at least] The errors aren't coming from the BT. It's coming from a very strange issue that honestly, makes no sense. I know what the issue is, and most of them are CC issues. (You guys really need to check if things exist in dictionaries, before accessing them) From what I've seen; it's not really a 'bug', but more of an 'undefined behavior' on MS's part.
