[Bug] ConfigVar replication serialization failed #203
Closed
n0minal
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 2 comments
|
I found the issue with the help of a discord user. It seems like whenever a convar is set to an empty string, it fails the serialization for all the other convars. In the case of qbox, the I believe empty string convars could either be just ignored or serialized as an empty/nil value, would be better than throwing that many errors on all convars just because of one malformed value. |
0 replies
|
I can confirm this is now fixed in Patch 4. Feel free to close this issue. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
I'm getting several
ConfigVar replication serialization failed for <state variable>for variables being set withsetr. Why is this happening? How do I fix the replication serialization for these convars?EDIT: found the issue, see my comment below.
Issue type
Server
Repro rate
Always
Server build version
build 95
OS
No response
CPU
No response
GPU
No response
RAM
No response
Storage type
None
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
None
OS version / distribution
No response
CPU
No response
RAM
No response
Using txAdmin?
None
Hosting provider
None
Machine type
None
/perf endpoint output
No response
DDoS protection
No response
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
Expected Behavior
No errors
Actual Behavior
Serialization errors showing up in the console
Evidence
No response
Additional Context
No response
All reactions