Read-Only Assets

In some cases, you may want to only allow a component to use a read-only version of a Soap asset. This implies that you can still register to its reactive events and read its value, while explicitly ensuring that no one can write to the value. In these situations, you can use the Read-Only version of a variable.

When should I use Read-Only Assets?

When the asset:

• Is owned and modified by a single system

• Needs to be observed by many consumers (UI, bindings, gameplay logic)

• Should never be accidentally modified from the Inspector or from code

Typical use cases include UI bindings, state display, game metrics, abilities, etc...