[Bug] Setting non-replicated client statebags errors when sv_stateBagStrictMode is enabled

[MauroNr1]

Summary

When setting a statebag value that is not replicated (client-only / local), the client-side SetStateBagValue native throws an error and stops the script even though the value is not being sent to the server:

Script error in Native SetStateBagValue: "StateBags can't be modified from the client when the StateBag strict mode is enabled. Disable it using setr sv_stateBagStrictMode false."

Issue type

Client

Repro rate

Always

Server build version

b105

Steps to Reproduce

1. Enable strict mode: setr sv_stateBagStrictMode true
2. From the client, call SetStateBagValue on a statebag that is not replicated (LocalPlayer.state:set('testKey', 'testValue', false))
3. Observe the error, even though no server-side state is being modified

Expected Behavior

Strict mode is meant to prevent clients from modifying replicated statebags that the server owns/authorizes. Since non-replicated statebags never leave the client, they shouldn't be subject to this restriction SetStateBagValue should work without error.

Actual Behavior

The check appears to apply regardless of whether the statebag is replicated, blocking legitimate client-only state changes and forcing users to disable sv_stateBagStrictMode entirely (defeating its purpose) just to use local statebags.

Evidence

Script error in Native SetStateBagValue: "StateBags can't be modified from the client when the StateBag strict mode is enabled. Disable it " "using setr sv_stateBagStrictMode false."

Additional Context

No response

[dBozee]

Same here on b106 using the Lua runtime.

[wolfram-cfx]

Thanks, we are looking into this.

[stelianclaudiu92-commits]

Great comment. UP!

[Gogsi]

A fix for this bug has been implemented and is available in the August 4 patch. Please try again and let us know if the issue persists. Thanks for your help!