Sorry to bother you again, but I’ve encountered a severe problem while using RBXSerialize. I encoded some materials 10 days ago and tried to encode the same materials today, but the results were different, and now I cannot decode it anymore. Is it possible for this to happen? I am currently trying to save my datastore.
Going to release an update soon, that fixes enums.
1 Like
Thanks for your help! I’m looking forward to the update!
Does this work on the client? I’m trying to send serversided serialized model Data from a Datastore to be locally deserialized and spawned in on each client. Do I need to :BuildAPI() on both client and server? in a specific order? or just on the server?
Also I’m getting a warning saying…
“RBXLSerialize][Binary]: Could not describe ValueType Massless - Server - Binary:31”
…is this an effect of using the module clientsided or is it just because there is no Massless property listed in the property tables at all? Does having this warning affect the encoding and decoding?
You should do it on the server since it will replicate to the client.
I made a temporary workaround fixing a bunch of issues with your library. Including enums not saving/loading properly. But its only a temporary workaround since it relies on a pre-computed enum lookup cache.
I hope you can make a real fix soon, I would definitely appreciate that.
(edit: decided to scrap the enums completely and use integers of the enums value instead. Since Roblox supports setting enum properties as strings and ints too .-.)
This entire library is outdated and simply existed to fill a hole in serializes on ROBLOX. I’ve been dmed a lot recently about it and want to release an update shortly.