Heya, I didn’t find a way to do this.
My research led me into finding that
- In order for the EQS to use a custom container for the Tag check, it would need to see a variable or “parameter” from somewhere
- Because the EQS is ran from a Behaviour Tree the Tag container would need to be an Object Type Blackboard key which is then fed into the parameters of the EQS query
Review:
In order for the EQS query to accept the tag container as a parameter inside the Behaviour tree, the EQS source code would need to be edited to support the parameter inside the GamePlayTag Checker parts of that script, and any other related scripts.
Workaround:
This may actually determent my attempt at implementing faster AI using EQS and small behaviour trees with few tasks, but I “could” include a task after an EQS returns a list of any object with gameplay tags of “enemy” for example, and then sort that list in a for loop task using the new 4.16 available gameplay tag queries / nodes:
These are a few of those.
Let me know if this is a good approach to battles which may contain upwards of 200 active combatants attacking each other like so