The bug
As can be seen in the screenshots, the map says "unknown map" in the chest's inventory and has actual information, when in the player's inventory.
[media][media]
How to reproduce
Get a map and right click it to make it a filled map
Put it into a chest
→ ✔ Map still has its information in the tooltipLeave and rejoin the world
→ ❌ The map's tooltip says "unknown map"Move the map into your own inventory
→ ✔ The information becomes visible again
Linked issues
is duplicated by 4
MC-136142
Maps stored in a shulker box in the player inventory randomly become "unknown map"
Resolved
MC-138322
Treasure and explorer maps show "Unknown Map" after placing them in container and reloading world
Resolved
MC-241007
Maps lose ID-data when placed in a chest/container
Resolved
MC-262306
Maps in chests turn into 'Unknown map' every time you restart the game
Resolved
relates to 1
Attachments
Comments 113
@Anthony Cicinelli
Thou U may not know Chinese, I think U can apparently find that the txts of the Filled Maps in the 1st & the 2nd screenshot R different 😛. The shorter 1 only says "Unknown Map" (未知地图), while the longer 1 gives U the particular info.
Does this still happen in 1.16.1?
Yes, could reproduce.
@Anthony Cicinelli
IDK, but I was sure that it happens in 20w30a.
It seems NeunEinser has confirmed it and cleared it up a bit.
Affects 1.16.3
The equivalent bug on Bedrock is MCPE-37740
Can confirm in 20w51a.
Still not fixed in 21w44a
Confirmed for 1.18 pre-release 1
Confirmed for 1.18 pre-release 2
Confirmed for 1.18 pre-release 3 and 4
Confirmed 1.18 pre-release 5
Confirmed 1.18 pre-release 6
Confirmed 1.18 pre-release 7
Confirmed 1.18 Pre-release 8
Confirmed 1.18 Release Candidate 1
Confirmed 1.18 Release Candidate 3
Confirmed 1.18 Release Candidate 4
Confirmed 1.18.1 Pre-Release 1
Confirmed for Minecraft 1.18.1 Release Candidate 1
Confirmed for Minecraft 1.18.1 Release Candidate 2
Confirmed for snapshot 22w03a.
Confirmed for snapshot 22w05a.
Confirmed for snapshot 22w06a.
Confirmed for snapshot 22w07a.
Confirmed for 1.18.2 pre-release 1.
Confirmed for 1.18.2 pre-release 2.
Confirmed for 1.18.2 pre-release 3.
Confirmed for 1.18.2 release candidate 1.
Still not fixed... Confirmed for 1.18.2
Confirmed for snapshot 22w11a.
Confirmed for snapshot 22w12a.
Confirmed for snapshot 22w13a.
Confirmed for snapshot 22w14a.
Still not solved in snapshot 22w15a.
Confirmed for 22w16b.
Confirmed for snapshot 22w17a.
Still not solved in snapshot 22w18a.
Confirmed for snapshot 22w19a.
Confirmed for 1.19 pre-release 1.
Confirmed for 1.19 pre-release 2.
Confirmed for 1.19 pre-release 3.
Confirmed for 1.19 pre-release 4.
Confirmed for 1.19 pre-release 5.
Confirmed 1.19 Release Candidate 1
Confirmed 1.19 Release Candidate 2.
Confirmed for 1.19.
Confirmed for snapshot 22w24a.
Confirmed for 1.19.1 Pre-release 1.
1.19.1 Pre-release 2.
1.19.1 Pre-release 3.
1.19.1 Pre-release 4.
1.19.1 Pre-release 5.
Confirmed for 1.19.1 Release Candidate 3.
Confirmed for 1.19.1.
Still not fixed in 1.19.2
Confirmed for snapshot 22w42a.
Still not solved in 22w43a.
Another week, no fix. Still confirmed in snapshot 22w44a
Confirmed for snapshot 22w45a
Confirmed for snapshot 22w46a
Confirmed for pre-release-1 1.19.3
Confirmed for 1.19.3 pre-release 2
Confirmed 1.19.3 pe-release 3
Confirmed 1.19.3 release candidate 1
Confirmed for 1.19.3 release candidate 2
Confirmed for 1.19.3 release candidate 3
Confirmed for 1.19.3
Confirmed for snapshot 23w03a
Still present in snapshot 23w04a
Still not adressed in 23w05a.
Confirmed for snapshot 23w06a.
Confirmed for 23w07a.
Confirmed for 1.19.4 pre-release 1
Confirmed for 1.19.4 pre-release 3
Confirmed for 1.19.4 pre-release 4
Confirmed for 1.19.4 Release Candidate 2
Still not fixed in 1.19.4 full release
Observing this issue for quite a few versions. Can confirm this is still present in 1.19.4.
Indeed, nothing has changed in 1.19.4, and it's a very noticeable bug as well.
Confirmed snapshot 23w13a
Still present in snapshot 23w14a
Confirmed 23w16a
Still not fixed in 23w17a
Still present in 23w18a
Still not solved, 1.20 pre-release 1
Confirmed in 1.20 pre-release 2.
Still present in 1.20 pre-release 4.
Still not adressed in 1.20 pre-release 5
Still present.... 1.20 pre-release 6
Confirmed for 1.20 release candidate 1
Still present in 1.20 full release
Still present in 1.20.1, not edit to list yet?
Confirmed for snapshot 23w32a.
Still not adressed in snapshot 23w33a
Confirmed for snapshot 23w35a
Stil not adressed in 1.20.2 Pre-release 1
Villager related issue... The perfect moment to adress it with the revamp of trading...
Still present in 1.20.2 Release Candidate 1
Not addressed in 1.20.2
Confirmed snapshot 23w40a
Confirmed snapshot 23w42a
Still not addressed in 23w43a
Present in 23w45a
Still not addressed in 23w46a
still present 1.20.3 pre-release 2
1.20.3 release candidate 1
Still not addressed in 1.20.4
Still present in 23w51b
Present in snapshot 24w03b
Still not addressed in 24w05b
Note: You have to use Advanced tooltips (F3+H).
That's not the issue.
What exactly is the bug here? Can you explain?