maps overlapping

Was the map that doesn't fit the grid one you created by zooming an old map? I had this happen to me once when zooming an old map to level 4. The zoomed map was centered at 0,0, which was more than 2500 blocks away from the map I zoomed it from. Every time I tried to zoom that map to level 4 I got the same problem. I had to recreate the original map to fix the problem. If, like me, your flawed zoomed map seems centered near the world spawn or 0,0, I recommend you try recreating the unzoomed map from scratch, then see if that one zooms correctly.

Moderators: I believe there is or was a bug in a map upgrade path. The map I was zooming was centered somewhere around (-2300,-1200) and would have been created sometime between June 1 and August 31 last year. I tried to zoom it to level 4 on January 8 this year, using 1.2.8. I'm convinced an upgrade path error damaged the map, but I didn't report it because I couldn't narrow down the timeframe of the upgrade that damaged it and I had an easy way to fix it.

Hi.
it was a freshly new made map, just few days ago. I tried it 3 times with same result, it just doesn't fit to the grid to align with previously made maps. However, I can't really recall when those previous maps were made.

In my case, the problem was with the unzoomed map, and I fixed it by replacing the unzoomed map with a new map and re-exploring the area. After that, zooming it to the next level created a map that fit into the grid correctly. I believe this will work for you, too.

I made maps all the time by walking off the edge of a previous map, making a new one and immediately zooming them out.  Now the maps are overlapping which is annoying to no end.  Do we have to carefully calculate out the grids now?

Nobody from Mojang trying to find and fix this bug? It is very sad. Playing Minecraft does not make any fun without using maps!

We can't find the bug until we're able to reproduce it, and that's the problem. Usually, either the reporter of a bug has some notion of what conditions are necessary to make the bug happen, or we can experiment to figure out what some of the conditions are. But that isn't working in this case because the bug remains invisible until you zoom a map that's broken in a certain way, and it appears that the way the map becomes broken is also invisible and occurs still earlier, during an upgrade to a new release—but nobody knows from/to what release, and nobody can provide a copy of an old pre-upgrade world with a known _un_broken map that we can upgrade it break it and then zoom to reproduce the bug under controlled conditions. So you can see how difficult it is to get a handle on this one. Until we have that, trying to find this bug is like looking for a needle in a haystack.

Thank you for your report!
However, this issue is a Duplicate of MCPE-27025.

If you have additional information, please add it to that report.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

@unknown: I have hidden your last comment from public view because your Google Drive account reveals a personal email address.
Thanks for providing the sample worlds and for helping keep this issue alive. You helped me think of a way I could get around an obstacle, so I now have a world file in which we can reproduce the problem under controlled conditions. With that, we were able to forward the issue to the developers.

I used my own world instead of yours, because I now have a complete history of mine. The developers may still appreciate having your worlds to test with, so leave them on Google Drive for a while if you can. They might need your sample worlds to check whether all these "duplicate" issues are actually being caused by the same bug.

Thank you for your commitment. I leave the data on the google drive as long as you need it.