Network connection shutting down due to read error

[ihatethisengine]

Testmerges

#4475: 'Adds drawing to tacmaps' by Cthulhu80 at commit b2c1041 #4812: 'Dropship weapons console TGUI' by mullenpaul at commit 32c3121 #4793: 'ports the tg profiler subsystem' by harryob at commit 4b06b80 #4866: 'Radio TGUI backend Tidy-up & Adds Listening Devices' by realforest2001 at commit f9749b2 #4879: 'Hotfix for missing Traitbound Elements Handlers' by fira at commit cecf097 #4889: 'Echo pad droppod fix' by fira at commit 6c3efed

Round ID

19491, 19503

Description of the bug

First time I got stunned by an incend OB (pic related, I didn't get killed as I was under core protection), which lead to my connection crashed. Second occurrence happened to another player on LV (19503, warrior NTF), who also got stunned, but this time by mortar. They didn't see the same error, but this is likely due to them using tgui chat that doesn't show errors. I don't think this happened until recently, but it happened to me only once so far.

What's the difference with what should have happened?

Should not crash.

How do we reproduce this bug?

No idea. In both cases there was an explosion and stun. But in case of incendary OB, the stun is not caused by the explosion, but iirc hard-coded.

Issue Bingo

• Issue could be reproduced at least once
• Issue happened in a recent (less than 7 days ago) round
• Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)

[ghost]

Can confirm the ob stun is hardcoded.