Hello.
I am baffled by the largely C++ exclusive nature of the Detection by Affiliation feature of the AIPerception Component. As I understand the feature, it should help optimize a project by limiting perceived stimuli to only those that are relevant. The AIPerception Component includes Detection by Affiliation for each added sense. However the Team system and relevant Enum creation are limited to C++. The entirety of the project I am working on, including the relevant Characters, are in Blueprints. As such, I either need to convert existing parts of the project to C++ or utilize Tags instead. Both solutions are, in my opinion sub-optimal. Converting portions of the project to C++ has the potential to be a long and arduous task. Based on my understanding, Tags would still require the Character to process the stimuli, at least to a greater extent than the affiliation system would. In addition, the Tag solution has the potential to necessitate nested if statements.
My sanity may not be recoverable, but implementing this feature into Blueprints can still save the time of other Devs and spare them from headaches. (Please pardon my melodrama, it’s mostly for laughs.)
I will also note that it might be worthwhile to look into optimizing the usage of Tags separately. Even if it wouldn’t improve performance, a special Switch on Tags Flow control Node that can accommodate one or more tags within each case would at least help the code to look cleaner.