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

Honorbuddy 2.5.7230.621

Status
Not open for further replies.

raphus

Well-Known Member
Joined
Jun 17, 2010
Messages
2,094
Reaction score
492
b_image_1_4.png


Honorbuddy v2.5.7230.621

Changelog

Code:
General
-----------------
* Honorbuddy now comes with as a MSI installer as well as a zip archive. The installer checks for .NET Framework and Microsoft Visual C++ Redist installations on the system and installs them if they are missing.
* Professionbuddy is included in the release once again.
* Stuck handler uses IsActuallyInCombat now instead of single Combat check. Previously in some cases it was failing to detect that character is stuck while its affected with the combat bug.
* 1418 new spells from patch 5.3 have been added to Spells.bin
* LeaderPlugin no longer rolls on loot.


UI Changes
-----------------
* You can now select the UI language from Settings&Tools window.
* The text in Info panel can now be copied.


AutoEquip2
-----------------
* Autoequip can now equip BindOnEquip items if they are already soulbound to the player


API
-----------------
* WoWUnit.Gender has been added back.
* IsSafelyFacing viewDegrees changed to 100 (from 150). Now in line with overloading methods.
* PendingCursorSpell should be return correct values now.
* Added BotBase.RequiresProfileScope which return true by default. When its off, HB will disregard Min/MaxLevel fields in profiles.
* WoWFishingBobber - IsBobbing works again. 
* GetTotalAbsorbs and TotalAbsorbs properties added in WoWUnit. 
* Added Icon in WoWSpell
* Battlegrounds.Current returns correct value for Deepwind Gorge now
* Added BlacklistFlags.Pull and BlacklistFlags.Interact. Pull flag can be used for mobs that we don't want to pull, but fight back in case we aggro them. Combat flag can be used for bugged/evading mobs that we must avoid no matter what.
* Ghost wolf and Travel form usages has been removed from mounting and it left to be handled by combat routines. You can hook OnMount event for own implementation.
* Added IncomingHealsCount(), IncomingHealsArray(),  GetPredictedHealth(bool includedMyHeals), and  GetPredictedHealthPercent(bool includeMyHeals)


Dungeonbuddy
-----------------
* [New] Add the normal difficulty versions of Gate of the Setting Sun and Siege of Nuizao Temple scripts and profiles.
* [New] Added scripts and profiles for the new 5.3 normal scenarios.
* [New] Added a new class, 'SpellActionButton', which provides useful info for spells on action bars such as the vehicle, pet or the 'extra button' bars.
* [New] Added HasBonusStep and IsBonusStepComplete to ScriptHelpers.ScenarioInfo
* [New] Added Dynamic Blackspots feature. 
* [Changed] Queue accept time is now randomized.
* [Changed] Merged all MOP heroic instance scripts with the normals versions.
* [Changed] Added some minor tweaks to targeting and raid following.
* [Fixed] Fixed exception caused by raid following logic.


Gatherbuddy
-----------------
* Added RandomizationFactor setting for GB2 which allows to determine how big the randomization is for hotspots. You can increase this value to create big random profiles.
* Green Tea Leaf and Ghost Iron will be shown at Node list at 1 skill


