#Tag Containers

A tag container is a collection of Gameplay Tags. Containers let one object, variable, or property hold multiple labels at the same time.

Example:

Faction.Enemy
Character.State.Burning
Damage.Resistance.Fire
Interaction.Usable

This makes gameplay logic composable. An object can be an enemy, burning, fire-resistant, and usable without requiring four unrelated booleans.

ScreenshotOpen full size ↗

#GameplayTagComponent

Add Game Creator > Gameplay Tags > Gameplay Tag Component to any GameObject that should participate in tag-based logic.

Common examples:

• Player and enemy prefabs.
• Interactable objects.
• Pickups and loot.
• Doors, chests, switches, traps.
• Quest objects.
• Area triggers.

The component exposes a runtime tag container that can be read or changed by Game Creator and C#.

#Container Mode and Single Tag Mode

Container mode is the most flexible and is the best default for most gameplay objects.

Single Tag mode is useful for exclusive categories:

Quest.Main.Available
Quest.Main.Active
Quest.Main.Completed

When a new tag is set in Single Tag mode, it replaces the previous tag.

#Add, Remove, Clear, and Set

Tags can be changed at runtime through Game Creator Actions:

Typical status effect flow:

1. Add Character.State.Burning when the fire effect starts.
2. Conditions check that tag to change behavior.
3. Remove Character.State.Burning when the effect ends.

#Runtime Matching

Containers support direct tag checks and container queries:

Matching can be exact or include children.

Owned: Damage.Type.Fire
Query: Damage.Type
Mode: Include Children
Result: true

#Runtime Behavior

At runtime:

• Adding an empty None tag does nothing.
• Duplicate tags are ignored.
• Containers are normalized and sorted.
• Removing a tag that is not present does nothing.
• Clearing an empty container does nothing.
• Tags are resolved through redirects when using the service and component APIs.
• Undefined tags can warn in the Editor or development builds.

Tip
Use tags for meaning, not values. Damage.Type.Fire is a good tag. Damage.Amount.25 should be a number variable instead.

#Tag Change Events

GameplayTagComponent exposes runtime events:

• EventTagsChanged
• EventTagAdded
• EventTagRemoved

Game Creator also includes tag-based Events:

#Saving Runtime Tags

The plugin includes a Game Creator memory type:

Game Object/Gameplay Tags

Use it when runtime tags on a GameplayTagComponent should be remembered by Game Creator save systems.

#C# Example

using SkywardGames.Runtime.GameplayTags;
using UnityEngine;

public class BurningState : MonoBehaviour
{
    [SerializeField] private GameplayTagComponent tags;

    private static readonly GameplayTag Burning =
        GameplayTag.FromPath("Character.State.Burning");

    public void Apply()
    {
        tags.AddTag(Burning);
    }

    public void Remove()
    {
        tags.RemoveTag(Burning);
    }
}

#Practical Use Cases

#Character States

Character.State.Stunned
Character.State.Burning
Character.State.Invulnerable

Use these to enable or block movement, attacks, abilities, prompts, and AI decisions.

#Combat Filtering

Faction.Enemy
Faction.Ally
Damage.Type.Fire
Damage.Resistance.Fire

Use these to filter targets and drive damage responses.

#Interaction Rules

Interaction.Usable
Interaction.Locked
Interaction.Usable.Door

Use these for raycasts, overlap checks, prompts, and interaction branches.