Is AddLooseGameplayTags Behaving as Intended, or Is It a Bug?

Development Programming & Scripting Blueprint
, ,
1

Hello everyone,

I’m encountering a seemingly strange behavior with AddLooseGameplayTags in Unreal Engine 5.3 and 5.5, and I’d appreciate any insights or clarification.

I’ve always understood that Gameplay Tags are designed to prevent duplicate entries within a FGameplayTagContainer. However, I’ve observed that when using AddLooseGameplayTags, it appears to allow duplicate tags to be added.

For example, using a simple setup like this :

a1
a1930×638 178 KB

My questions are:

Is it intended behavior for Gameplay Tags to allow duplicate entries?
Is it possible that only AddLooseGameplayTags allows duplicate entries, while other methods respect the unique constraint?
Or is this potentially a bug?
I’ve tested this in both UE5.3 and UE5.5 and observed the same behavior. I’m hesitant to file a bug report without further confirmation, so I wanted to ask the community first. Any information or clarification would be greatly appreciated.
Sorry if this is a specification.

Thank you in advance.

※AI Translation

2

Sorry… it was a misunderstanding on my part.
Basically, GameplayTags are designed to stack, so this behavior is correct.
Since it’s only checked once when granting, I mistakenly thought that it would only be granted once.