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

Honorbuddy 2.0.0.3895 Discussion Thread

Status
Not open for further replies.

Nesox

Well-Known Member
Joined
Jan 15, 2010
Messages
1,563
Reaction score
48
DO NOT REPORT BUGS IN THIS THREAD!

They will be deleted.
Please post all bug reports on the bugtracker.
Link to release thread
 
Last edited:
Can already see its much faster, thanks
 
Thank you Nesox! It is now smooth. YAY.


Posted bug to bug tracker. Instancebuddy failed. and Session invalid.
 
Last edited:
Still doesn't pop into combat mode correctly when only the Pet is aggroed, but otherwise it is working much smoother (with experimental pathing turned off) then the previous version.

Seems a bit more crisp in the movements.
 
Still doesn't pop into combat mode correctly when only the Pet is aggroed, but otherwise it is working much smoother (with experimental pathing turned off) then the previous version.

Seems a bit more crisp in the movements.

Confirmed. Hunter's aren't entering combat when the pet is in combat ... using the default hunter CC that ships with this release.
 
Both AB and GB have this fixed. Ask CC authors to add a logic to target pet's target. When you are in combat, has no target, has pet and pet has target

Code:
if (StyxWoW.Me.CurrentTarget == null && StyxWoW.Me.GotAlivePet && StyxWoW.Me.Pet.CurrentTarget != null)
{
      StyxWoW.Me.Pet.CurrentTarget.Target();
}

new Decorator(
     ret => StyxWoW.Me.CurrentTarget == null &&
               StyxWoW.Me.GotAlivePet && 
               StyxWoW.Me.Pet.CurrentTarget != null,
     new Action(ret => StyxWoW.Me.Pet.CurrentTarget.Target()))

same post in 3 threads huh :)
 
woot thnx going to instal it just saw it man ur fast with updates
 
Having an issue with Logging in. Had the same issue with the last test version that was put out also. I can still log into the old version 804 without any problems. I keep getting:
Loading Honorbuddy 2.0.0.3895 settings.
Authenticating..
Authentication failed!
 
jdmscene, you do not have permission to access this page. This could be due to one of several reasons:

  1. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  2. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

I just tried to download it and I get this message
 
Both AB and GB have this fixed. Ask CC authors to add a logic to target pet's target. When you are in combat, has no target, has pet and pet has target

Code:
if (StyxWoW.Me.CurrentTarget == null && StyxWoW.Me.GotAlivePet && StyxWoW.Me.Pet.CurrentTarget != null)
{
      StyxWoW.Me.Pet.CurrentTarget.Target();
}

new Decorator(
     ret => StyxWoW.Me.CurrentTarget == null &&
               StyxWoW.Me.GotAlivePet && 
               StyxWoW.Me.Pet.CurrentTarget != null,
     new Action(ret => StyxWoW.Me.Pet.CurrentTarget.Target()))

same post in 3 threads huh :)

As I stated in my post ... I'm using the default hunter CC that ships with the product. I'd expect this to work out of the box with the stock default custom class. I trust you guys can handle something this simple without requiring me to run around and find the author for you.
 
As I stated in my post ... I'm using the default hunter CC that ships with the product. I'd expect this to work out of the box with the stock default custom class. I trust you guys can handle something this simple without requiring me to run around and find the author for you.

It's not a bug with the cc's it's the default targeting filter, it's not adding your pet's target if it aggro's something for w/e reason.
Haven't had time to fix it yet but will.. :)
 
It's not a bug with the cc's it's the default targeting filter, it's not adding your pet's target if it aggro's something for w/e reason.
Haven't had time to fix it yet but will.. :)

Fair enough. Thanks for the explanation Nesox.

Cheers-
Mega
 
It's not a bug with the cc's it's the default targeting filter, it's not adding your pet's target if it aggro's something for w/e reason.
Haven't had time to fix it yet but will.. :)

Hopefully soon that's the only thing preventing me from using the new Test releases. Glad to see you all are working on a fix though, looking forward to it.
 
It's not a bug with the cc's it's the default targeting filter, it's not adding your pet's target if it aggro's something for w/e reason.
Haven't had time to fix it yet but will.. :)

couldn't it be fixed with a plugin (for a temp fix?)
like
Put this in the plugin init
Targeting.Instance.IncludeTargetsFilter += IncludeTargetsFilter;

and then somewhere do.. something like
private static void IncludeTargetsFilter(List<WoWObject> incomingUnits, HashSet<WoWObject> outgoingUnits)
{
outgoingUnits = (from o in incomingUnits
where o.Type == WoWObjectType.Unit
orderby o.Distance ascending
let cUnit = o.ToUnit()
where (
(cUnit.GetThreatInfoFor(ObjectManager.Me).ThreatStatus != ThreatStatus.UnitNotInThreatTable || (ObjectManager.Me.GotAlivePet() && cUnit.GetThreatInforFor(ObjectManager.Pet).ThreatStatus) != ThreatStatus.UnitNotInThreatTable )
select o).ToList();



}

Just an idea.. havent' tried it though-_-;;
 
couldn't it be fixed with a plugin (for a temp fix?)
like
Put this in the plugin init


and then somewhere do.. something like


Just an idea.. havent' tried it though-_-;;

Code:
Targeting.Instance.IncludeTargetsFilter += IncludeTargetsFilter; 			 		
private static void IncludeTargetsFilter(List<WoWObject> incomingUnits, HashSet<WoWObject> outgoingUnits)
{
    if (!StyxWoW.Me.GotAlivePet || (StyxWoW.Me.GotAlivePet && !StyxWoW.Me.Pet.Combat))
        return;

    for(int i = 0; i < incomingUnits.Count; i++)
    {
        if(incomingUnits[i] is WoWUnit)
        {
            WoWUnit u = incomingUnits[i].ToUnit();
            if (u.Combat && (u.IsTargetingMeOrPet || u.PetAggro))
                outgoingUnits.Add(u);
        }
    }
}

you could try that if you want
 
Status
Not open for further replies.
Back
Top