mojira.dev

alef

Assigned

No issues.

Reported

MC-227268 Maps don't work properly in old terrain when caves and cliffs data pack is enabled Invalid MC-8541 Beds can't be broken in adventure mode Duplicate MC-1077 Flipped green pointers on maps inside item frames Works As Intended

Comments

More info

  • Both attached screenshot have been taken from 1.17-pre4

  • The first screenshot is the map locked in 1.16.5. It is not a new map generated in 1.17-pre4

  • A map generated in snapshot 1.17 can render partially fine and stone-like depending whether the rendered chunks have been generated with or without datapack.

In such case, minecarts with chest may embed in calcite. The rail block is gone but the minecart vehicle has not been replaced removed.

Reoccurring in 15w51b. It happens also for World Type: Customised -> Customise

In 15w47c, a secondary effect of this is that as you log out and back in, your horse has been duplicated with the same equipment. To be checked if this also duplicates the items in the chest on a donkey.

1.8 adventure mode changes should close this issue too.

Confirmed in 14w03b

  • 13w25c SMP Windows7,Java7,64-bit

  • 3 rd copy at scale 1:2, never changed scale during copies

    • the other two hung in frames, green pointers show correctly

      • hung inside the map range

  • noticed after server restart

  • white pointer is drawn between paper and map pixels

  • MC-3416_z-order.png: upper right is the round white pointer

13w19a. The level.dat of re-created hardcore world has TAG_Byte(hardcore) set to 0, while the original is 1.

Using MCP 730c on 13w02b: bed's Material.id is "cloth" (115), so you would think to use the shears.
But if you look at ItemShears' canHarvestBlock()/getStrVsBlock() call stack, the match on blockID fails because Block.cloth.blockID is 35 and bed's is 26, so it checks for the Item's strength that returns 1.0F, which in turn fails at canCurrentToolHarvestBlock() (requires > 1.0F).

It doesn't work with any of:

1. Sword
2. Axe
3. Shovel
4. Pickaxe

Looking into MCP, the "frame-" kind of — MapCoord is initialized with the frame direction, so yes it sounds intentional.

Please close.