mojira.dev
MCPE-35315

Map Offset in Worlds Imported from Console Edition

Worlds imported from Xbox One Console Edition should have the 'CenterMapsToOrigin' tag set to 1.

Maps created in Console Edition are imported as level 3 maps centered on the origin (0,0), matching the area the originally covered. However, with 'CenterMapsToOrigin' set to 0, any new (level 3) maps created in the imported world are offset by 512 blocks (one half map) from any existing maps. This creates a forced overlap and makes it impossible to complete any existing map walls with contiguous maps.

More to the point, this is unnecessarily confusing for casual players, especially since the overall behavior of maps in the most recent update isn't inconsistent in principle with how Console Edition does it. It could (and should) be as simple as learning that you now have to scale maps up to level 3 to match your old ones. Yet, not only is there seemingly no official explanation of this behavior (outside this tracker, i.e. MCPE-27025), but it seems the only solution to be offered anywhere is "start all over".

Comments 3

Having imported a survival world and put significant additional time into it before finally exploring further and discovering this undocumented "feature", I cannot easily revert. Nor am I particularly interested in recreating all of my maps from scratch. Given the votes on the previous issue, I'm certain I'm not alone. Given that existing maps are already preserved with their original (technically arbitrary) coordinates, there shouldn't be any reason to force this offset, especially since a flag for the desired behavior ('CenterMapsToOrigin') already exists and works in the current release version.

Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

This is absolutely still an issue, and an incredibly easy fix, as it only requires a bit-flip during the import process.

Bryan Wendlberger

(Unassigned)

Unconfirmed

Xbox

alignment

1.4.2.0

Retrieved