I've been trying out HB for the majority of today, and one problem I can't seem to fix is my character talking to the quest NPC then choosing an available quest but not accepting it and instead just repeating the process, over and over. I'm in Mulgore using the [H]1-39 All Races/Classes [Tubajediamr] profile and Fpsware Paladin CC, also the latest version of HB. I suspect this is the sauce of the problem? Code: [2:22:44 AM:718] Lua failed! Status: c [2:22:44 AM:734] System.NullReferenceException: Object reference not set to an instance of an object. at Styx.WoWInternals.Lua.GetReturnVal[T](String lua, UInt32 retVal) If so, how would one fix this?
Bug 552 – Repeatedly trying to accept quests unrelated but similar dosnt seem to have been picked up on
Tried with version 3804, with all plug-ins disabled. Still having the same problem. Log for this try attached, any other ideas?
I have this sometimes in 99% it workes if I close HB and open it new. But there are some Quests that are broken and you need to kick them out of the XML File, that I had once.
I have an idea but idk if it will fix your problem for sure. I tried to find the link within the Wiki pages but I couldn't - put this attachment in your "Quest Behaviours" folder It: "Allows you to do quests that requires you to talk to Npc's also allows you to choose a gossip option", and doesn't come standard with HB. /Credits to ChinaJade: http://www.thebuddyforum.com/mediawiki/index.php?title=Honorbuddy_Custom_Behavior:_Message
Bug 552 – Repeatedly trying to accept quests been on bug tracker for 3-4 releases now; can be solved by macros of the other cc you linked
Sorry bout the slow reply, haven't had a chance to test it with all these patches Blizzard is releasing... The CS file on the other page hasn't fixed it and the character still refuses to hand in a quest. I'm not sure what you mean by the macros. Attached a more recent log with the latest release.
KickAzz006 is correct, if you are going to give credit to someone please give credit where it is correctly due. This behavior was scripted by Nesox at the start of the Quest Behaviors system.