> For the complete documentation index, see [llms.txt](https://roogame.gitbook.io/roogame/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://roogame.gitbook.io/roogame/roo-gameplay-framework/getting-started/quick-start.md).

# Quick Start

This guide creates one Stat, one Attribute, and one runtime Stats Component.

## 1. Create a Stats Designer

In the Content Browser, choose the folder that should own the generated assets. Right-click inside that folder and select `RooGame > Stat > Roo Stats Designer`. Name the new asset `DA_GameStatsDesigner`.

Double-click the asset to open Stats Designer.

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2FG1vhEImHBe0BcIA5B3hF%2Fimage.png?alt=media&#x26;token=01bea748-0ec0-4033-b728-b25bfd68fda7" alt=""><figcaption></figcaption></figure>

## 2. Choose a Tag Namespace

At the top of Stats Designer, set Tag Namespace before adding definitions. A newly created Designer defaults to `RooGame`; you may keep it or replace it with a project-specific value such as `MyGame`.

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2FizUNhpqhntKOmD2W9ge9%2Fimage.png?alt=media&#x26;token=2cf9b31a-041e-4c0a-a5ee-c75e98101587" alt=""><figcaption></figcaption></figure>

The namespace belongs to this Designer Data Asset. It determines the two tag roots used by the left panel:

```
MyGame.Stats.Stat
MyGame.Stats.Attribute
```

Use letters, numbers, underscores, and dots. Do not use the demo namespace `RooRPGDemo` for production content.

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2FCSr8KOcJqPrhTmBcy2u1%2Fimage.png?alt=media&#x26;token=ac1a2c7f-a61c-4dda-b89d-262424c922c6" alt="" width="563"><figcaption></figcaption></figure>

## 3. Add definitions

In the left panel:

1. Add MaxHealth under Stats.
2. Add Health under Attributes.
3. Keep both definitions enabled.

With the example `MyGame` namespace, the Designer writes:

```
MyGame.Stats.Stat.MaxHealth
MyGame.Stats.Attribute.Health
```

The Designer also ensures the namespace, Stats, Stat, and Attribute root entries exist in `Config/DefaultGameplayTags.ini`.

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2Ff1tTSjGH7EY2Dexq3MMt%2Fimage.png?alt=media&#x26;token=cedc29f9-da31-4d3e-a58c-9ad406d57b35" alt=""><figcaption></figcaption></figure>

## 4. Create the Stats Set

Enter Player as the new set name in the center panel and click +. Click Use to create the first set and its Stat and Attribute assets.

Generated layout:

```
DA_PlayerStatsDesigner/
  Stats/
    Player/
      DA_StatsSet_Player
      Stats/
        DA_Stat_MaxHealth
      Attributes/
        DA_Attribute_Health
```

The actual root is the directory containing your Designer Data Asset.

## 5. Configure values

In the Player row:

1. Set Stat.MaxHealth.Base to 100.
2. Set Attr.Health.Min to 0.
3. Assign `DA_Stat_MaxHealth` to Attr.Health.MaxStat.
4. Set Attr.Health.StartPercent to 1.
5. Click Use again.

StartPercent uses a range from 0 to 1. A value of 1 starts Health at 100 percent of MaxHealth.

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2FGugGJDSb4m5xaEFcIkJY%2Fimage.png?alt=media&#x26;token=9c5507d8-18f3-4f35-bd1f-a695b6c9d02e" alt=""><figcaption></figcaption></figure>

## 6. Add the runtime component

Open an Actor or Character Blueprint:

1. Add Roo Stats Component.
2. Assign `DA_StatsSet_Player` to Stat Value Config.
3. Compile the Blueprint.

The component initializes automatically during Begin Play. Queries also initialize it on demand if needed.

## 7. Read values

Use either tag-based or name-based Blueprint nodes:

```
Get Stat Value By Tag
Get Stat Value By Name
Get Attribute Value By Tag
Get Attribute Value By Name
Get Attribute Max Value By Tag
Get Attribute Ratio By Tag
```

<figure><img src="https://2218703886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4YPyrdOyfjDGtlxlvjSd%2Fuploads%2FcdPvmhUX1MW7ce73k8Zk%2Fimage.png?alt=media&#x26;token=9d2ed59e-57fd-4cf1-97fc-a381e5a40763" alt=""><figcaption></figcaption></figure>

For name-based lookup, MaxHealth and Health are valid short names when they resolve uniquely in the component. Tag-based lookup is the safest option for large projects.

Expected initial result:

```
MaxHealth = 100
Health = 100
Health Ratio = 1
```

## Common mistakes

Set the namespace before creating tags and generated assets. Changing the namespace switches the Designer to a different tag hierarchy; it does not rename or migrate definitions from the previous hierarchy.
