No, I want to have a visible (stderr) warning as soon as negative obstacle
indexes appear *somewhere* in saved data, since in my opinion it indicates a
(gave?) bug somewhere in the code.
Instead of just ignoring the root of the bug and discarding the invalid
obstacles, we should fix the bug itself so that negative obstacle indexes can no
It will at least hopefully give some idea where to search for the bug.