Robert Kovach

All of your points are valid and reasonable, and I agree it is a matter of perspective. But let me outline a few counterpoints:

1. F3 should never be required to play Minecraft. F3 is for debugging purposes, and relying on the player coordinates is a form of "cheating".
2. even with F3 to count steps, it is still very difficult to create two 2k by 2k maps that snap together (i still somehow ended with a 32 block discrepency).
3. two maps that cover the same area but are not copies of each other doesn't seem like a problem to me. this will happen as each player creates and manages their own 1:1 maps.
4. When 1:1 maps snap together flawlessly, it is odd that two 2:2 maps will not snap together unless they are created with the proper centers. This inconsistency is working as intended, but is not easily understood.
5. Each map size would only conform to one grid. For every 2k by 2k region there is only 1 valid map, much like for every 128x128 blocks there is only 1 valid map.

Thanks for reading and your consideration.

adjacent 1:1 maps converging into the same zoomed out map is precisely what I see as the intended behavior, this is what would ensure zoomed out maps always align to each other

If I make a 1:1 map at center point 16,0, then move to 128, 64 and make another 1:1 map, I would expect that if both maps are zoomed out to 2k by 2k, that they would be identical maps that cover a range from 2048, 2048, to 0,0 with a center point of 1024, 1024.

Because zoomed out maps do not behave as 1:1 maps, it appears to be a bug.

While it may be working as intended, it is very inconvenient to count blocks so the zoomed map is created at the proper location. What if the correct location to create a new zoomed map is in the middle of the ocean?

Also consider how long it physically takes to map a 2k x 2k map. These maps should automatically align to neighbors just like 1:1 maps.

Maps at each zoom level should be created on their own grids, so they snap together automatically.

Thanks for reading.