Nesox
Well-Known Member
- Joined
- Jan 15, 2010
- Messages
- 1,563
- Reaction score
- 48
Changelog 2.0.0.4555
Honorbuddy
Changes
- Enabled debug statements in Mount.ShouldDismount - this will provide extra information about dismount reasons.
- Should no longer allow re-checking if flight paths should be used, for 15 seconds. Up from 5 seconds.
- Honorbuddy now prints a reason when dismounting.
- Vendors.ForceTrainer works as it previously did.
- Targeting filters is properly getting set back when running PVP+Grind with MixedMode meaning it will not run around from hotspot to hotspot without killing units.
- FindVendorsAutomatically now stores the results from the 'CanNavigate' check ?nstead of checking it each time the function is called.
- QuestOrder "If" tag, conditions, should now properly support LINQ queries.
- ActionMoveToPoi now checks Mount.ShouldMount before actually mounting. This resolves mounting up to move 3yds to a quest NPC. (Usually happens after dismounting from a flying mount)
- EquipMe works for Paladins now.
- Mount.Dismount(string reason) added.
- New shortcuts usable with Conditions: Chance(), Random()
See the Wiki for details... Honorbuddy Profile Tag Attribute: Condition - Buddy Wiki - Most Behaviors that take QuestId, now take (optional) QuestInLogRequirement and (optional) QuestCompleteRequirement
See the Wiki for for an explanation... Honorbuddy Programming Cookbook: QuestId for Custom Behaviors - Buddy Wiki - For behaviors, QuestId="0" is no longer allowed (it was never a valid quest id)
If you want the behavior to run outside of the context of a Quest, omit the QuestId attribute
when calling the behavior. - A number of behavior attributes have been renamed in order to make attribute usage consistent across behaviors.
The old attribute names are always honored. However, you will receive a warning that requests the profile
be updated to use the preferred name.
Bugfixes
- Fragment database has been updated. This should fix most of the stuck issues.
- Blacklisted digsites should be properly saved now.
Bugfixes
- Shuttered movement while reaching nodes should be fixed now.
- Corpse runs in Vashj'ir should be properly working now.
- Rezzing at spirit healer in Vashj'ir should be fixed now.
- Standing still doing nothing in Vashj'ir is fixed.
Bugfixes
- There has been major changes to increase the performance of IB. It should run alot faster now.
- More improvements to party queueing.
Bugfixes
- Added support for Profile settings, read the document for more info and also look at herb/mining 1-525 version 2 to see an example of usage.
- Reverted to previous mail retrieval behavior, might be some slower but it's more stable.
- Numerous minor bug-fixes
- Fixed the 'unable to find Tripper.Tools.dll" error
- Professionbuddy now remembers its running status between sessions and no longer stops when Honorbuddy is stopped, This will allow Professionbuddy to work with reloggers
- Fixed an error in 1-300 herb profile.
- Fixed a string to float conversion error on machines running windows with non english regional settings.
Code:
[SIZE=3][COLOR=red]If you are getting this exception:
Invalid Executor, Styx.Helpers.CharacterSettings threw an exception, or
[/COLOR][/SIZE][SIZE=3][COLOR=red]Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid, or[/COLOR][/SIZE] [SIZE=3][COLOR=red]something similiar to that.
Then you need to do this /run print(GetCVar('gxApi'))[/COLOR]
[COLOR=red]open the chatbox in wow copy paste that press enter.
If it prints D3D9 ure all good if it says D3D11 you have to open your Config.wtf file and edit this row:
SET gxApi "D3D11"[/COLOR]
[COLOR=red]Make sure it looks like this:
[/COLOR][COLOR=red]SET gxApi "D3D9"[/COLOR][/SIZE][SIZE=3][COLOR=red]
[/COLOR][/SIZE]In order to use Hb your WoW client must be fully (100%) patched
Download Here: Honorbuddy 2.0.0.4555
