What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Problem turning in quest

K

Kelcer

New Member
Joined
Dec 21, 2012
Messages
37
Reaction score
0
I have problems turning in some quests. Somehow it can't choose the desired reward. It's the 2nd quest where it doesn't work already. I get access violation exceptions in the log.

I attached the full unedited logs. I cleared the log folder before reproducing the issue.
 

Attachments

Last edited:
do a fresh install of honorbuddy into a new folder, and completely restart your machine.
 
I did reinstall HB and restarted the machine as well. It worked for a while. But now I got the exactly same access violation exceptions again. It looks like the offsets sometimes are different? Beside this, I have absolutely no problems with HB.
 

Attachments

Last edited:
follow our instructions plz and let me know
 
I will, but I still think it's non sense.

It's the "CacheDB" for items which has to be messed up. I guess normally the name of an item is read on it's 1st encounter. But in this case the cache is populated, when you pick up the quest. Now, when the Wow process decides to relocate the cached item, it bombs when you try to read the name, while turning in the quest.
 
Kelcer said:
I will, but I still think it's non sense.

It's the "CacheDB" for items which has to be messed up. I guess normally the name of an item is read on it's 1st encounter. But in this case the cache is populated, when you pick up the quest. Now, when the Wow process decides to relocate the cached item, it bombs when you try to read the name, while turning in the quest.
Click to expand...

Hi, Kelcer,

Honorbuddy got updated to .523 since you last stopped by this thread. Please upgrade to the latest version first.

And indeed, Combat Routines can cause sync errors.


No joy?
Try what they suggested.

Still no joy?
Post a fresh log, please.

cheers,
chinajade
 
Quest rewards are usually handled by AE2.
Like china says, please update a provide a new log.
 
Well the problem is, it can't read the names of the quest rewards. It has nothing to do with the weight code! Also this problem seems to exist for quite some time. Found at least one other thread from November where the same offset resulted in an access violation (299), when selecting quest rewards. However there was no resolution.

Since I didn't want to change two things at once I updated to 523 (clean installation) only. The problem is still there!

I will now test with 523 and CLU.
 

Attachments

Last edited:
Mario27 said:
i have a solution for u in data folder u have weight sets delete all weight sets except the one u lvling lets say im lvling a retribution paladin keep that weight set in it and delete all others and restart honorbuddy if u dont know how to do that i can help u with teamviewer

make it how it in the picture is if you lvling a warlock destro or demo only put the warlock weight set in it
Click to expand...

Thank you Mario27. But I tried this and it didn't help. I think it crashes before deciding what item to pick anyway. A quick and dirty fix would be to catch the exception and select the 1st item.
 
wel that works for me it choose all the right items some times it wil take a dodge ring or something but thats because it does it sometimes did u turned on autoequip in plugins? and configed the weapon style etc
 
Well it seems to be better with 523. My test char went from 1 to 15 without getting stuck. But then I didn't watch it for 2h and it had been stuck again for almost the entire time :( Restarting Wow fixes it. It isn't always at the same spot. What Combat Routine do you use? AE2 is configured and works just fine.
 
turn wow on dx11 and give it a try plz
 
hmm,try a new Hb installation from scratch plz
 
I did that multiple times already. The last time I installed from scratch when updating to 523. As additional note, I use VMWare. But still, memory read errors shouldn't happen. Should they?
 
idk if its vmware related since we are not experienced on that :(
 
You must log in or register to reply here.
Back
Top