Moving overlapping regions is weird

[DCNick3]

I didn't test it too much, but it seems that moving overlapping regions doesn't do what I would expect.

Doing it correctly requires a very particular order of operations (same as in memcpy vs memmove).

It would be nice if it worked correctly, or, at least, refused to do this operation, as it can lead to very unexpected results

(There was a floor there)

[RecursivePineapple]

Yeah, moving needs a lot of fixes. It's a bit better in dev but I still need to fix the core algorithm.