Tests should not trigger OOB chunk access

Question

Tests should not trigger OOB chunk access

Closed this issue 11 years ago · 1 comments

When the server is run (without previous world, haven't tested with), or when running the tests it will continuously _spam_ "Coordinates %s are OOB in %s() of %s, ignoring call"-like messages.

This is because the coordinates fail to the validation going on in chunk.py:34
This is something I think is rather alarming, and should be fixed.

Answer 1 · 2013-04-14T23:32:48.000Z

It is definitely alarming, and if I had any gumption to hack on Bravo, I'd go and fix some of them. Patches welcome. Note that this bug cannot ever be closed as worded, but that's okay; somebody will close it when messages get down to an acceptable level.

Edit: Updated title to have a measurable goal.