UseAbility causing console spam on arg0 around 20

[WildCard65]

Seems like BossTimer calling UseAbility causes 2 errors, one an index out of bound errors on the CallPushString in UseAbility(can't remember which of the 2) and another with forward saying max params reached. This happens when arg0 is around 20

[winstliu]

Why in the world would you have an arg0 that's 20. If I remember correctly the highest documented number it can go up to is 9.

[WildCard65]

to prevent ff2 itself from activating the ability

[winstliu]

That seems a bit hacky.

[WildCard65]

wierd thing, -20 doesn't cause such issue at same time reaching same goal 20 should do.

[WildCard65]

@50Wliu How about for ff2 2.0 you add arg-1 which can either be 1 or 0 and if it's 1, FF2 can NOT activate the ability, only subplugin that defines it can(Default value of 0 to preserve existing bosses)

[winstliu]

Why is setting arg0 to 7 not good enough?
Have you tried FF2_PreAbility or FF2_DoAbility?

[WildCard65]

I set to 20 just to give myself assurance that I'm futureproof incase ff2 reserves 1-19 for activation(if ever), right now my boss uses -20 and -21 to bypass the console spam while still achieve goal of not allowing ff2 to activate the ability(and let subplugin do it via DoAbility native)