Originally Posted by
Numba1stunna1
-I haven't used this profile, but you can write the program so that for a specific inputted SpellID, you can make it have filters to prevent it from failing to cast (you probably already did that, probably not).
-Have a priority list for the spells. For instance, my dk profile has (mind freeze, pet charge disrupt, death grip, pet stun, and Strangulate -- Cata). It tries to first use Mind Freeze. All of them have filters for so they don't fail (like no spell immunity, in range, enough runic power, and no disrupt immunity for mind freeze, and so forth).
-Have a randomizer so that every time the UnitCastingInfo (or UnitChannelingInfo) exists, then set a math.rand between the end of the cast and the beginning. For instance, kick between 40% and 70%.
-Have an auto latency compensation using NetStat.
-Require a LoS check and/or Facing Check and/or Range Check and/or Position Check (like gouge requires target facing you and you facing target). Every ability has different requirements.
Again, these are just ideas I am throwing out. I never actually tried/looked at the scripts of your program. Thanks.