Normally I wouldn't say anything, but this problem has run its course. Please, before you do ANYTHING else, fix this bug! I beg of you. Was working yesterday, updated, and now its all back in the pooper. Just when I got my DK to 90 too, so please fix this asap! --Debeisus
There is a tendency to go 2 steps forward, 1 step back with updates and DB. I'm sure there is a lot of functionality to consider when they push a new release...but DB does seem to get the "backhand redheaded stepchild" treatment. There were initial problems in the last release too regarding the scripts. They were fixed after a few weeks of release. Users posted work arounds prior to official updates last time and this time (such as delete offending files holding up the compile). I'll bet this gets ironed out in another week.
Deleting these three was the only work-around I was able to find that actually allowed it to continue to work. Hopefully they can figure it out soon
Delete them from the Dungeon Scripts folder in the main HB folder AND the Dungeon Scripts folder within the Dungeonbuddy folder inside "Default Profiles"? I only did the latter at first and it still didn't work and then I deleted them from both and un-cheched "auto-update scripts" and then it worked.
I would imagine as long as you weren't planning on running "Dungeon Scripts\Mists of Pandaria\Raids\The Vault of Mysteries.cs" you should be fine. Just deleted these files Dungeon Scripts\Burning Crusade\Dungeons\Slave Pens Heroic.cs Dungeon Scripts\Cataclysm\Dungeons\Deadmines Heroic.cs Dungeon Scripts\Mists of Pandaria\Raids\The Vault of Mysteries.cs with a fresh HB installed seemed to fix this. On a side note I would like to thank highvoltz for this awesome bot, yes as we all know it does have some setbacks from time to time but I find it incredibly useful and am glad for its creation. Thank you again highvoltz <3
Dungeonbuddy Queueing me in wrong role Hi. I have never seen this issue before. My active spec is shadow, I've selected DPS in the dungeon finder window, but DG keeps overriding it and queuing me as a healer. Here's the log: View attachment 6736 2013-02-11 00.10.txt . Thanks!
Hey since the new update, I've selected Healer on my priest (I'm Disc) and for some reason the bot forces me as Ranged DPS.
priest specs are definitely fubar. When you are disc it queues as dps. when you are shadow it queues as healer.
Hi Highvolts, I hope you are reading the things the normal users are posting here to help you. Your last post was on 02.02 and I wish you would have a better connection to the community as a developer. Maybe you have a twitter account ... I would like to see your advancing DB ... some posts on what you work would be incredeble appreaciated. I have some issues for you: 1. I bot with 5 toons db. Everytime one dungeon is absolved, the healer (restro shaman) is not working in the next dungeon. logs are added. The big one is the log from the restro. The log is blewing up till the healer joins the secound dungeon. I guess this has something to do with the problem. I had to cut the log from the healer because it was to big. I commented the cut in the log View attachment -- README --.txt View attachment 776 2013-01-31 22.33.txt View attachment 1620 2013-01-31 22.28.txt View attachment 2840 2013-01-31 22.29.txt View attachment 4900 2013-01-31 22.31.txt View attachment 3728 2013-01-31 22.32.txt 2. Please improve the scripts from mop dungeons. They need love. Lower dungeons are not interessting until mop dungeons are not working, because we can lvl with kicks profils. Jadetemple have meshproblems.
I had to cut the log from the healer, because it was to big to upload. - - - Updated - - - I had to cut the log from the healer, because it was to big to upload.
if you dont mind me asking, how do i fix it locally myself so that I don't have to wait for the next update?
Is there a script and profile for Lion's Landing scenario? This makes the random scenario queue kind of pointless.
Styx.InvalidObjectPointerException: Cannot read a descriptor on an invalid object. 1) This is caused from a bug with older version of singular. I recommend trying singular from the v3 branch. https://subversion.assembla.com/svn/singular_v3/ (Free signup) because singular that is shipped with current hb release has a bug in in that causes resto shaman to infinitely spam shields while in an instance. 2) My 2nd team is almost ready to start the lower level MOP dungeons so I will be reviewing them again soonish. I was told Jade temple mesh issues were resolved but apparently not.. Jadetemple mesh issues I can't fix but I'll forward them to someone that can once I get the details. - - - Updated - - - There was no mesh available for that scenario at the time I was scripting scenarios. I will be looking at scenarios again after I get my horde to level 90 so I can do the faction specific ones as well. They're at 84-85 atm. - - - Updated - - - This is a bug in core so only thing you can do is queue manually atm. I trying to get a new HB bug fix release.
