Modder warning - potential range check errors

[jimbob55]

The mine laying problem could have been due to your DN minelayer trying to launch 79456 mines in one turn....This is a little outside the unsigned int limit of 65,536.
A minelaying component that lays 'only' 100 mines per turn would fix the problem.

Best to limit any values you edit to the restrictions of common data type.
unsigned (unsigned int) 0 to 65535
long int ± 2 billions
unsigned long int 0 to 4 billion
float 3.4 ±e38
double 1.7 ±e308

Unfortunately, I have no idea which type is used for which values in the game....

[Barnacle Bill]

quote:

---

Originally posted by jimbob55:
The mine laying problem could have been due to your DN minelayer trying to launch 79456 mines in one turn....This is a little outside the unsigned int limit of 65,536.
A minelaying component that lays 'only' 100 mines per turn would fix the problem.

Best to limit any values you edit to the restrictions of common data type.
unsigned (unsigned int) 0 to 65535
long int ± 2 billions
unsigned long int 0 to 4 billion
float 3.4 ±e38
double 1.7 ±e308

Unfortunately, I have no idea which type is used for which values in the game....

---

I'm pretty sure that is the problem. Not that it tried to launch that many, as it only had 5 on board. I think when it tried to launch, though, the game checked its total capacity and found it too high. Again, when I lower the value to 459 per turn, the problem went away.