mozar

Issue has been fixed with network version 8-30 . Now able to host servers again.

Hello, A few days ago I upgraded my multiplayer servers to aec214c without any issues. Today I upgraded to ae3bc61 and now it is not possible to connect to the servers. They will not show up on the master server list and when I attempt to manually connect to them via IP address the game just reports "no data" . When I revert back to aec214c everything works again but since it's on an older network version users will not connect. --Mozar

You caught me. I'm sorry. I just encountered the error again, this time it had nothing to do with ride properties, as they were disabled when the error occurred this time. af48099d-d81a-423b-896c-278b581f2163(a874756).dmp af48099d-d81a-423b-896c-278b581f2163.sv6

what the heck, I think someone stole my identity. Whoever did that better stop!

I'm not sure who's doing that, but they are probability just trying to give more visibility to the issue. Here's some more dumps. 7c2b9bd7-e7f7-4f0d-b93f-aa434fe6b989(a874756).dmp 7c2b9bd7-e7f7-4f0d-b93f-aa434fe6b989.sv6 b2f2ac88-5a32-4551-9067-4418434f7788(a874756).dmp b2f2ac88-5a32-4551-9067-4418434f7788.sv6

I'm on 0.0.5.0 build a874756 and its still crashing with same error ID. disabling the ride properties permission stops the server from crashing.

This is still a huge issue. It happens when there is a closed ride that people switch to testing. The only work around as Mattiator said is to disable ride properties, which makes the game unusable.

~50 new development releases since this issue was first reported and it's still a massive gaming breaking issue. I cannot run a server for more than 15 minutes before it crashed due to this bug. The crash is somehow triggered by users in ride properties. I feel some online users know how to trigger the bug and use it to maliciously crash servers.