[SOLVED] Bug? Target Self when Ability Target != Self (i.e. Ally, All)

dragosun

GiL, Others,

I'm currently working on my game's custom AI system (modelled of FFXII Gambit System) using ORK Battle AIs.

I have an issue shown by a simple test below using 2 combatants and different AI 'Check Status ' targets and ability 'target types' trying to cast a simple heal.

Check | Target Type | Found Targets |Cast Success

Ally | Ally | 2 | Yes
Ally | Self | 2 | Yes
Self | Ally | 1 | No
Self | Self | 1 | Yes
Self | All | 1 | No

If I test with one combatant, the first test (Ally, Ally) also fails.

So the issue is, that I cannot cast on self unless ability target type is specifically set to 'Self'. I have not ticked 'Not on Self'. Given that 'Check Status' 'Ally' returns the user combatant I am wondering if this is a bug. Surely you would set a heal as target type 'Ally' and all members of the group should be valid targets.

The above shows how I set up the event. 'Store target' is a custom event used to store targets on the user's custom <TargetVariableComponent>. It is a simple method of storing targets and retrieving them later. In this setup it does nothing but ensure I could debug the found target list so it can be ignored.

gamingislove

I can't confirm that - did a quick test with a similar setup (checking Self and using an Ally ability) and the ability was used on the user combatant (i.e. self).

dragosun

Thanks for the prompt response GiL. Unfortunately, it does not work for me and is driving me nuts.

With some more testing I have confirmed that if I set they target to 'Ally' I can target self manually (using battle menu). I even created a fresh ability to check and got the same issue.

Using the AI posted above: without changing any other settings, changing target from 'Ally' to 'Self' solves the problem of the enemy not healing themselves. As I said, using my custom event step I have debugged (using Visual Studio) and confirmed the found target list contains the 'self' game object.

So it SHOULD work, but somehow does not.

I will re-import ORK to see if that solves the issue.

gamingislove

Things that can interfere with using found targets are the preferred targets (based on the combatant's AI settings) and auto target settings of the ability. Try enabling Force Found Targets in the action step.

dragosun

Your a champ GiL. Got it working.

For some reason, I had Preferred Target - Nearest Target enabled. I guess this overwrote the found targets check, even with Force Found Targets enabled and tried to grab closest target, thus excluding the self.

Just to check - is this intended behaviour though? Surely if there is no Nearest Target (i.e. closest ally) then self should be included for 'ally' abilities target list?

Anyway, thanks again. After 3 nights of pulling my hair out it is working. An with that, my AI system is all-systems go (at least until my next issue :P)