unreal-data-assets-tables

Design, load, cook, and validate data-driven content in Unreal Engine 5.8.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill unreal-data-assets-tables-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unreal-data-assets-tables
Source: https://github.com/steveulrich/ProjectB/tree/main/.cursor/skills/unreal-data-assets-tables
Command: npx skills add https://github.com/steveulrich/ProjectB --skill unreal-data-assets-tables-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Unreal Engine projects often misuse Data Assets, Data Tables, and Data Registries, causing broken packaged builds, unstable identifiers, accidental hard-reference memory spikes, and mutable state stored in shared definition assets. This Skill provides a decision framework and operational rules for choosing the right data representation and shipping it correctly. ## Core Features & Use Cases - Representation selection: Decision tables for choosing between UDataAsset, UPrimaryDataAsset, Data-Only Blueprints, Data Tables, Curve Tables, Composite Data Tables, and Data Registries. - Loading and cook correctness: Guidance on hard versus soft references, asynchronous loading, Asset Manager scan rules, asset bundles, Primary Asset Labels, chunking, and packaged-build verification. - Validation and debugging: IsDataValid and UEditorValidatorBase patterns, Data Validation commandlet usage, and a symptom-to-cause failure routing table. - Use Case: When building an item catalog, use this Skill to define UPrimaryDataAsset definitions with UI and Gameplay bundles, keep runtime inventory state separate, and prove cook inclusion in a packaged build. ## Quick Start Use the unreal-data-assets-tables skill to design a validated data and asset-loading workflow for this Unreal project.

Frequently Asked Questions about unreal-data-assets-tables

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Data Asset and Data Table in Unreal Engine?▼

Use a UDataAsset for one inspectable authored definition with heterogeneous fields, and a UDataTable for many homogeneous rows sharing one FTableRowBase schema. Choose UPrimaryDataAsset when the definition needs a stable FPrimaryAssetId, Asset Manager discovery, bundles, or cook rules.

When should I use soft references versus hard references in Unreal?▼

Use hard references only for assets that must load with their owner and are acceptably small. Use TSoftObjectPtr or TSoftClassPtr when content is optional or a large catalog must stay unloaded, but define load failure behavior and cook inclusion explicitly.

Why does my asset work in PIE but fail in a packaged build?▼

Editor discovery and PIE loading do not prove an indirectly referenced asset was cooked. Identify the Primary Asset, label, directory, or cook rule that includes it, then inspect Asset Audit and test the cold-load path in a packaged build.

Can I cache a Data Table row pointer in Unreal Engine?▼

No, never cache a Data Table row pointer beyond local use when the table may reimport, because reimport can refresh the table and invalidate pointers. Resolve rows by handle when needed or copy the row only when a snapshot is intentional.

When should I use a Data Registry instead of a Data Table?▼

Use a Data Registry when data comes from multiple read-only sources, needs ordered fallback or overrides, asynchronous acquisition, or managed caching. Prefer one simple Data Table until a demonstrated loading or production requirement justifies the registry's plugin and indirection.

Can I store player inventory state in a Data Asset?▼

No, Data Assets, Data Tables, and Data Registries are read-only definitions at runtime. Store quantity, durability, ownership, and progress in a runtime state struct keyed by the stable definition ID, and persist it through SaveGame.