Unintended effects from making objerror non-fatal

[4LT]

I'm finding the fact that objerror is now non-fatal results in a negative development experience. I one instance I fell through the world, because an entity was assigned world when it wasn't supposed to, and changed the solidity type. This increased the time it took to debug the situation partly because the objerror message wasn't the last thing printed when opening console (there were several messages about items falling through the world that spammed the console).

I believe the intended effect of making objerror non-fatal is to create a better player experience, but I fear it's just going to create surprises. At the very least, I think objerror should stop execution of the current spawn/touch/think context, and developer 1 should default to fatal behavior.

[4LT]

@andrei-drexler pinging for awareness

I didn't make this an issue b/c it's opinionated in nature