I really don't mean to be rude, but it seems like a really bad idea to silently roll out changes like this, particularly at the end of a patch cycle. All sorts of things broken because of it, making me run around troubleshooting instead of playing the game or making new mods and content for the community. Very much agree, and if it is a security feature why does it not have a toggle like other anti-cheat options? I have zero interest in this feature and now my 100+ players are suffering with a broken map mod, a broken vehicle claim player list, broken walkie talkie communication without visiting a player in person (I know Spiffo insists that you made no changes to this, but without any changes on my end it broke with 41.78.12 and remains broken, reproduced with no mods and a fresh save), and more all since 41.78.12. It also has other prominent modders sharing concerns having also seen the issue. The Discord thread has links to places where others encountered this issue and/or resolved it by deleting the map_sand.bin file as I describe being the issue above. Was told it wouldn't necessarily get attention there on 3/8 but between being sick and being busy I have not had a chance to post it here until now. I first posted this on Discord in late January here: It will show these in the sandbox options screen as if those settings were never changed, though if you go to look at the file on the server the values are in fact the newer values (unless that admin hits save). If this happens to an admin account and that user goes to edit the sandbox options, it will overwrite existing options with those from map_sand.bin upon saving. Changed a value? Too bad, it's the old value still for this client. Turned a feature on? Too bad, it's off on this client. Old settings are persistently used on a client even when the server's sandbox options have changed from these settings. When this is the case, there are the following implications which I have personally experienced: It seems that the client won't get new settings unless they delete map_sand.bin from their save folder when this happens, whatever conditions it happens under. This means old settings can be retained, and it likely means that you could hex edit the file to change settings and cheat. It would seem that map_sand.bin, which stores the sandbox settings, is used if present on a save, yet not necessarily updated in MP when the user joins the server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |