Gameplay TagsGame Creator 2 Module
Game Creator 2 Module

Gameplay Tags for Game Creator 2

Hierarchical gameplay tags, tag containers, Reactions, Game Creator Actions, Conditions, Events, Scene View debug gizmos, and a runtime C# API for cleaner gameplay logic.

Start with the guide Skyward Games Website Support Discord

Gameplay Tags for Game Creator 2 brings an Unreal Engine-style Gameplay Tags workflow to Unity and Game Creator 2. It gives your project a shared, searchable language for gameplay state, object identity, factions, damage types, quests, interactions, reactive behaviors, and more.

Instead of scattering booleans and hand-typed strings across Actions, Conditions, prefabs, and scripts, you define tags once and reuse them everywhere.

Character.State.Stunned
Character.State.Burning
Damage.Type.Fire
Faction.Enemy
Quest.Main.Completed
Interaction.Usable.Door
ScreenshotOpen full size ↗
Gameplay Tags settings window with hierarchy and details panel
Gameplay Tags settings window with the hierarchy on the left and the details panel on the right.

#Why Gameplay Tags?

Gameplay Tags solve a common production problem: as a project grows, gameplay logic becomes harder to read and harder to maintain.

Without tags, logic often becomes a mix of:

IsStunned = true
IsBurning = true
EnemyType = "Undead"
DamageType = "Fire"

That works for prototypes, but it does not scale well across designers, prefabs, Game Creator graphs, save data, and custom scripts.

Gameplay Tags help you build cleaner systems because they are:

  • Centralized: Define tags in one project database.
  • Reusable: Use the same tags in Actions, Conditions, Events, Reactions, Variables, inspectors, and scripts.
  • Hierarchical: Query broad categories like Damage.Type or specific tags like Damage.Type.Fire.
  • Reactive: Automatically trigger visual scripting logic when tagged GameObjects are created, enabled, disabled, destroyed, or mutate their tags.
  • Visual Diagnostics: Real-time floating Scene View debug badges in Edit Mode and Play Mode without runtime performance cost in release builds.
  • Readable: Logic communicates design intent directly.
  • Designer-friendly: Pick tags from dropdowns instead of typing strings by hand.

#Main Features

Feature What It Helps With
Hierarchical tags Organize gameplay concepts with dot syntax.
Parent/child matching Match exact tags or broad categories.
Tag database Manage project tags in a central Game Creator settings page.
Tag picker dropdowns Select valid tags in inspectors and Game Creator fields.
Tag containers Store multiple tags on objects, variables, and properties.
Gameplay Tag Reactions Automatically trigger visual scripting logic on object creation, enable, disable, destruction, or tag mutations.
Scene View Debug Gizmos Real-time floating tag badges with connection guidelines and anchor discs in Edit & Play Mode.
Game Creator Actions Add, remove, set, mutate, loop (For Each), find, filter, raycast, and overlap by tags.
Game Creator Conditions Branch logic based on tags, containers, and active reactions.
Game Creator Events React to lifecycle changes, tag additions/removals, triggers, and collisions.
Runtime API Use Gameplay Tags, containers, reactions, and queries from custom C# systems.
Validation tools Detect invalid paths, duplicates, and redirect issues.

#Quick Start

  1. Open the Gameplay Tags settings page in Game Creator.
  2. Create a tag such as Character.State.Stunned.
  3. Add a GameplayTagComponent to a player, enemy, or interactable prefab.
  4. Assign one or more tags to that component.
  5. Use Game Creator Actions, Conditions, or Gameplay Tag Reactions to drive reactive logic during gameplay.
VideoOpen video ↗
Creating a Gameplay Tag and using it in a Game Creator Condition.

#Documentation

#A Simple Example

Imagine an enemy becomes stunned.

With Gameplay Tags:

  1. Add Character.State.Stunned to the enemy.
  2. Movement logic checks whether the enemy has that tag.
  3. AI logic checks the same tag before attacking.
  4. UI logic can show a stunned indicator.
  5. When the stun ends, remove the tag.

The tag becomes a shared gameplay fact. Every system reads the same state, using the same name, without duplicating variables or string constants.

#When to Use Gameplay Tags

Use Gameplay Tags for:

  • Character states.
  • Factions and teams.
  • Damage types and resistances.
  • Quest states and quest categories.
  • Interaction types.
  • Item categories.
  • Abilities, buffs, debuffs, and gameplay flags.
  • Reactive spawn scaling and lifecycle behaviors.

Use variables or custom data for:

  • Health, mana, stamina, score, currency, or quantities.
  • Timers, cooldowns, and durations.
  • Object references.
  • User-facing text.
  • Values that require math, ranges, or sorting.

Documentation Sections

Getting StartedCreate your first tag and use it in Game Creator 2.Gameplay Tags OverviewUnderstand hierarchy, dot syntax, and matching.Tag ManagerManage, validate, rename, import, and export tags.Tag ContainersStore and query multiple tags on objects and variables.Gameplay Tag ReactionsReact automatically to object spawns, lifecycle events, and batch loops.Game Creator ActionsUse tags from Game Creator visual scripting Actions.Game Creator ConditionsBranch logic with tag-aware Conditions.Scripting APIUse the runtime API from custom C# scripts.Best PracticesOrganize tags cleanly and avoid overengineering.FAQAnswers to common setup and workflow questions.ChangelogRelease notes and version history.