Skip to content

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.

Screenshot 01 — Hero shot — Inspector open on Tags tab with hierarchical tag tree visible, source column showing tag origins.


  • 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
  • Don’t expect tag editing — UE’s GameplayTagsManager owns that
  • Don’t expect data table editing — use the Data Table editor

  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

Hierarchical view of every registered tag.

SectionWhat it does
Scan buttonEnumerates registered tags via UGameplayTagsManager
Tag treeDepth-indented hierarchy
Source columnWhere the tag is registered (.ini, plugin, etc.)
SearchFilter by tag name

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

SectionWhat it does
Scan PathFolder to scan
ScanWalks every UDataTable
Tables listPer-table row: name, row count, column count, fill rate, duplicate row flag
Per-table drill-inClick to see column-by-column fill stats

Screenshot 02 — Data Table tab — Tables list with fill-rate column visible, one row flagged for duplicates.


  1. Switch to Tags tab
  2. Click Scan
  3. Walk the hierarchy, search for specific tags
  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

FieldDefault
Scan Path (Data Tables tab)/Game

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


  • In-panel tag tree + tables list
  • No edits — read-only

  • 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


Report an issue with this tool

Opens our feedback form in a new tab with the tool name pre-filled.