Currently, as far as i can tell from my own playtesting, the fleet burn during slow-moving is not capped correctly.
If to say, the max burn for slow-moving is at 4, it is possible that the velocity gets past 4, like 4.1, 4.2, or 4.5.
This, as far as my playtesting goes, can happen if theres a lot of acceleration within one single frame.
This may not sound like much of an issue, but CampaignFleet.getCurrBurnLevel() returns a rounded value of the fleets currently acceleration.
This means at 4.5, it returns 5. The issue with this is, that this will cause it to fail checks on terrain, like Hyperspace storms, where despite slow-moving, you still get hit.
With one exception this doesnt happen in vanilla, but it can very quickly happen in modded enviroments that increase the fleets acceleration stat.
If you combine this with the players FPS being low, i.e around 30, even just a 50% acceleration boost to the fleet can cause the player to get hit by hyperspace storms, as the high "amount" value multiplied with the acceleration starts returning higher numbers in just a single frame.
How to Reproduce
This can be reproduced in vanilla with the Emergency Burn ability, since it has an even more extreme 4x acceleration multiplier.
Simply Hold S, activate Emergency Burn, and try moving through Hyperspace Storms. They should now hit despite being slow moving.
This is essentialy not really an issue in vanilla, because you will never combine those two commands, but should help bugfixing this issue since it is quite am annoying issue for some mods.
Author
Topic: Fleet Velocity is not capped correctly, causing issues with Terrain. (Read 547 times)