When I send a table to a client I’m getting “Failed to Read type” errors with bogus types like 2 (LightUserData), 33 (Video) and a couple of others I can’t remember off the top of my head. The tables are always consisting of strings and never once does the error type say it’s a string.
So far I’ve tested the following conditions, and they usually yield the net.ReadType error:
-If the keys of the table are SteamID’s
-If the written table contains a nested table with a SteamID entry.
-If the written table contains a nested table with non-english characters ( russian text is especially aggressive )
You would think that SteamID’s would be causing the error, but when I replace the SteamID with the Steam64 equivalent, I still get the net.ReadType errors.
My initial thought was that these tables are too big and are getting cut off along the way, but allocating the main table can still randomly produce the error ( I haven’t gotten to do more testing on the conditions within the allocations )
These tables can range anything between 1 and 1000 entries, and I’ve had these net errors appear even from a single entry with the above conditions.
I should also point out this happens on high server load ( tested with 63 players ) and a single lonely person.
The table can also be sent at any time and still produce the error. Most of the time these tables are sent when the client has already loaded.
Has anyone come across this issue and know how to get around it? Or is there some better way to prevent corruption? Or hell, just have any idea why it happens. This has been a huge stump for me