Movement bug visualisation

[Searry]

I made this thing quickly to show how to avoid the movement bug.

[epaminondas]

Thanks for your work, Searry, but I'm afraid I can't access the "Image" you've included.

[Searry]

Thanks for your work, Searry, but I'm afraid I can't access the "Image" you've included.

Really? It shows up perfectly fine for me.

[Nikel]

Cannot see it either.

[Searry]

Cannot see it either.

How about now?

[Nikel]

I can now

[epaminondas]

Yep, me too. Thanks again - sums things up nicely. Trouble is you don't know that it's going to happen until it's happened and you then have to wind back the turn, try to identify where the cross-over has occurred, then unpick the movements involved in the hope that they don't create new cross-overs elsewhere. That's atomically annoying.

No doubt there are real-life analogues to this kind of snafu, but in those cases you would at least have the satisfaction of shooting the staff officer responsible!