ChronoSphere superweapon with SW.Next crashed in multiplayer

[Coronia]

Description

• set SW.Next for a ChronoSphere superweapon
• start a multiplayer and use this superweapon, then click again to fire corresponding ChronoWarp superweapon
• THE OTHER PLAYER's game will have a chance to crash, while the user of superweapon is fine
• it's much easier to reproduce the crash when trying to click frequently with these ChronoSphere/Warp superweapons cursors, which is also likely to release more than one shot of SW.Next
• ChronoWarp with SW.Next will NOT crash by itself, but seemed to increase the chance of the said crash in testing

Used dev nightly to test. Logs and corresponding dll/idb are in the attachement

ChronoSphere+SW.NextFE.zip

Phobos Version

develop nightly (see attachment)

Conditions to reproduce

No response

INI code

[ChronoSphereSpecial]
SW.Next=NukeSpecial
SW.Next.RealLaunch=no

Steps to reproduce

...

Expected behaviour

either fix the crash or prohibit ChronoSphere superweapon from SW.Next, or at least document that

Actual behaviour

the user of the superweapon is fine, while the other player crashed

Additional context

No response

Checklist

• [x] The issue happens on the latest official version of Phobos and wasn't fixed yet.
• [x] I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented.
• [x] I added a very descriptive title to this issue.
• [x] I used the GitHub search and read the issue list to find a similar issue and didn't find it.
• [x] I have attached as much information as possible (screenshots, gifs, videos, debug and exception logs, etc).