Automap does not work correctly for staggered maps #3089

(This is a known problem, but there did not appear to be an issue open for it. Now there is.)

Automapping only works correctly for orthographic and non-staggered isometric maps. Automapping should take staggering into account and work for all supported orientations.

Supporting multiple orientations would open up some UX issues:

• What should happen if automap rules with a different projection from the map are applied? Should rule files with incompatible projections be ignored? Should rule files be interpreted as being of whatever orientation the target map has?
• What about the same projection (e.g. iso) but different orientations, e.g. staggered vs non-staggered, or hex with different stagger indices or axes? Should these be ignored? Should the algorithm attempt a conversion to produce visually consistent results? Can that even be done reliably?
• How and when should the user be warned if some of their rules are ignored or reinterpreted due to incompatibility?

For all of these, I suppose the answers should be consistent with whatever is done when attempting to paste across maps with different orientations.

Tiled has some issues with different stagger values (e.g. #2874), those should probably be tackled first to avoid those bugs propagating into Automap.