Use native DataTables with Scientific Number fields

Create a project-owned row

Create a Blueprint struct or C++ USTRUCT for your game’s row. Add one or more FScientificNumber fields alongside other game fields. A struct such as ST_EconomyRow can contain Price and Reward (Scientific Number), Category (Gameplay Tag), and Label (String), including inside nested structs and containers.

Create a DataTable using that struct and enter a sample row in Unreal’s editor. Export it as CSV or JSON from the native DataTable editor. Use Unreal’s output as the template for the row-name header and Gameplay Tag serialization when editing and reimporting the file. Enter a value in the field’s single text editor with notation such as 1e3. CSV/JSON serialization uses a Base/Exponent value, for example (Base=1.25,Exponent=400). Resolve any import errors and reimport the corrected source. Validate Assets checks the content currently stored in the asset; it does not replace reviewing import errors.

In Blueprint, connect the event execution pin to Unreal’s Get Data Table Row. Its Row Found and Row Not Found pins are execution outputs, not a bool for Branch. Connect Out Row to Break ST_EconomyRow and handle each execution output directly. Pass a normal numeric field to an existing operation such as a Safe component’s Try Set Value, then check that operation’s result. SNT does not add DataTable lookup, category, update, or CSV helpers.

Validate numeric fields

Select the DataTable in the Content Browser and choose Asset Actions → Validate Assets. The SNT editor validator checks reflected FScientificNumber fields in any row struct, recursively through nested structs, arrays, sets, and map keys and values. It reports the asset, row, full property path, and typed numeric failure reason. Typed failures such as Overflow invalidate the field; malformed representations receive a distinct diagnostic. The validator does not rewrite values or enforce gameplay rules such as positive prices. Packed and Safe fields are outside its scope.