Short answer is yes, it is easier.
Technical answer is, if you have a compiler issue with Quest Behaviors, save time and just delete/move the .cs file in question. Then restart the quest bot, until there's no compiler errors.
If it still comes up, HB won't load that particular file until there is no compiler errors.
Usually, questing will try a recompile before it starts with a profile, and we're using that as a test and way to find old or damaged files that don't work anymore.
If it's a file inside plugins or routines, move or delete the folder, and reinstall HB as a precaution.
If there's a whole screen of compiler errors in the log, find, delete the listed files one by one, or, move them to a new folder outside of the game folders, eg Honorbuddy/Backups/
You should restart honorbuddy after deleting those files anyway, it's just an initial debug, that you want to start HB to find out what it needs to do, initially see if it loads properly once that one .cs file has been deleted.
When it starts moving the player, questing is working. So, to be safe, stop HB and close it, then reopen HB and start the profile again.
The deprecated folder in this case, means that it was on the way out for a while, and now isn't supported.
Installing over the top of the old version creates problems like this, using the updater usually (?) prevents it.
Shouldn't be coding so early into the morning![]()
Added, will be in 3.4New Neighbors Quest also needs a blackspot at <Blackspot X="193.4517" Y="1862.687" Z="23.10341" Radius="8.545116" />
There's a pillar in the middle of the hunting ground spot that my druid keeps getting stuck on.
Could not create current behavior in quest bot; exception was thrown. Bot stopping! Reason: Could not create current in quest bot!
Got this message
I can't figure out what it is referring to.
It worked really well up to this point.
Thanks. I'll do that.Doing Quest (35261): Shot-Caller
Do that one by hand and see if it picks up, I wasn't able to finish testing this last night.
That was a mis-read on my part, you had already done that but:Thanks. I'll do that.
Just so you know - I don't currently have that quest.
Thanks. That fixed it.That was a mis-read on my part, you had already done that but:
<TurnIn QuestName="Hardly Working" QuestId="35260" TurnInName="Darkscryer Raastok" TurnInId="80157" X="390.1614" Y="2444.607" Z="19.77696" />
Was previously missing the XYZ, fixed below in a couple spots:
View attachment 157758
Thanks. That fixed it.
I'm wondering if I should move on to Nagrand. Do you happen to know if I would miss out on any significant quest rewards if I did that?
Sounds like a PEBKAC issue, post logsbot not only runs through a huge amount of mobs until it dies..but when it finally does pull it tries to pull an entire area regardless of me changing it in the script...appreciate the effort though.
This should be understood by now, and should be understood with all Quest profiles.Do not attempt to run this profile AFK.
Rather than detail the millions of mesh issues irrelevant to the profile, how about post the quests that are the problem so I can look at them:?It gets stuck inside the Inn in Spires of Arak, it runs into walls, it gets stuck at various quest givers, and it has some other pathing issues. It is a good and worthwhile profile because there is basically nothing else right now (12/15/2014) that will even travel through the zone doing the quests for Horde. Just be sure to watch what it is doing!
So far ive ran into nothing but problems on a clean install of honorbuddy and a clean cache...bot not only runs through a huge amount of mobs until it dies..but when it finally does pull it tries to pull an entire area regardless of me changing it in the script...appreciate the effort though.
will post logs tonight when I get home.