Add a Gameplay Tag Container to the Actor class

General Feedback & Requests
, ,
1

If possible could we get a Gameplay Tag Container added to the AActor class by default. It would make it so much easier to work with them between actors and allow you to actually manipulate actors with tags without having to cast to a higher level class or set up an interface on every actor that you want to use gameplay tags on. In fact, there are some blueprint nodes, such as “Get All Actors of Class Matching Tag Query” that literally do nothing since AActor does not implement the IGameplayTagAssetInterface by default.

Here is an example of setting up gameplay tags to work with an actor, but it requires doing this on every actor type you have. It also requires you to jump in C++, which rules out doing this in blueprint only projects as the IGameplayTagAssetInterface isn’t available in blueprint. This interface should be implemented on AActor by default.

2

Agreed. That would make lots of sense.

1 Like
3

I fully agree. Deprecate the actor’s tag name array and add a tag container. Actors have so much rubbish inside that it wouldn’t make a difference.

4

Bump. Now I’m trying to make my game detect which type of actors hit a collider based on tags so that I could cast them to respective classes. The actor tag works okay but apparently it’s less ideal than gameplay tag. But in order to access gameplay tags I’d have to cast the actors to child classes first, which makes no sense in my situation. It would be nice if it’s a default actor class feature.