Closed fire-bot closed 3 years ago
These crash reports are not from the unstable version, but the current public version. This issue should be fixed in Unstable (commit in our private repo: https://github.com/Regalis11/Barotrauma-development/commit/bc1098535941848cb13a619d7bf1a95256857b52).
Unstable docking port null errors, invisible force field between ports were tested and found to still occur. However, docking crash from repeated docking/undocking in pvp multiplayer was tested in unstable and found not to crash.
No change with 0.12.0.2
There's another ticket about the "docking port null" error (https://github.com/Regalis11/Barotrauma/issues/5026), closing this one.
Sent by WordPress (issue@barotraumagame.com). Created by fire.
From: Leo
Description Docking ports appear to become out of sync and sometimes create hulls that are unpassable even in latest unstable especially in pvp on the mirrored sub. Reasons appear to be due to continuous docking either due to continuous state wiring or continually toggling docking by griefers. I believe this error was reported already for stable before but I think it was assumed fixed but still occurs. At worst, this can also lead to crashing with an index error. May be related to the bug that causes invisible ports on mirrored subs where the original port was like #4746
Steps To Reproduce Get a sub with wiring that sets docking continuously or find a griefer who toggles docking repeatedly until bug occurs or crash
Version 0.12.0.1
Operating System Windows
--
This issue was sent from a contact form on https://barotraumagame.com/bug
Attachments: