Hello!
I tripped myself up with a silly error today, which thankfully didn’t take too long to resolve, but I can see how it could potentially cause issues for others later down the line.
Consider the following image:
The math function ‘Random Int in Range’ has been supplied an invalid range, and has returned ‘1’. Since this is in visual script, I would expect it to throw a warning that the function has been supplied an invalid range.
Since blueprints are script and has less performance requirements, and that it is both easier to trip oneself up with small errors and considerably harder to debug than it is in C++, My request would be that all similar math functions rather than being directly mapped to their C++ equivalents, should have an additional layer of wrapping to throw relevant warnings with functions are misused. This could really help debug issues in more complex use cases where it may not be immediately obvious that invalid ranges are being supplied.
Thanks!