Honorbuddy for MoP 5.0.5.16057

Since a week or longer i have one problem which i reported like 5 times already:

PHP:

System.AccessViolationException: Could not read bytes from 1CE7DFF0 [299]!
   bei Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
   bei Styx.MemoryManagement.MemoryBase.ReadString(IntPtr address, Encoding encoding, Int32 maxLength, Boolean relative)
   bei Styx.WoWInternals.WoWObjects.LocalPlayer.get_RealZoneText()
   bei Honorbuddy.MainWindow.HandleSuccess()
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   bei MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

I've read a lot of other people having the exact same issues - this happens at startup, nothing has been chosen by that time, it just plain crashes. SINCE WEEKS already.
Sorry if i sound harsh..but, really guys, same error over and over and over and over again after every update. I just would like to know if this is gonna be fixed anytime soon or if i still have to wait for another 2 weeks or maybe longer... at least i wouldnt try until then.

 

Druid combat works better in last version, but he just heals outside of combat, can set whatever i want in Singular, he dosnt does as set.

 

Im getting this when Im trying to start quest bot. "Could not create 'CurrentBehavior' in quest bot; an exception was thrown: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index" and yes.. I have don some questing on the beta before. So its a up coming problem for me.

 

Last update just broke everything. Did you even test it before pushing it?

 

Did you even supply a log?

 

It's been reported already. And that was not the point of my post, so move along.

 

Got the error on two lvl 15's that I started yesterday. Posting here as from what I can tell the problem is coming from the behaviors instead of the questing profile itself. However I could be wrong

Error message:

Code:

[16:34:45.236 N] Could not create 'CurrentBehavior' in quest bot; an exception was thrown: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
[16:34:45.237 D] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at Bots.Quest.Actions.ForcedBehaviorExecutor.
(ObjectiveNode )
   at Bots.Quest.Actions.ForcedBehaviorExecutor.
(OrderNode )
   at Bots.Quest.Actions.ForcedBehaviorExecutor.
.
()
[16:34:45.237 D] Stop called!

Profile: Kick's 12-58 Horde
QuestID: 14038 QuestName: Love it or Limpet

Here is the log. View attachment 5520 2012-09-20 11.34.txt

There were only some minor bugs with the profile but I have compiled those to send to kick when he gets back. This is the only behavior related one I've come across that kills HB. If the dev's can't/wont fix this and will wait for kick, is there any way I can override this quest for the time being? Thanks.

 

Questing is still broken, per the official Quest Developer "Kickazz006". Not only is it broken, but he entirely close his support thread because of it.

http://www.thebuddyforum.com/honorb.../50549-kicks-mega-profile-packs-1-85-a-2.html

 

I cant wait for BGBuddy and druids to be working!

 

The update that was applied yesterday was a big fix for quest bot. It runs about 90% atm from what I can tell. He closed his thread for his profile before that fix went live.

 

I started having this problem after this morning's autoupdate. Here's what I did to solve it, YMMV.

1. I rebooted my computer. No idea if that really was part of the fix but I don't do it very often and System Access Violations have to do with RAM so it can't hurt to clean things up.
2. I checked my shortcut on my desktop and found out that somewhere in one of the Blizz updates it changed my shortcut from wow.exe to the World of Warcraft Launcher.exe again. (It did this on 5.0.4 patch day too.) I changed it back to wow.exe and restarted WoW.
HB .458 loaded just fine.

So imo a reboot can't ever hurt and make sure you're using wow.exe. Don't assume its like it was yesterday just because you're doing the same things you were doing yesterday.

FYI, this particular box is still on XP so certain steps don't apply to me but also make sure you're running both WoW and HB as an administrator if you're using a Windows flavor beyond XP. When troubleshooting a problem always go back to basics first.

 

post the rest of what he said...there was a reason he closed the thread.

 

And he only temporarily closed the thread until the questbot was functional as liege also pointed out. Plus he's also in the middle of moving iirc, so give him a chance. He probably can't find which box his Magic Fixit Wand of AwesomeSauce was put in.

 

tooooooo long

 

His Magic Fixit Wand of AwesomeSauce is what gets the ladies.

Just sayin

 

Tested any Dailies yet?!

 

Nope. I was trying to test out the first 30 or so levels with MoP being released this coming week. Was also testing out the 50 to 58 range.

 

Can Any of the developer crew give some realistic timescale as to when this bot will be functional again its 3 weeks into expansion now and its still running like a 3 legged pregnant cow, surely there must be some light on the horizon by now or are we going to be continually told to be patient? At least release the updates once a week to give us a chance to use the bloody thing without having to trawl through hundreds of pages of posts in the hope of finding a profile or bot update to get the bloody thing working again.

 

Get some fatal error when i open HB with WoW

View attachment log.txt

 

I think its fair, to ask for some communication from the Buddy Team. People hung in with you during the Diablo3 suit, but just communicate with your customers and give us some realistic time frames.