walter
Active Member
- Joined
- Jun 25, 2012
- Messages
- 1,112
- Reaction score
- 10
Ravage for maras.
I know what your saying and you are correct. WaitforCast is absolutely useless in Joe's routine because the routine is not using TreeSharp behaviors (AI based behaviors) and instead written with businesslogic.
He 'fixed it' by putting thread sleeps everywhere which caused significant performance issues and botbreaking behavior. Could you test the following correction for me:
Say you are a shield specialist vanguard. Open up Test Build/DefaultCombat/Routines/Advanced/ShieldSpecialist.cs
Where you see
Code:public static Composite ShieldSpecialistCombat() { return new Sequence( new Action(ret => { MercHelpers.SSCombat(); }), Spell.Cast("Recharge and Reload", ret => false)); }
Make it instead:
Code:public static Composite ShieldSpecialistCombat() { return new PrioritySelector( Spell.WaitForCast(), new Action(ret => { MercHelpers.SSCombat(); }), Spell.Cast("Recharge and Reload", ret => false)); }
let me know if that fixes it. If so I'll implement it throughout.
I will test this again but I am sure it won't do much but an optical illusion since this isn't set up in tree sharp.