When I make a map, I must start at the smallest size. I make the map and explore it. When I get to the edge I get my crafting table and enlarge the map. The data that was on it gets erased and I have a blank map.
Example: I had a map that was 3/4 scale. I was outside of the area covered by the map and I enlarged it to 4/4 - the largest map size. The map I was left holding then showed no explored area (should have been the closest 1/4 to me, but it showed no explored area except for the fuzzy area close to the edge I was standing at. So I have to go explore the entire map again?
This is bad behavior. Pretend I just taped the other 3 unexplored sections to make the largest map - that is what I should have been left with, a large map with 1/4 explored.
Linked issues
Comments 12
Based on MCPE-25099, this sounds like the return of MCPE-24653.
Based on MCPE-25099, this sounds like the return of MCPE-24653.
Based on MCPE-25099, this sounds like the return of MCPE-24653.
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-16948.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-16948.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
As far as I am concerned it has never been corrected on iOS. Yes it may be a duplicate of the original MCPE-16948 or 24653 or 25099 but unless one is marked as reopened rather than resolved nothing will be done and the fault will still exist.
As far as I am concerned it has never been corrected on iOS. Yes it may be a duplicate of the original MCPE-16948 or 24653 or 25099 but unless one is marked as reopened rather than resolved nothing will be done and the fault will still exist.
As far as I am concerned it has never been corrected on iOS. Yes it may be a duplicate of the original MCPE-16948 or 24653 or 25099 but unless one is marked as reopened rather than resolved nothing will be done and the fault will still exist.
As far as I am concerned it has never been corrected on iOS. Yes it may be a duplicate of the original MCPE-16948 or 24653 or 25099 but unless one is marked as reopened rather than resolved nothing will be done and the fault will still exist.
Based on MCPE-25099, this sounds like the return of MCPE-24653.