In my VPAC maps, I have not been a fan of how squishy bombers are (thanks to how much game balance I have messed with) and have devised a way to increase the Bomber unit's HP. It works great... until you kill their bomber pad which then causes CW4 to crash.
And unlike my past uses of "crash", this is an actual crash. I get a crash window to force close CW4.
My assumption is that when a bomberpad is destroyed, the way it handles with destroying bomber units can not deal with their massively increased health and something goes wrong with destroying it, causing a full crash.
When the code runs and you go and destroy the bomberpads (I did so using just Creeper for consistency), upon bomberpad destruction the game will crash. Simple as that!
I will not be surprised if this applies to all "sub-units" like the TerpDrone, RefineryDrone, etc.
Very annoying circumstances have made this appear as an issue. It was nothing more than very consistent coincidence.
The real cause however seems stranger.
In my VPAC maps, I have not been a fan of how squishy bombers are (thanks to how much game balance I have messed with) and have devised a way to increase the Bomber unit's HP. It works great... until you kill their bomber pad which then causes CW4 to crash. And unlike my past uses of "crash", this is an actual crash. I get a crash window to force close CW4. My assumption is that when a bomberpad is destroyed, the way it handles with destroying bomber units can not deal with their massively increased health and something goes wrong with destroying it, causing a full crash.
Player.log Player-prev.log
Code that does all of this:
When the code runs and you go and destroy the bomberpads (I did so using just Creeper for consistency), upon bomberpad destruction the game will crash. Simple as that! I will not be surprised if this applies to all "sub-units" like the TerpDrone, RefineryDrone, etc.