Unfortunately, there is no real way to solve this issue. What you are experiencing is so-called hull overflow, where the hull exceeds the maximum value that the game can handle and loops around to a negative. When this happens, the station is destroyed due to having negative hull. The only way to solve this is to increase the maximum values, which can be done either by reducing the number of decimal places that are tracked or editing the game to use 128-bit values. Neither can be done with mods.

And before you ask, there is no way to make this issue not happen. Hull overflow is simply a game-specific case of the broader concept of integer overflow. Integer overflow itself is a consequence of the way computers work, and can not be removed without completely overhauling them on a hardware level. That is not ideal.

There is a workaround, however. Check the policies for a hull-reducing policy. That might help.

Hmm I didnt consider overflow shenanigans. I wonder if the "Overflow Workaround Components" mod could fix this. Although I dont know if I can change the blueprint of starbases.

You probably can't change the blueprint, unfortunately.

i mean there could be a way to stop storing the hull in one variable, or to store it in a Double data type instead of integer, such as splitting the number into two parts in different variables

Originally posted by Marxist Leopard Gaming:

i mean there could be a way to stop storing the hull in one variable, or to store it in a Double data type instead of integer, such as splitting the number into two parts in different variables

The thing is, though, they already made the switch from 32-bit values to 64-bit values. Mods reached the new limits within days. Increasing the maximum value again would simply result in mods increasing the numbers again.

Originally posted by Nova Solarius:

Originally posted by Marxist Leopard Gaming:

i mean there could be a way to stop storing the hull in one variable, or to store it in a Double data type instead of integer, such as splitting the number into two parts in different variables

The thing is, though, they already made the switch from 32-bit values to 64-bit values. Mods reached the new limits within days. Increasing the maximum value again would simply result in mods increasing the numbers again.

sorry for the necro, but you are wrong. They did go 64 bit, but in good ol paradox fashion, they didnt up the values. they are still using 32bit values internally. Paradox was just lazy as always. The values didnt go up at all during their transition. 64 bit could actualy display multiple bilions without issue