rearrangement of loops, where the outer loop iterates through the
slidePossibilities array, and the secondary loop iterates through the array of
BlockOrientation. As a result the order specified in slidePossibilities, which
currently has Move.POST_DROP_NO_ACTION at the top, takes precedence over block
orientations and block center of rotations. In particular it will cause the
slide moves earlier in the list to take precedence. I need to study this code
a bit more, in order to verify that these statements are accurate. In
addition, some fairly massive optimizations can now be made, which I'm about to
do.
