Troubleshooting
Find the failed boundary before changing data or regenerating keys.
On this page
Nodes do not appear
Confirm the plugin is enabled in this project, its modules compiled, and the editor restarted. Use the current Win64 target. Drag from the correctly typed number or component pin to find its methods; similarly named Normal and Safe operations are not interchangeable.
Negative or fractional values fail
Check Idle Mode. It only rejects negative values; positive fractions are valid. Change the policy before use and restart. Do not interpret a rejection as an automatic clamp.
A Safe read or mutation fails
Check the success/error outputs, that you retained the original variable, and that its context matches. For components, verify their game initialization occurred. An invalidated handle or wrong context must not be replaced with a fresh starting balance to hide the failure.
The client still shows zero
Enable Replicates on the owning Actor, verify relevance to the client, and perform changes on the server. Observe On Value Changed after replication arrives. Test in distinct processes. Safe components do not automatically replicate.
A saved balance cannot be recovered
Confirm which layer failed. Unreal SaveGame only reports local serialization/load success; it does not authenticate the file. For Safe, check that your provider verifies/deprotects the record before calling Restore, that the intended memory GUID/name is used, and that every provider and Restore result is checked before applying the value. Keep rejected data from changing the authoritative balance.
Formatting or AI discovery fails
For formatting, validate the asset, resolve names and add it to configured Formatter Assets before reloading/restarting. For AI, check Toolset Registry, startup logs and the configured client bridge. An engine Registry startup error is not resolved by installing a second studio plugin.
If the problem remains, send a minimal reproduction through support.