MC-122995BlockEntityTag data fix walker is incomplete and incorrect
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.
[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparator
Note: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use 
to indicate that an entry should be removed.
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
| Block id | Required action |
|---|---|
| lit_furnace | |
| standing_sign | |
| wall_sign | |
| piston_head | |
| daylight_detector_inverted | |
| unpowered_comparator | |
| powered_comparator | comparator |
| standing_banner | |
| wall_banner | |
| end_portal | |
| end_gateway | |
| shield |  Note |
New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
| Block id | Required action |
|---|---|
| lit_furnace | |
| standing_sign | |
| wall_sign | |
| piston_head | |
| daylight_detector_inverted | |
| unpowered_comparator | |
| powered_comparator | comparator |
| standing_banner | |
| wall_banner | |
| end_portal | |
| end_gateway | |
| shield | Note |
Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.
minecraft:banner is contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
Linked Issues
is duplicated by1
NormalCreated Issue:
Warning for light-blue-banner in log, although none existent
I noticed the error message:
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in the world I was in when that message occurred.I was in one of my bugtestworlds, and neither in my inventory, nor in any container, nor attached to anything as block were any light blue banners.
I do have a banner in another bugtestworld, but it is regular blue.
Currently I don't know why it occurs or how to reproduce it.
Attachments6
light-blue-banner_warn.PNG
I noticed the error message:
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in the world I was in when that message occurred.I was in one of my bugtestworlds, and neither in my inventory, nor in any container, nor attached to anything as block were any light blue banners.
I do have a banner in another bugtestworld, but it is regular blue.
Currently I don't know why it occurs or how to reproduce it.
I noticed the error message:
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in the world I was in when that message occurred.
Currently I don't know why it occurs or how to reproduce it.
Warning for light-blue-banner in log, although none existentSince 17w47a: "Unable to resolve BlockEntity for ItemStack" warning upon loading the world list
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in the world Iwas in when that message occurred.
I was inone of my bugtestworlds,
I do have a banner
but it is regular blue and I have not been with 49b inside of it when that warn message already occurred.
Currently I don't know why it occurs or how to reproduce it.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
In 17w46a it did not show up.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessearily with light blue banners, but with other blocks/items.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessearily with light blue banners, but with other blocks/items.
Since 17w47a: "Unable to resolve BlockEntity for ItemStack (ItemInstance)" warning upon loading the world list
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necess
earily with light blue banners, but with other blocks/items.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survical, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot.
Since 17w47a: "Unable to resolve BlockEntity for ItemStack (ItemInstance)" warning upon loading the world list (potential data loss?)
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survi
cal, it'd be great if someone could figureif this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13snapshot.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure* if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot*.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure* if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot*.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot before.
If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it woudl be an issue if mapmakers or Survivalplayers woulf lose some data when they load their worlds from release to release version.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot before.
If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it wou
dl be an issue if mapmakers or Survivalplayers woulflose some data when they load their worlds from release to release version.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot before.
If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it would be an issue if mapmakers or Survivalplayers would lose some data when they load their worlds from release to release version.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot before.
If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it would be an issue if mapmakers or Survivalplayers would lose some data when they load their worlds from release to release version.
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figure if this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshot before.
If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it would be an issue if mapmakers or Survivalplayers would lose some data when they load their worlds from release to release version.
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)
Since the Client thread is logging this, could this be caused by the class net.minecraft.client.renderer.tileentity.TileEntityItemStackRenderer (or its new variant) and therefore the BlockEntityTag is meant?
Since 17w47a: "Unable to resolve BlockEntity for ItemStack (ItemInstance)" warning upon loading the world list (potential data loss?)BlockEntityTag datafix walker is incomplete and incorrect
BlockEntityTag data fix walker is incomplete and incorrect
I noticed the error message:
Unable to resolve BlockEntity for ItemStack: minecraft:light_blue_banner
although I got no light blue banner in any of the worlds I recently opened.
In 17w46a it did not show up.I noticed that this warn message already occurs when I just clicked on "SinglePlayer", it doesn't have anything to do with me being in a world actively.
I currently assume there must be a problem with a light blue banner in the level.dat of one of my worldsaves, but it's not one of those I recently loaded.That means it will likely happen for other people as well, just not necessarily with light blue banners, but with other blocks/items.
I suspect this could mean potential data loss if people were to rejoin in their worldsaves with affected blocks/items.
E.g. if I'd have a light blue banner with NBT data (a pattern), it may be that this pattern would be lost upon loading that worldsave in the current snapshot.
Considering that this may be an issue for mapmakers as well as Survival, it'd be great if someone could figureif this occurs also if you would load a world from 1.12.2 release to the final 1.13 release, or if the potential data loss only would occur if you loaded your world in a 1.13 snapshotbefore.If it only affects worlds previously loaded in snapshots, it wouldn't be as problematic, as people know that snapshots are experimental/can corrupt worlds, but it would be an issue if mapmakers or Survivalplayers would lose some data when they load their worlds from release to release version.
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield h5. Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.minecraft:banner in contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield h5. Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.minecraft:banner in contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
@ Marcono: If it helps somehow, I could dedicate some time in trying to find the affected world in my saves which causes this warning; I currently got around 300 saves in that folder, and albeit a banner with texture cannot be in all of them (as some worlds are older than the addition of banners), it'd still take some time to go through at least around 100 or so
But, like I said, if it would help to narrow down the issue, I could still do that (and backup any world I'd enter).
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield h5. Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.minecraft:banner in contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.
minecraft:banner in contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.
minecraft:banner i
ncontained twiceThe map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
The bug
The data fix / upgrader walker for the BlockEntityTag of items (net.minecraft.util.datafix.walkers.BlockEntityTag) is incomplete and incorrect.
Warnings like the following mean that it could not walk the block entity data because it did not recognize the block entity based on the item id.[Client thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:comparatorNote: It is unclear why the client is logging this since the server should likely be doing the upgrade.
Problems
Block ids are used instead of item ids
Some entries use the block ids instead of item ids. The following lists use
Old block entity id map
Maps from item id to the old block entity id, for example RecordPlayer.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield New block entity id map
Maps from item id to the old block entity id, for example minecraft:jukebox.
List last updated for 17w50a
Block id Required action lit_furnace standing_sign wall_sign piston_head daylight_detector_inverted unpowered_comparator powered_comparator comparator standing_banner wall_banner end_portal end_gateway shield Note to shields
Shields should possibly not even be contained in these maps since they have no block entity. For current data versions they should probably map to minecraft:banner. In case their NBT structure changes at some point an data version check should be added.
minecraft:banner is contained twice
The map for the new block entity ids contains a minecraft:banner to minecraft:banner entry twice.
Missing player head item ids
The map for the new block entity ids does not contain the item ids for the new splitted heads / skulls ids:
List last updated for 17w50a
- skeleton_skull
- wither_skeleton_skull
- player_head
- zombie_head
- creeper_head
- dragon_head
Missing bed item ids
The map for the new block entity ids does not contain the item ids for the new splitted bed ids.
Outdated entries not data version filtered
The map for the new block entity ids does not filter based on the data version, this means it walks for outdated entries like for example the flower pot which does not have a block entity anymore.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Grum (Erik Broes)![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Good to know. This affects only items, not the respective blocks, right? I had some signs in my inventory that executed commands when right-clicked. It might have to do with that.
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Can confirm. For me it happens with an armor_stand and a comparator. Tested in 17w49a.
I don't know which one of my worlds causes it either.
The problem appears to be the data fix / upgrader walker for the BlockEntityTag for items. I am going to change the report accordingly.
@Meri Diana could you please include the class name column when taking screenshots of the launcher next time. It could come in really handy.
I added 1.12.2 as affected version since it is affected by the block id used instead of item id too.
@Marcono1234 I'll keep it in mind next time, thanks a lot for your help
In 1.13pre1 I still had the output of armor_stand and comparator, since 1.13pre2 it is gone.
I can only confirm it fixed for armor_stand and comparator, not for the other things on the list.
Marcono1234 In the cases that happened to me it appears to be fixed. You seem to have some further inside on this issue.
Can you by any chance confirm if this is fixed in the prereleases?
The classes have changed and I am not sure where everything has moved. Maybe some of it is in the acb and some in the aby class (1.13-pre5 names).
However the aby class still adds the banner-banner combination twice to the same hash map, so I am going to leave the report open and add 1.13-pre5 as affected version.
Still exist in 1.14.3 pre-3
Unable to resolve BlockEntity for ItemStack: minecraft:airStill exists in 1.15.0 using `--forceUpgrade`
Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
Unable to resolve BlockEntity for ItemStack: minecraft:spawner
Just updated a server from 1.15.2 to 1.16.2 and I had :
The warns appeared only once though. Is it something that could possibly cause world corruption?
It would likely not be corrupting the world, but at most make these affected items non-functional (i.e. placing them might not apply the NBT data correctly). However, I don't think there have been any NBT changes for signs in the recent versions which could cause any issues.
Good to know. This affects only items, not the respective blocks, right? I had some signs in my inventory that executed commands when right-clicked. It might have to do with that.
Is this still an issue in 1.17.1 or later?
In 1.17.1 the Mojang class name appears to be net.minecraft.util.datafix.schemas.V99.
It looks like at least some of the points mentioned in the description still apply. For example the map named ITEM_TO_BLOCKENTITY still uses some block IDs (which do not exist as item IDs) as keys.
I am going to add 1.17.1 as affected version, though the description might in parts be outdated.