Negative values in numeric variables in Script Config

With the recent changes, it seems that negative values can now be used in numeric variables in script configuration (I don't recall being able to input negative values before), potentially impacting numerous scripts that relied on the previous behavior. Is there a current an official way to handle this? That is, to specify that only positive integer values are acceptable, or is it now necessary to perform this control internally after obtaining the value of the conflicting variables?

I think you’d need to range check the configured value.

Probably not a change for most scripts, as zero or really large (or small) numbers were probably an issue as well? Maybe this just makes the need for a range check more obvious.