Open iampremo opened 1 year ago
personally i think this should throw an exception error the same as trying to work outside the bounds of an array does
yeah having a hard crash with a stack trace would be so much more useful than just saying "grid index out of bounds" and having to track down what grid operation silently failed by hand
Ticket #202664
Feature Type: feat_change_ingame Description: The console message for trying to write data to a grid out-of-bounds isn't displaying enough information to be a useful debugging tool, especially in larger projects. Seeing a message like "Grid 23, index out of bounds writing [124,168] - size is [50,72]" pop up in my output doesn't really help me narrow down where it is coming from. Benefit: Especially in large projects, adding more info to these messages would make debugging grid code less tedious. Link: