> 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/demo-overview.md).

# Demo Overview

RooDemo is a Blueprint-focused example included with the plugin content. It demonstrates how the runtime systems can be presented in a game-facing interface.

Enable Show Plugin Content in the Content Browser, then browse to RooGameplayFramework/RooDemo.

The demo includes examples of:

* A player Stats Set with Stats and Attributes.
* Formula and Progression Table assets.
* Stat Actions for damage, healing, mana, experience, and level changes.
* Stackable Status Effects.
* Inventory items and equipment.
* Equipment-driven Stat modifiers.
* Inventory and equipment drag-and-drop widgets.
* Buff progress and stack UI.
* Tooltip and value display widgets.

## Demo tag namespace

All native Gameplay Tags supplied for the demo use the dedicated `RooRPGDemo` namespace. Examples include:

```
RooRPGDemo.Stats.Stat.AttackPower
RooRPGDemo.Stats.Attribute.Health
RooRPGDemo.Stats.StatusEffect.Hemorrhage
RooRPGDemo.Inventory.Equipment.Weapon
```

This keeps plugin demo tags separate from production tags. Do not use `RooRPGDemo` as the namespace of your own Stats Designer. Choose a project-owned namespace such as `MyGame` instead.

## What the demo is for

Use the demo to inspect asset configuration and Blueprint event flow. It is not required by the runtime plugin, and your production project does not need to copy the demo HUD.

Useful starting assets include the RooDemo map, `WBP_RooDemoHUD`, the Player Stats Set, example equipment items, and example Status Effects.

## Recommended review order

1. Open the Player Stats Designer and confirm its Tag Namespace is `RooRPGDemo`.
2. Open the Player Stats Set and inspect the referenced Stat and Attribute assets.
3. Open one Formula asset and its optional Progression Table.
4. Open one Status Effect and inspect its stack, duration, tick, and action settings.
5. Open one equipment item and inspect its Properties.
6. Open the demo HUD and follow the component queries and event bindings.

## Production guidance

Treat RooDemo assets as examples. Create project-owned Stats Designers, Stats Sets, Status Effects, items, and UI in your own content directory. Give each production Designer a project-owned Tag Namespace before adding definitions. This keeps your tags and assets separate from plugin updates and makes migration easier.