Hi all, Ive fix this Holy Paladin Bug in recent update.This is why:
[14:50:46.494 D] Exception was thrown in BotBase.Root.Tick
[14:50:46.494 D] System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at A.c6b8f7979e4af4b107d84aacb997cab3f.c67ec6096131d9e653e9bb99ca61831f9(Object c3c3d8b8073752f88a39c678e185a68e3)
at TuanHA_Combat_Routine.Classname.TuanHA_Combat_Routine(Int32 CO_auraID, WoWUnit CO_target)
at TuanHA_Combat_Routine.Classname.TuanHA_Combat_Routine(WoWUnit CO_target)
at TuanHA_Combat_Routine.Classname.TuanHA_Combat_Routine(Object CO_ret)
at Styx.TreeSharp.Decorator.CanRun(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.(Action , String , Boolean )
Hi all, Ive fix this Holy Paladin Bug in recent update.
Just test Holy Paladin, heal is fine but the Priority feel like MoP version and we are now 3 week into WoD
I'm rewriting Holy Paladin from the ground, hope a major update will be there soon.
This is an exciting news. Paladin needs love !I'm rewriting Holy Paladin from the ground, hope a major update will be there soon.
[06:30:34.662 N]
Can you please update new rev, set log level to diagnostic, send me log?
Also please use the Current release NOT the BETA, BETA mean not tested and there's nothing sure it's bugging on this version or not.
You are using BETA Honorbuddy v2.5.12203.759 by the way.
I have the same problem!) Please help me. thanks in advanceA newer version of DNGuard Runtimer.............. .
i have the paid version - i put the .dll into the hb folder, i unlock the .zip - new hb -
routine doesnt load. i always get this : A newer version of DNGuard Runtimer.............. .
after using ret prem routine in pvp for a while ive noticed the following:
Utility:
- emancipate spam is fixed, however CR will use cooldowns like freedom/everyman in cases where it could spend the same gcd on emancipate and save those CDs.
- Blessing of Sac as Ret now has the ability to dispell magic from friendly target, and freedom can now be used to shave hostile ccs. does the CR currently have the ability to use sac/freedom on friendlies based on ccs on them? I havent noticed it so I've been manually working it
Dmg:
- Final verdict is taking a lower priority to some other abilities, which limits the amount of divine storm procs we can use. Moreover divine storm's priority is quite low as well even when we allow it to be used on single targets. As result the CR currently generates fewer DS procs (+100% dmg / range) and utilizes it less than it should.
btw, are comments like these helpful at all? Hoping to be able to contribute to the CRs i use the most.
The code Hand of Sac removed CC is already in MoP I just need time to bring them back for PvP in WoDafter using ret prem routine in pvp for a while ive noticed the following:
Utility:
- emancipate spam is fixed, however CR will use cooldowns like freedom/everyman in cases where it could spend the same gcd on emancipate and save those CDs.
- Blessing of Sac as Ret now has the ability to dispell magic from friendly target, and freedom can now be used to shave hostile ccs. does the CR currently have the ability to use sac/freedom on friendlies based on ccs on them? I havent noticed it so I've been manually working it
Dmg:
- Final verdict is taking a lower priority to some other abilities, which limits the amount of divine storm procs we can use. Moreover divine storm's priority is quite low as well even when we allow it to be used on single targets. As result the CR currently generates fewer DS procs (+100% dmg / range) and utilizes it less than it should.
btw, are comments like these helpful at all? Hoping to be able to contribute to the CRs i use the most.
The code Hand of Sac removed CC is already in MoP I just need time to bring them back for PvP in WoD
@totemz: I'll take a loot at T17 bonus soom, lol how come you already got it? The raid only start last 2 days...