Data Systems Inspector

Module: Design · Category: Systems · Tool ID: DataSystemsInspector

A two-tab inspector for the project’s tag and data systems. Tags browses the gameplay tag hierarchy with depth and source info. Data Tables audits every Data Table for column fill rate and duplicate rows.

Inspector open on Tags tab with hierarchical tag tree visible, source column showing tag origins.

When to use it

• Refactoring a tag taxonomy: seeing the full hierarchy and where tags come from
• Auditing data tables for missing rows or duplicate keys
• Pre-shipping check: confirming every tag in the project is registered correctly

What it isn’t for

• Don’t expect tag editing. UE’s GameplayTagsManager owns that.
• Don’t expect data table editing. Use the Data Table editor.

Opening the tool

1. Open the EQLabs Hub and search for Tags or Data Table (or browse to Design → Systems).
2. Click the tool card.
3. Use the tab bar: Tags or Data Tables.

Tab 1: Gameplay Tag Browser

Hierarchical view of every registered tag.

Section	What it does
Scan button	Enumerates registered tags via UGameplayTagsManager
Tag tree	Depth-indented hierarchy
Source column	Where the tag is registered (.ini, plugin, etc.)
Search	Filter by tag name

Tab 2: Data Table Inspector

Per-DataTable column fill-rate and duplicate-row analysis.

Section	What it does
Scan Path	Folder to scan
Scan	Walks every UDataTable
Tables list	Per-table row: name, row count, column count, fill rate, duplicate row flag
Per-table drill-in	Click to see column-by-column fill stats

Tables list with fill-rate column visible, one row flagged for duplicates.

Workflow

Auditing tags

1. Switch to Tags tab.
2. Click Scan.
3. Walk the hierarchy, search for specific tags.

Auditing data tables

1. Switch to Data Tables tab.
2. Set scan path, click Scan.
3. Sort by fill rate ascending — low fill rates indicate sparse data tables.
4. Click rows with duplicate flags to drill in.

Settings reference

Field	Default
Scan Path (Data Tables tab)	/Game

Settings file: [Project]/Saved/EQLabs/Settings/DataSystemsInspector.json

Output

• In-panel tag tree and tables list.
• No edits. Read-only.

Tips and gotchas

• Tag source matters. Tags from .ini files are easy to remove; tags from plugins are harder.
• Low fill rate isn’t always a bug. Sometimes tables are sparse on purpose. Use as signal.
• Duplicate keys in data tables are usually bugs. UE allows them but lookup is undefined.

Related tools

• Modeling-to-Gameplay Tag Pipeline — assigns tags to mesh sections + auto-generates trigger volumes