I have noticed repeated issues with the bot not being able to repair as it believes it can't find the vendor, this happens even if it's standing right on top of the vendor, and in that case opening the window manually seems to fix it as it then repairs and requeues.
It doesn't seem to happen every time but when it does it stops the whole group, trying to narrow the issue down and hopefully have more info for you.
Edit: added extract from log when this happens. I clicked the vendor to open the window and it repaired when it found him, otherwise it would have just continued looping (there should probably be some throttling so it doesn't loop so aggressively).
Its pretty odd this is happening considering your bot is right at a vendor and bot location is also on the mesh. Vendors are ignored if they can't be navigated to or are blacklisted. If they are blacklisted then it would be in the log. Have you tried restarting hb to see if it was just some navigation quirk? Maybe a full log (zipped if needed) would be more helpful.
wow wtf man? seriously wtf. we need the option to keep that disabled, has nothing to do with edited scripts. It's because updates break the bot. The last 3-4 updates broke compiling of some dungeons. Shit RIGHT NOW the dungeonbot is down due to last night's update causing "Compiler Error: error CS0182: An attribute argument must be a constant expression, type of expression or array creation expression of an attribute parameter type".
Please dont let this go live. There is NO REASON ON EARTH why an honorbuddy customer using dungeonbuddy would need a sudden FORCED update to the scripts that are working perfectly well. we'll update for any improvements when we know there are no errors. Do you seriously want all users to constantly manually move the scripts into some backup folder just in case the next time they log in there's a sudden update?
The only reason an option to opt out of script updates was added was to allow for people to make changes to the default scripts without fear of them getting over written. This wasn't really efficient and is no longer needed since I added an option to use scripts and profiles from another folder. Dungeonbuddy will use scripts found in the 'Custom Scripts Path' over any default ones.
The issue most people are having is they have stale unused scripts in the default scripts folder. Since these old scripts are no longer being updated they might contain removed api calls which leads to compiler errors and cause everything else to fail.
In order to fix the above problem Dungeonbuddy needs to delete any files in the default scripts and profile folders that are not on the update server.
No script issues have been found in Dungeonbuddy that comes with current stable HB release after any stale scripts have been removed. I tested it myself and I've also been allot more careful with script updates the past few weeks. If you're having script compiler errors chances are you are using an old version of HB or you have stale scripts and need to delete them.
not sure what this is for. was there some issue you are trying to fix? isn't the general idea here to prevent people from noticing they are running with a bot dps. There are numerous dungeons where EVERYONE by now follows the same strat, to run past certain skippable mobs or to hide behind a pillar and wait for them. You don't want the bot attacking anything the tank is not already tanking. That's how you get the whole group to freak out and start calling out in chat, quickly followed by them realizing they are looking at a bot.
Dps will not attack NPCs that are not already in combat with group. What this change means is they will not strictly switch targets whenever tank switches (for example to pick up a stray NPC) because doing so would be a dps lost. DPS will instead prioritize NPCs based on number of group members that are attacking npc (this does included tank) and health percent.
MORE SUGGESTIONS:
Please let us decide the pull range. Pulling every living thing is getting old. You dont need to clear half the packs it does. There are also area's that should be skipped and it just pulls on through.
.
A 'PullBlackspot' tag in profile should be used to blacklist groups of NPCs that should be skipped. It's exactly like a Blackspot tag except different name. Someday I'll write a profile specifications .
example.. This just goes inside the <DungeonBuddyProfile> tag.
<PullBlackspots>
<PullBlackspot X="3717.217" Y="2583.737" Z="769.5298" Radius="9.433087" />
</PullBlackspots>
