The Quiet Keystone: Setting Any Property by Text

Most of v1.2’s headline features — type authoring, DataTables, DataAssets — quietly depend on one unglamorous pair of tools: asset.get_property_text and asset.set_property_text.

Here’s the problem they solve. Setting a float on an asset is trivial. Setting a user-defined enum value, a struct, a GameplayTag, a soft object reference, or an array/map container is not — UE’s scripting surface has no clean path for arbitrary typed values, and eval_python alone can’t reliably construct them.

One reader, one writer, every type

The text-property tools round-trip a property through UE’s own text serialization — the same format the engine uses for copy/paste and DataTable export. So the agent can set practically anything by handing over a text value, then read it back to confirm.

Why you should care

It’s the difference between “the agent can author your data model” and “the agent can author the easy 60% of it.” Every typed field on a struct, every enum on a DataAsset, every tag container — all settable from a prompt.

Try it

Get Webified Bridge on Fab · Getting Started guide · Join the Discord