Questing
-----------------
* Fixed a bug with quest pickups where it gets stuck in an open/close quest window loop
* Fixed a bug in Quest pick up, should never try to pickup a completed quest now.
* It doesn't care about quest giver's location now if the quest is already completed. (Avoids unnecessary bot stops due to Can't find npc by id)
* Quests with wrong cached data for their objectives on can be overridden properly now.
* RunTo will be done if a quest id is specified and you don't have the quest in log


Singular
-----------------
General
* change - Current target monitoring in debug also watches pets target
* change - suppress exceptions occurring when weighting heal targets for all healers
* change - resized columns on General tab so setting names are less likely to be clipped
* fixed - Infrequent exception occurring when checking if pet battle in progress
* fixed - infrequent bug where movement stopped when HonorBuddy wants to mount but cannot
* fixed - movement while in a quest vehicle disabled
* fixed - issue impacting automatic cast of spells which allow casting while moving. 
* fixed - exception caused by log message from CastOnGround when Debug is enabled
* fixed - will now always update bot detected when bot starts.  corrects infrequent but repeatable issue when switching bots
* fixed - uses a local function for checking cursor for a pending target spell cast while awaiting change to API in HonorBuddy.  Should no longer spam message about /cancel spell cast Guild Tabard, etc. on every spell cast
* fixed - infrequent exception occurring when casting spell and checking certain classes for ability to cast while moving
* fixed - corrected test in CastOnGround to use local pending spell test. should no longer receive misleading /cancel message on every ground ability cast 


Druid
* fixed - Balance - Wild Mushroom and Detonate revised.  Will now output message as to target being cast upon.  Will detonate when 3 mushrooms exist or existing mushrooms have aged more than 4 seconds.


Hunter
* new* - All Specs - support for context specific pets now working.  Settings can be used to select pets specific for Solo, PVP, and Instances.  Defaults to Pet #1 if you don't have pet of number given.  Will dismiss Pets if needed.  NOTE: due to the information available at that moment, you may get a failed Ressurection cast on your Pet during pet changes.  This is expected presently.
* change - All Specs - will output message indicating status of Growl auto-cast when changing contexts (entering / exiting an instance for example.)
* fixed - Lowbie - bug causing Hunters at Level 1 through 9 to attempt to Dismiss Pet before spell is learned.
* fixed - All Specs - resolved bug impacting handling of Growl when entering/exiting instances.
* fixed - All Specs - exception occurring when the Disable Pet Usage option is set
* fixed - All Specs - modified AoE priorites. added Explosive Trap to Beast Master and Marksman
* fixed - All Specs - Blink Strike was still found by HonorBuddy SpellManager so at times Singular was attempting to cast.  reference within Singular removed


Mage
* change - Arcane - improved debug log output
* change - Frost - improved debug log output
* fixed - All Specs - will now correctly cast Ice Floes if needed


Monk
* change - Mistweaver - Pull behavior (when solo) now has *****ling Jade Lightning at the highest priority (previously was Provoke) so some ranged damage can be achieved.  Continues to use Jab as Chi generator during Combat due to higher DPS (in general.)


Paladin
* fixed - Protection - exception occurring when no current target selected


Priest
* new* - Discipline - rewrite of all Disc behaviors.  Now supports configuration for healing contexts in Group Healing tab of Class Config.  Now supports Atonement Healing and improved damage in all contexts
* fixed - Holy - fixed bug where Prayer of Mending spell was not available accept when Cascade talent was selected.


Shaman
* fixed - All Specs - will now correctly cast Spiritwalker's Grace if needed
* fixed - Restoration - was previously setup for long range Pull behavior ( 35 - 40 yds ) which is out of range of spells.  Corrected to medium range Pull ( 25 - 30 yds ).  The reference to Pull here is regarding internal logic and has no relation to the Pull Distance setting in HonorBuddy
* fixed - Elem/Resto - issue with setting/refreshing totems in some circumstances (like solo testing on training dummy with instance behaviors....)


Warlock
* new* - Destruction - implemented two spell priorities (Noxxic and Icy Veins) which can be selected by COnfig Setting
* fixed - Demonology - now applies DoT appropriate for current form prior to switching form
* fixed - Demonology - no longer casting Soul Fire without Molten Core aura active
* fixed - Destruction (Priority 2) - no longer consumes Backdraft with Chaos Bolt
* fixed - Destruction (Priority 2) - will now only cast Rain of Fire on single target if it is instant
* fixed - Destruction - cast of Havoc when > 1 target
* fixed - Destruction - bug in retrieving the number of stacks of Backdraft
* fixed - Destruction - added Rain of Fire to single target spell priority



Download From: Installer (recommended) / Zip

Requirements



Reporting Bugs
When reporting a bug, please include your full log file (found in your bot folder under the "Logs" directory, sort by creation date to find it easier), a full and detailed explanation of the bug, as well as any screenshots that may be useful in tracking down the bug.

Enjoy!
 
Last edited by a moderator:
Honorbuddy v2.5.7230.621 started.
Logging in...
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #17055
You are currently on build #0
-------------------------------
 
Honorbuddy v2.5.7230.621 started.
Logging in...
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #17055
You are currently on build #0
-------------------------------
Same here dosent work :(
 
CurrentPendingCursorSpell seems to return false at all times, kinda messes up PvP for me :P
 
when i start kicks questing
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\DebuggingTheTerrace.cs(20,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\Laosy.cs(20,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\LittleHatchlings.cs(20,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\MantidUnderFire.cs(16,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\Pompfruit.cs(24,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\RidingTheStorm.cs(24,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\Silkfeather.cs(20,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\ThunderingSkies.cs(20,18) : error CS0101: The namespace 'Blastranaar' already contains a definition for 'Blastranaar'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\Deprecated\Escort6641.cs(20,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.Escort6641' already contains a definition for 'Escort6641'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\SpecificQuests\DeathknightStart\FindAndBeatNpcs.cs(35,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.FindAndBeatNpcs' already contains a definition for 'FindAndBeatNpcs'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\SpecificQuests\DeathknightStart\IntotheRealmofShadows.cs(31,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.IntotheRealmofShadows' already contains a definition for 'IntotheRealmofShadows'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\SpecificQuests\DeathknightStart\TheGiftThatKeepsOnGiving.cs(44,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.TheGiftThatKeepsOnGiving' already contains a definition for 'TheGiftThatKeepsOnGiving'
[Compiler Error]: x:\Desktop\Honorbuddy\Quest Behaviors\SpecificQuests\DeathknightStart\TheGiftThatKeepsOnGiving.cs(299,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.TheGiftThatKeepsOnGiving' already contains a definition for 'WoWUnitExtentions'

O.o
 
Honorbuddy v2.5.7230.621 started.
Logging in...
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #17055
You are currently on build #0
-------------------------------
:/
 
Humph, looks like the new AutoEquip has a few of my older modifications included yet there's no mention of those in the changelog. I see the selectable disenchanting is in there.
 
[Bot] Warden upgrade! Be careful!!!

An opcode named SMSG_EnableHonorbuddyDetection have been added into the WoW client since the early 5.3.0 PTR patches, if the server send it, the WoW Client receive it and will add a "jmp" into FrameScript_Load to hook the calls to that function. The check range is recursivly n + 1, so FrameScript_LoadBuffer must be not safe, but I'm not sure about this part.

if the function is call from somewhere else than the .text of FrameScript_LoadBuffer, it will send back data to Blizzard servers and flag you "using Honorbuddy" for a banwave mostly.

This paquet has been started to be active since yesterday, on 17055 build. It was off all the rest of the time.

To avoid a detection, you can either have a good anti-warden and keep using it (as the paquet received are really rare... maybe it's done by "if you are online more than 10hours, you receive it", I don't know when they send it exactly, but for sure, not everytime).

Or you can simply stop to use both of that functions FrameScript_LoadBuffer and FrameScript_Load.

HB used to use this function FS_Load for direct access to LUA return of values.

example
var myVar = FS_Load("return UnitHealth()");

rather than :
FrameScript_ExecuteBuffer("HP = UnitHealth()");
var myVar = FrameScript_GetLocalizedText("HP");

The HB text is a part lie, because not so much bot or hacks used to have Fs_Load or Fs_LoadBuffer, my project TheNoobBot don't use it at all for instance.
And the goal of that detection was trully for Honorbuddy as blizzard named the opcode as is. (EnableHonorbuddyDetection)

So devs, can you tell us what will happen with the HB-specific detection method? For each individual users, would the tripwire or whatever method you have disconnect us before this new code triggers and tags an account? whatever this whole process does "it will send back data to Blizzard servers and flag you "using Honorbuddy" for a banwave mostly. This paquet has been started to be active since yesterday, on 17055 build. It was off all the rest of the time.", it won't work vs this HB release, right?
 
Status
Not open for further replies.
Back
Top