Huh? That’d be weird as 0 and 0.0 are both the same in binary, so you likely contrived your example…?!
There once was an attempt at actually having float arguments be converted to float, but this led to compatibility issues as not all native declarations in the community native DB import correctly said/say whether they’re int/float, and also scripts intentionally pass incorrect parameters (e.g. all animation scripts using a particular snippet pass an int in a float field and actually depend on it getting misinterpreted, as passing 1.0 would equal not playing any animation), the same would go for adding ‘errors/warnings’ since that’d just make all these scripts error out and confuse people as to why their working script is suddenly ‘spamming the console’.
(also, ‘warnings’ would be more ‘performance heavy’ than ‘internal casting’, lol)
This would be doable if tying it to a new fx_version, of course, but then the usual considerations go along with that.
Finally, why is this even in the FxDK section? It seems to be a general ScRT question/request/something.