Capopanzone
- capopanzone
- capopanzone
- Europe/Stockholm
- Yes
- No
When breaking blocks, the particles are only from the bottom side texture of that block. This bug it's present since Beta 1.7.2. In Beta 1.7_01 that particles used the texture of the side on which the pointer was.
Also, when running, the blocks use their bottom textures, when it would be more correct if they used their top side texture.
When breaking blocks, the particles are only from the bottom side texture of that block. This bug it's present since Beta 1.7.2. In Beta 1.7_01 that particles used the texture of the side on which the pointer was.
Also, when running, the blocks use their bottom textures, when it would be more correct if they used their top side texture.
HOW TO REPRODUCE:
Sprint on grass blocks, the particles are from the bottom texture.
Hit a workbench on its top side, the particles will use the bottom texture (it's the oak planks texture).
Biomes change color too brusquely: they change color whitin 4 or 5 blocks and tall grass/fern/vines and sky color don't fade at all. This issue is present since Anvil file format was added and it's very noticeable when there is a river in the jungle biome. I downloaded 12w03a, when jungles where added, but world used the old format, so i have a bunch of screenshots for comparison (the first and the last screenshots are from 1.4.3pre, the others are from 12w03a).
Biomes change color too brusquely: they change color w
hitin 4 or 5 blocks and tall grass/fern/vines and sky color don't fade at all. This issue is present since Anvil file format was added and it's very noticeable when there is a river in the jungle biome. I downloaded 12w03a, when jungles where added, but world used the old format, so i have a bunch of screenshots for comparison (the first and the last screenshots are from 1.4.3pre, the others are from 12w03a).Biomes change color too brusquely: they change color within 4 or 5 blocks and tall grass/fern/vines and sky color don't fade at all. This issue is present since Anvil file format was added and it's very noticeable when there is a river in the jungle biome. I downloaded 12w03a, when jungles where added, but world used the old format, so i have a bunch of screenshots for comparison (the first and the last screenshots are from 1.4.3pre, the others are from 12w03a).
Large oak trees don't spawn, they're replaced with some strange trees.
The %% in the attribute strings (such as attribute.modifier.plus.1=+%d%% %s) isn't parsed correctly and doesn't print the % character when playing with Pocket UI. This can be easily seen with speed, slowness, strenght
and weaknesspotions.Tested on Android using only the default resource pack and the English US language. This is not an issue when playing with classic UI.
The %% in the attribute strings (such as attribute.modifier.plus.1=+%d%% %s) isn't parsed correctly and doesn't print the % character when playing with Pocket UI. This can be easily seen with speed, slowness, and strenght potions.
Tested on Android using only the default resource pack and the English US language. This is not an issue when playing with classic UI.
The %% in the attribute strings (such as attribute.modifier.plus.1=+%d%% %s) isn't parsed correctly and doesn't print the % character when playing with Pocket UI. This can be easily seen with speed, slowness, and streng
ht potions.Tested on Android using only the default resource pack and the English US language. This is not an issue when playing with classic UI.
The %% in the attribute strings (such as attribute.modifier.plus.1=+%d%% %s) isn't parsed correctly and doesn't print the % character when playing with Pocket UI. This can be easily seen with speed, slowness, and strength potions.
Tested on Android using only the default resource pack and the English US language. This is not an issue when playing with classic UI.
Also tested on Windows 10: not an issue in both classic and pocket UI settings
The %% in the attribute strings (such as attribute.modifier.plus.1=+%d%% %s) isn't parsed correctly and doesn't print the % character when playing with Pocket UI. This can be easily seen with speed, slowness, and strength potions.
Tested on Android using only the default resource pack and the English US language. This is not an issue when playing with classic UI.
Also tested on Windows 10: not an issue in both classic and pocket UI settings.
Update: it seems to be an issue only when playing with touch controls. I have just tried playing on Android with a bluetooth controller on Pocket UI and the % sign showed up.
"Getting Wood" è un modo di dire inglese che si usa quando il pene è in erezione, quindi si è scelto di tradurlo con un modo di dire simile.
"Preparing spawn area %s%%" string is hardcoded/not translatable
A few blocks have no translation in the en_us file:
- `block.minecraft.bubble_column`
- `block.minecraft.tall_sea_grass`
- `block.minecraft.kelp`
- `block.minecraft.potted_oak_sapling`
- `block.minecraft.potted_spruce_sapling`
- `block.minecraft.potted_birch_sapling`
- `block.minecraft.potted_jungle_sapling`
- `block.minecraft.potted_acacia_sapling`
- `block.minecraft.potted_dark_oak_sapling`
- `block.minecraft.potted_fern`
- `block.minecraft.potted_dead_bush`
- `block.minecraft.potted_dandelion`
- `block.minecraft.potted_poppy`
- `block.minecraft.potted_blue_orchid`
- `block.minecraft.potted_allium`
- `block.minecraft.potted_azure_bluet`
- `block.minecraft.potted_red_tulip`
- `block.minecraft.potted_orange_tulip`
- `block.minecraft.potted_white_tulip`
- `block.minecraft.potted_pink_tulip`
- `block.minecraft.potted_oxeye_daisy`
- `block.minecraft.potted_brown_mushroom`
- `block.minecraft.potted_red_mushroom`
- `block.minecraft.potted_cactus`
This issue can be fixed by adding these to the language file:
`"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",`A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
{{"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",}}
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
{{"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",}}A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",}}
"block.minecraft.kelp": "Kelp Column",}}
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",}}
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",}}
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",}}
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",}}
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",}}
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",}}
"block.minecraft.potted_fern": "Potted Fern",}}
"block.minecraft.potted_dead_bush": "Potted Dead Bush",}}
"block.minecraft.potted_dandelion": "Potted Dandelion",}}
"block.minecraft.potted_poppy": "Potted Poppy",}}
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",}}
"block.minecraft.potted_allium": "Potted Allium",}}
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",}}
"block.minecraft.potted_red_tulip": "Potted Red Tulip",}}
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",}}
"block.minecraft.potted_white_tulip": "Potted White Tulip",}}
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",}}
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",}}
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",}}
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",}}
"block.minecraft.potted_cactus": "Potted Cactus",}}
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column","block.minecraft.tall_sea_grass": "Tall Sea Grass",}}"block.minecraft.kelp": "Kelp Column",}}"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",}}"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",}}"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",}}"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",}}"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",}}"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",}}"block.minecraft.potted_fern": "Potted Fern",}}"block.minecraft.potted_dead_bush": "Potted Dead Bush",}}"block.minecraft.potted_dandelion": "Potted Dandelion",}}"block.minecraft.potted_poppy": "Potted Poppy",}}"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",}}"block.minecraft.potted_allium": "Potted Allium",}}"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",}}"block.minecraft.potted_red_tulip": "Potted Red Tulip",}}"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",}}"block.minecraft.potted_white_tulip": "Potted White Tulip",}}"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",}}"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",}}"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",}}"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",}}"block.minecraft.potted_cactus": "Potted Cactus",}}A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",Note on kelp: I would change its ID to kelp_column and the ID of kelp_top (also used by the inventory form) to just kelp, so that the ID names and the translations are consistent.
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",Note on kelp: I would change its ID to kelp_column and the ID of kelp_top (also used by the inventory form) to just kelp, so that the ID names and the translations are consistent.
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",Note on kelp: I would change its ID to kelp_column and the ID of kelp_top (also used by the inventory form) to just kelp, so that the ID names and the translations are consistent.
Missing translations in en_us.json for certain blocks and entities
The bug
A few blocks have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus",Note on kelp: I would change its ID to kelp_column and the ID of kelp_top (also used by the inventory form) to just kelp, so that the ID names and the translations are consistent.
The bug
A few blocks and entities have no translation in the en_us file:
- block.minecraft.bubble_column
- block.minecraft.tall_sea_grass
- block.minecraft.kelp
- block.minecraft.potted_oak_sapling
- block.minecraft.potted_spruce_sapling
- block.minecraft.potted_birch_sapling
- block.minecraft.potted_jungle_sapling
- block.minecraft.potted_acacia_sapling
- block.minecraft.potted_dark_oak_sapling
- block.minecraft.potted_fern
- block.minecraft.potted_dead_bush
- block.minecraft.potted_dandelion
- block.minecraft.potted_poppy
- block.minecraft.potted_blue_orchid
- block.minecraft.potted_allium
- block.minecraft.potted_azure_bluet
- block.minecraft.potted_red_tulip
- block.minecraft.potted_orange_tulip
- block.minecraft.potted_white_tulip
- block.minecraft.potted_pink_tulip
- block.minecraft.potted_oxeye_daisy
- block.minecraft.potted_brown_mushroom
- block.minecraft.potted_red_mushroom
- block.minecraft.potted_cactus
- entity.minecraft.cod_mob
- entity.minecraft.salmon_mob
- entity.minecraft.puffer_fish
This issue can be fixed by adding these to the language file:
"block.minecraft.bubble_column": "Bubble Column",
"block.minecraft.tall_sea_grass": "Tall Sea Grass",
"block.minecraft.kelp": "Kelp Column",
"block.minecraft.potted_oak_sapling": "Potted Oak Sapling",
"block.minecraft.potted_spruce_sapling": "Potted Spruce Sapling",
"block.minecraft.potted_birch_sapling": "Potted Birch Sapling",
"block.minecraft.potted_jungle_sapling": "Potted Jungle Sapling",
"block.minecraft.potted_acacia_sapling": "Potted Acacia Sapling",
"block.minecraft.potted_dark_oak_sapling" "Potted Dark Oak Sapling",
"block.minecraft.potted_fern": "Potted Fern",
"block.minecraft.potted_dead_bush": "Potted Dead Bush",
"block.minecraft.potted_dandelion": "Potted Dandelion",
"block.minecraft.potted_poppy": "Potted Poppy",
"block.minecraft.potted_blue_orchid": "Potted Blue Orchid",
"block.minecraft.potted_allium": "Potted Allium",
"block.minecraft.potted_azure_bluet": "Potted Azure Bluet",
"block.minecraft.potted_red_tulip": "Potted Red Tulip",
"block.minecraft.potted_orange_tulip": "Potted Orange Tulip",
"block.minecraft.potted_white_tulip": "Potted White Tulip",
"block.minecraft.potted_pink_tulip": "Potted Pink Tulip",
"block.minecraft.potted_oxeye_daisy": "Potted Oxeye Daisy",
"block.minecraft.potted_brown_mushroom": "Potted Brown Mushroom",
"block.minecraft.potted_red_mushroom": "Potted Red Mushroom",
"block.minecraft.potted_cactus": "Potted Cactus","entity.minecraft.cod_mob": "Cod",
"entity.minecraft.salmon_mob": "Salmon",
"entity.minecraft.puffer_fish": "Pufferfish",Note on kelp: I would change its ID to kelp_column and the ID of kelp_top (also used by the inventory form) to just kelp, so that the ID names and the translations are consistent.
The ID name of a few blocks, items and entities isn't consistent with the translated name or the ID of another form of that object:
Blocks and items
- mob_spawner should be spawner
- Consistency with block name, which is more correct as spawners can actually spawn any kind of entity
- melon should be melon_slice
- Consistency with item name
- speckled_melon should be glistering_melon
- Consistency with item name
- melon_block should be melon
- Consistency with block name
- experience_bottle should be xp_bottle
- Consistency with entity ID name and xp_orb
- prismarine_bricks_slab should be prismarine_brick_slab
- See MC-126034
- prismarine_bricks_stairs should be prismarine_brick_stairs
- See MC-126034
Entities
- commandblock_minecart should be{{ command_block_minecart}}
- Consistency with item ID name
- ender_crystal should be end_crystal
- Consistency with item ID name
- evocation_illager should be evoker
- Consistency with entity name
- fireworks_rocket should be firework_rocket
- Consistency with item ID name
- illusion_illager should be illusioner
- Consistency with entity name
- snowman should be snow_golem
- Consistency with entity name
- village_golem should be iron_golem
- Consistency with entity name
- vindication_illager should be vindicator
- Consistency with entity name
Tooltip "Cannot build unresolved tag entry" is not translatable. This message was shown as a tooltip for the command.failed string after loading a data pack.
Step to reproduce:
- Enable the attached data pack
- Hover with the mouse on the command failed message
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT
`HideFlags:32`.Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT
{HideFlags:32}.
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT
{HideFlags:32}.
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT HideFlags:32 .
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT HideFlags:32 .
This affects both banners worn by illagers and banners generated in outposts.
Ominous banners generated in outposts show the pattern list
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT HideFlags:32.
This affects
both banners worn by illagers andbanners generated in outposts.This bug can't be fully fixed due to
MC-178410.
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT HideFlags:32.
This affects
both banners worn by illagers andbanners generated in outposts and banners dropped by pillagers that have been placed and then mined.This bug can't be fully fixed due to
MC-178410.
Ominous/illager banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode. This can be fixed by adding the NBT HideFlags:32.
This affects
both banners worn by illagers andbanners generated in outposts and banners dropped by pillagers that have been placed and then mined.This bug can't be fully fixed due to
MC-178410.Ominous banners show their last 6 patterns on the tooltip, even though they have 8 patterns (the tooltip can only show 6 of them), and it's useless information as they can't be recreated in Survival mode.
This affects banners generated in outposts and banners dropped by pillagers that have been placed and then mined.
This bug can't be fully fixed due to
MC-178410.
In pre-release 4 double yod has been fixed, geresh and gershayim have been lowered.
Ambient occlusion doesn't affect End portal frames (both normal and filled) despite their model files being changed to include the line `"ambientocclusion": true,`.
Ambient occlusion doesn't affect End portal frames (both normal and filled) despite their model files being changed to include the line "ambientocclusion": true, .
Ambient occlusion doesn't affect End portal frames (both normal and filled) despite their model files being changed to include the line "ambientocclusion": true, .
This is related to
MC-165503
As in the title, doors, end portal frames (both normal and with eye) and fence gates attached to a wall aren't affected by ambient occlusion, despite similar blocks being affected.
Related issue for End portal frames:
MC-165504
In 20w06a the names for ```smooth_quartz``` and ```bamboo_sapling``` were changed to "Smooth Quartz Block" and "Bamboo Shoot". Despite this, their ID wasn't updated. This also affect other files such as textures, models, recipes, advancements and loot tables.
In 20w06a the names for smooth_quartz and bamboo_sapling were changed to "Smooth Quartz Block" and "Bamboo Shoot". Despite this, their ID wasn't updated. This also affect other files such as textures, models, recipes, advancements and loot tables.
weeping_vines and weeping_vines_plant
names arethe same ("Weeping Vines") despite them being different blocks. The translation for the string block.minecraft.weeping_vines_plant should be changed to "Weeping Vines Plant".The name of weeping_vines and weeping_vines_plant is the same ("Weeping Vines") despite them being different blocks. The translation for the string block.minecraft.weeping_vines_plant should be changed to "Weeping Vines Plant".
en_us.json issue:missing distinction betweenweeping_vines and weeping_vines_planten_us.json issue: weeping_vines and weeping_vines_plant have the same name
Snapshot 20w09a changed the lighting direction in the Nether to be more similar to Bedrock Edition. This change only applies to blocks and doesn't affect:
- fluids
- blocks that are rendered as entities (chests, signs, heads, shulker boxes, etc.)
- entites
New Nether lighting system doesn't affect fluids,block entities (chests, etc.) and entitiesNew Nether lighting system doesn't affect fluids, entity-like blocks (chests, etc.) and entities
The name of twisting_vines and twisting_vines_plant
nameis the same ("Twisting Vines") despite them being different blocks. The translation for the string block.minecraft.twisting_vines_plant should be changed to "Twisting Vines Plant".
This issue prevents
MC-148057to be fully fixed. Banners worn by captains correctly hide the pattern list, but this property is lost once the banners are placed, mined and picked up in the inventory again. This also prevents banners generated in outposts to hide the pattern list once mined and obtained in the inventory.To reproduce:
- Locate a pillager outpost
- Kill a pillager captain and collect the ominous banner
- The pattern list won't be shown in the inventory
- Place the ominous banner
- Mine it
- The pattern list will be shown in the inventory
Banners don't savethe HideTags tag when placed down as blocksBanners don't support the HideTags tag when placed down as blocks
Banners don't support the HideTags tag when placed down as blocksBanners don't support the HideFlags tag when placed down as blocks
This issue prevents
MC-148057to be fully fixed. Banners worn and dropped by captains correctly hide the pattern list, but this property is lost once the banners are placed, mined and picked up in the inventory again. This also prevents banners generated in outposts to hide the pattern list once mined and obtained in the inventory.To reproduce:
- Locate a pillager outpost
- Kill a pillager captain and collect the ominous banner
- The pattern list won't be shown in the inventory
- Place the ominous banner
- Mine it
- The pattern list will be shown in the inventory
Long block names such as "Smooth Red Sandstone Stairs" or "Polished Blackstone Pressure Plate" can overlap or even extend past the height info in the superflat customization screen. This is also an issue for many other languages which have longer block names compared to English.
To reproduce, use this superflat preset:
minecraft:smooth_red_sandstone_stairs,minecraft:waxed_lightly_weathered_cut_copper_stairs,minecraft:polished_blackstone_pressure_plate;minecraft:the_voidRelated issues:
MC-26757,MC-203757A possible quick fix could be making the two columns more spaced apart, and anchroing them to the window border so more room is available when the window is larger.
Long block names such as "Smooth Red Sandstone Stairs" or "Polished Blackstone Pressure Plate" can overlap or even extend past the height info in the superflat customization screen. This is also an issue for many other languages which have longer block names compared to English.
To reproduce, use this superflat preset:
minecraft:smooth_red_sandstone_stairs,minecraft:waxed_lightly_weathered_cut_copper_stairs,minecraft:polished_blackstone_pressure_plate;minecraft:the_voidRelated issues:
MC-26757,MC-203757A possible quick fix could be making the two columns more spaced apart, and anchroing them to the window border so more room is available when the window is larger.
The name of cave_vines_body and cave_vines_head is the same ("Cave Vines") despite them being different blocks. Note that the IDs themselves are also inconsistent with similar blocks such as weeping vines (
MC-213765). The translation of cave_vines_body should be changed to "Cave Vines Plant", while the translation of cave_vines_head should be left as "Cave Vines".To reproduce this bug, run the command
/give @s minecraft:shears{CanDestroy:"minecraft:cave_vines_head","minecraft:cave_vines_body"]}Notice how both types of cave vines blocks share the same name.
The name of cave_vines_body and cave_vines_head is the same ("Cave Vines") despite them being different blocks. Note that the IDs themselves are also inconsistent with similar blocks such as weeping vines (MC-213765). The translation of cave_vines_body should be changed to "Cave Vines Plant", while the translation of cave_vines_head should be left as "Cave Vines".To reproduce this bug, run the command
/give @s minecraft:shears{CanDestroy:"minecraft:cave_vines_head","minecraft:cave_vines_body"]}Notice how both types of cave vines blocks share the same name.
Can't reproduce in 1.17 pre1
![]()
Can't reproduce in 1.17 pre1 (seed: -8558177248601725758 coordinates: -383 76 27)
![]()
Surface generation of lofty peaks changed between experimental snapshots and regular snapshots. Now every stone block is covered with snow blocks (not just snow layers), which was not the case in the experimental snapshots (for example, see theese screenshots from Henrik Kniberg's twitter https://twitter.com/henrikkniberg/status/1433723910122582041
).Bedrock edition is unaffected by this change, and lofty peaks still generate like in the experimental snapshots.
Here are a few comparison screenshots (seed: 3006516195185472982)
(experimental snapshot 7, note how some of the stone is only covered by snow layers and not full snow blocks)
(Bedrock 1.17.40.21, not all stone is covered by snow blocks)
(Java 21w39a, all the stone blocks are covered with snow blocks)Surface generation of lofty peaks changed between experimental snapshots and regular snapshots. Now every stone block is covered with snow blocks (not just snow layers), which was not the case in the experimental snapshots (for example, see theese screenshots from Henrik Kniberg's twitter https://twitter.com/henrikkniberg/status/1433723910122582041).
Bedrock edition is unaffected by this change, and lofty peaks still generate like in the experimental snapshots.
Here are a few comparison screenshots (seed: 3006516195185472982)
(experimental snapshot 7, note how some of the stone is only covered by snow layers and not full snow blocks)
(Bedrock 1.17.40.21, not all stone is covered by snow blocks)
(Java 21w39a, all the stone blocks are covered with snow blocks)
Stone inloftypeaks is always covered by snow blocksStone in jagged peaks is always covered by snow blocks
Surface generation of
loftypeaks changed between experimental snapshots and regular snapshots. Now every stone block is covered with snow blocks (not just snow layers), which was not the case in the experimental snapshots (for example, see theese screenshots from Henrik Kniberg's twitter https://twitter.com/henrikkniberg/status/1433723910122582041).Bedrock edition is unaffected by this change, and
loftypeaks still generate like in the experimental snapshots.Here are a few comparison screenshots (seed: 3006516195185472982)
(experimental snapshot 7, note how some of the stone is only covered by snow layers and not full snow blocks)
(Bedrock 1.17.40.21, not all stone is covered by snow blocks)
(Java 21w39a, all the stone blocks are covered with snow blocks)Surface generation of jagged peaks changed between experimental snapshots and regular snapshots. Now every stone block is covered with snow blocks (not just snow layers), which was not the case in the experimental snapshots (for example, see theese screenshots from Henrik Kniberg's twitter https://twitter.com/henrikkniberg/status/1433723910122582041).
Bedrock edition is unaffected by this change, and jagged peaks still generate like in the experimental snapshots.
Here are a few comparison screenshots (seed: 3006516195185472982)
(experimental snapshot 7, note how some of the stone is only covered by snow layers and not full snow blocks)
(Bedrock 1.17.40.21, not all stone is covered by snow blocks)
(Java 21w39a, all the stone blocks are covered with snow blocks)
The bug
The strings at position and [HERE] of the immediate command response cannot be translated.
How to reproduce
- Switch to any non English language
- Type
/experience set @a test
Remark
The [HERE] of the command echo is translatable
Analysis
Code analysis of this issue can be found in this comment by Capopanzone.
Capopanzone, please create a new ticket for that, if we don't have one already.
Capopanzone can you update the affected versions as it is still a problem in the newest release 1.15.1.
I have figured out why this is a difficult problem to solve. The end frame had once AO turned on but that gave this bug: MC-51113 (TLDR darkens the top face of the end protal frame) I suspect that the other items suffer similar problems if the their AO is set on. Solving this problem will fix a bunch of other related bug such as MC-160917 where custom models cant have any complex geometry without being effect by the MC-51113 bug.
The current way Minecraft calculates AO is via each voxel (which is good as it's fast to compute). The downside is that any sub geometry of the voxel (i.e. 3d details in a given block) experiences unexpected darkening.
There is a solutions to this problem, and it should be relatively easy to implement:
In the model (.json) file, give the possibility to either enable or disable AO per face and/or per element, while still including AO for the root tag as it should be an indicator for the projection of AO on neighboring voxels/blocks. So to fix the case of the end portal frame just disable AO on the top face, or create a new element that only includes the top face and disable AO on that.
Capopanzone could you also make one for MC-202598?


































Also, 11 should be obtainable in survival.
This can be fixed by saving achievements per world, so they won't be lost on every minecraft.jar change. Also, if achivements were saved per world, it would be possible to give them a utility, such a experience reward!
Even wooden fence has this problem.
Please close, I see other people had this problem.
Another screenshot! It's easy to see the extra flame!
Ugly!
They also go "behind" ice. Boring bug, I hope this will be fixed soon.
You can see the seed I used, so you can reproduce easily.
Confirmed for Italian. Fix please!
It seems to be fixed in 13w10a.
In Italian translation, for splash potions, we decided to add "(Da lancio)" (means throw-able) before the potion name.
It also happens with villagers and Iron golems.
Confirmed for 24b. I'd really like to see this fixed.
Still in 13w24b
Still in 13w36b. I'd to see this fixed in the biome update...
Still in 1.12 pre-2
Still an issue in 1.12-pre2
Partially fixed in 1.12-pre6: only game messages were made available, the hardcoded Realms strings are still hardcoded
Fixed in 1.12-pre6
Confirmed for 1.2.0.25:
It also happen with furnaces. Fuels don't get moved to the fuel slot if there's an incomplete stack in the inventory. This doesn't happen with ingredients and doesn't happen at all on Java.
I can confirm it in 1.2.0.25
I experience this issue on Android (7.0) with touch controls and Windows 10 with keyboard and mouse
Confirmed for 17w48a. Fixing this would literally take less than a minute.
Sort of fixed in 17w48a. The redstone wire block translation has been changed to "Redstone Dust" and the sugar canes item translation has been removed.
Could this be intentional? It's a cool effect imho and already happens on Bedrock edition.
Is this really a bug? That's part of the river biome, it's just less noticeable in other biomes because they are generally lower/flatter and already have grass and trees. The only way to fix this is adding a new river sub-biome that would spawn inside mesas, but that's more of a feature request rather than a bug report.
Confirmed for 17w49a.
Not fixed in 1.2.10 build 1. Mineshafts still generate in one place making them both rare and messy.
Seed: -340659009
Coordinates: 2515 30 -172
IIRC it matches Java. If it were changed in some old Java edition update, then is a missing/outdated feature and not really a bug
This issue is different though. Flower pots are trying to use a key that doesn't exist anymore and uses an old format
I don't agree with "clayball", it doesn't really exist as a single word and it's fine as it is now. Snowball is often used as a single word and slimeball is a fantasy item I guess, so those are fine as single words.
"Lapis Ore" and "Lapis Block" would be inconsistent with the "Lapis Lazuli" item. Their IDs should be changed instead.
I'm not a native speaker either
"Snowball" seems to be by far the most common form. Language is often inconsistent and there's not much we can do about that. I would change the current kelp (which has no translation in en_us - related:
MC-126022) to kelp_column and kelp_top (translated as "Kelp", used by both the top block and the inventory form) to just kelp. Also you forgot to remove lapis block and ore from the other ticket!I don't think they can just change the item ID of kelps. Items that place blocks (sugar cane, sign, flower pot, etc.) now use the block translation so I'm believing that those items are just the blocks with a different icon for inventories. If this is indeed correct, they can't change only the kelp item as it's not different than the kelp_top.block.
So kelp (untranslated) -> kelp_column ("Kelp Column")
and kelp_top ("Kelp", both block and inventory form) -> kelp ("Kelp")
IMHO would be the best solution
Oh right, that's true
They can spawn treasure maps - which is working as intended - and filled maps, which are labelled as "Unknown Map" and get drawn when you hold it. In Java Edition this type of map is an empty map, which makes more sense
Still an issue in 1.4.2 and beta versions
It is a bug: the string is hardcoded, not in the en_us json, thus it can't be translated in any language. As it is not on the json lang file, it's not available on Crowdin.
It is fixed in 1.13-pre6 - the en_us.json file now contains the line "menu.preparingSpawn": "Preparing spawn area". Crowdin has not been updated yet but that's not an issue with the game.
Fixed some time between 1.13-pre5 and 1.13
Glad to see this fixed. Now the best biome generates correctly!
Fixed in 1.11.0.3
Fixed in 19w13b!
Fixed in 1.14.2 pre-release 3
Fixed in 1.14.2 pre-release 3
Yep, there's an extra pixel coming from the maqaf, which isn't aligned properly in the spritesheet
Double yod is fixed in 1.14.4 pre-release 1
"Bee hive" should be "Beehive", which is the more common form
It's fixed in 19w38b (and I suppose 38a too)
As of 19w45b, these blocks are still shaded even if they shouldn’t:
• saplings, flowers, mushrooms, dead bushes and ferns in flower pots – inconsistent with cross-model plants including themselves when not planted in a pot
• pumpkin and melon stems (both normal and attached) – inconsistent with cross-model plants and other crops
• redstone torches in repeaters and comparators – inconsistent with normal redstone torches
Sneaking is a toggle with controllers and touch controls in Bedrock and you keep sneaking when you open an inventory.
Is it really an issue? The honey level is a block state and ctrl+pick block only copies NBT data.
Still an issue in 19w45b. This affects the hardness and blast resistance of:
• smooth sandstone
• smooth sandstone stairs
• sandstone slab
• cut sandstone slab
• smooth sandstone slab
• smooth red sandstone
• smooth red sandstone stairs
• red sandstone slab
• cut red sandstone slab
• smooth red sandstone slab
• smooth quartz block
• smooth quartz stairs
• quartz slab
• smooth quartz slab
This is a duplicate of
MC-152441. They forgot to update the models for corner stairs when they changed the texture mapping for regular and smooth quartz.Beds are also affected, but that's a different issue as they are rendered as entities and entities don't support ambient occlusion.
Is this really a bug? This is due to how texture mapping works for pretty much every block. Stairs textures aren't rotated so they blend in with the full blocks.
Not being able to reduce the render distance below 9 would mean many players with less powerful PCs wouldn't be able to play the game anymore. It would be the worst way to fix this issue.
Slightly related to
MC-165503Still an issue both in 1.14.4 and 1.15 pre2
This issue also seems to affect shulker boxes in the 1.15 snapshots. This is mostly noticeable on withe shulker boxes with the brightness set to moody.
It still happen in 1.15.2-pre2, but I'm not sure it's really a bug. Furnace minecarts are supposed to push carts, not pull them
Thanks for the explanation. I don't think there's any issue with AO on doors and fence gates. Fence gates normally already have AO, they are missing in ONLY when they are attached to a wall, which is obviously an inconsistency and not intended.
Yeah, that could also work. Nice to see this has been assigned anyway. It would be nice if they were available in the Creative inventory like in Bedrock, but that would be a feature request I guess.
Awwww I made separate tickets for the other issues.
MC-171526: weeping vines plant translationMC-171529: wall banner translation (not reported here, but related)Oopsie, I suck at searching
This issue affects the en_us language and we can't modify it on Crowdin. Issues with en_us have always been allowed here, so please reopen.
IMHO every block is too dark in the inventory. Either the lighting should be less drastic, or changed so that the right side is brighter than the left side, or block models should face to the right instead of the left.
affects 20w10a
The old issue was resolved as "WAI" due to the world generator being redone then-recently. Can this be re-opened again?
potted_bamboo.json
The fix is really simple, you just need to remove the bottom face of bamboo.
There are two possible fixes for this: one is really easy and not really a fix, which is using the bottom texture instead of the side texture. The other one requires creating "template" models for walls which support 3 different textures and then using those templates for sandstone and red sandstone wall models. These fixed models are included in the attached resource pack. MC-137957 Sandstone wall fixes.zip
All the screenshots except for stems should be removed as those issues were fixed and the ticket now only covers stems. I have attached a resource pack with fixed stem models. It also removes shading, just like they looked before 1.8. MC-96463 Stem fixes.zip
Each mushroom block in Java has 64 states (each face can show either the red/brown/stem texture or the pores texture, so that's 2^6 possible combinations), while Bedrock is AFAIK still limited to 16 states. Stem blocks are also different, as in Bedrock they are variants of red/brown mushroom block, while in Java they have their own ID and are the same for both red and brown mushrooms. The placement differences can only be fixed if/when Bedrock finally recives the flattening.
In the meanwhile, mushroom block drops could be changed to the 6-sided cap variants (data value 14) instead of the pore variant (data value 0). Stem variants already drop themselves, so that's fine.
Can this be reopened? It affects new versions too. I also request ownership of this ticket, if possible. I opened this ticket with an older account, I use this account nowadays.
Related to MC-124142,
MC-171523,MC-171526Also relates to MC-124142 and
MC-174481Also related to
MC-174481Affects 20w11a
Affects 20w11a
It's fixed for banners dropped by pillagers, but not for banners generated in outposts.
container.hopper should just be "Hopper", there's no need of "Item"
Can't reproduce in 20w13b. Are you using a resource pack? https://i.imgur.com/FPrVvWS.png
Soul sand does
It also affects blackstone walls, the side texture is used in every face
This is still an issue in 1.16.0.58 despite almost every other villager trade being changed to match Java Edition. Clearly the trades are intended to be the same as Java, so this is a parity issue.
Ah you mean that. The issue is different. These blocks aren't affected by ambient occlusion on their faces, soul sand doesn't cast ambient occlusion on other blocks and that's another different issue.
A few more untranslatable strings:
Can confirm. Coral fans can't survive on waterlogged blocks (e.g. an upper slab) and it's inconsistent with normal coral and Java Edition behavior.
Would it be a parity issue now? Non-oak signs have been updated in the Bedrock 1.16 betas
Yeah, it seems you don't get this error anymore. I'll open a new bug ticker or comment here/on discord if I experience it again.
The 1.15 advancements descriptions all use incorrect capitalization:
Or "click" should be lowercase, since this is just a description. Either way it's inconsistent
Should it? It's really just a message, not a title or button text that needs capitalization. "Left Shift" is capitalized because it's the string used for the key in the controls menu.
Not really a bug, those characters in your resource pack are probably using codepoints which are actually assigned to other characters and thus show up as the correct character when you use the unicode font. Mind sharing your pack?
That character is not an apostrophe, but an acute accent (´) that is missing from the default minecraft font, so it shows up using the unicode font
They simply aren't included neither in the default font nor in the Unicode font. Support for extended range has been added only recently, but the unifont sheets are outdated/incomplete (
MC-108045)They show up as empty squares to me when using either the default font or the Unicode font (https://i.imgur.com/hubRQJq.png). This is expected because they are not supported in any font.
This also affect the ominous banner, which relies on display tag and shows its name in italics
You can sort of fix it in chat by increasing the line spacing, but it can still affect other text boxes such as signs
I don't think it's really necessary to make purpur blocks and chorus blocks dragon-immune, but end stone bricks (+ slab, stairs, wall) and ender chest really should be dragon immune, since it's inconsistent with end stone and obsidian
I'd say the waxed, cut, and waxed cut variants are missing the word "Block". Quartz block variants keep "Block" in their names ("Chiseled Quartz Block", "Smooth Quartz Block")
This can be seen with waxed slightly weathered cut copper stairs in the creative inventory using the default windowed resolution and the default GUI size. The name is quite long, so the tooltip gets moved to the left - too bad there's also not enough room on the left and thus it appears cut off. A possible fix would be moving the tooltip below the cursor if there's also not enough room on the left. Note that the name "Waxed Slightly Weathered Cut Copper Stairs" is fine and not the issue here, and it can't really be shortened without losing information about the block.
The pattern translations follow the names used in heraldry, so these should be translated as "<color> Field" (https://en.wikipedia.org/wiki/Field_(heraldry))
The "at position" message is translatable now (command.context.parse_error), but "<--[HERE]" is still hardcoded when typing a command. See attached screenshot, it is translated in chat but not in the command suggestion area.
Infested blocks are always mined instantly regardless of the tool you are using. This was changed in 1.13 and I suppose it was done on purpose, otherwise it was possible to distinguish infested blocks from regular stone (in older versions, and currently in Bedrock, infested blocks had a set mining time and no tool assigned, so you tell whether a stone block was regular or infested)
Amethyst geodes can replace End portal frames
Seed: -341133055506249258
Coordinates: /execute in minecraft:overworld run tp @s 10893.67 41.25 9545.98 -136.20 34.20
The ideal fix would be increasing the anvil character limit, the issue here is that the anvil limit is too short. Shortening the copper block names wouldn't fix this issue as many languages have names that are longer than 35 characters and often there's no real way to shorten those.
The best fix would be renaming all the mineral blocks to "X Block", so that they are consistent with their IDs (iron_block, quartz_block etc) and other manufactured blocks ("Snow Block", "Magma Block", "Bone Block" etc), and in the case of quartz to be consistent with its variants ("Block of Quartz" vs "Smooth Quartz Block", "Chiseled Quartz Block")
At the very least it should be changed so that the entire "<action> is bound to <key>" string is used as the placeholder for "%s button", instead of just the key name. This is pretty annoying in languages such as Italian which use a different word order for "%s button" - the result is something like "<action> is bound to button <key>". The best fix would still be not using "%s button" at all for these buttons.
For comparison, this is how long tooltips are handled in Bedrock. If there's not enough room on the left it gets centered over the pointer.
I've attached a text file which should fix all the outdated, inconsistent or incorrect names (including a few that have been missed in this report). While it's true most of these names were changed before Java 1.15, I believe they are still valid issues as they are inconsistent with other names (e.g. planks, slabs and stairs using "wood") or IDs (e.g. "enchantment table"), or could be simplified ("pillar quartz block").
fixed names.txt
It might have been fixed for copper blocks (as their names got shortened), but 35 characters is still too low for other names in other languages, so the core issue here (anvil char limit being too low) hasn't been fixed yet.
Still an issue in 21w05a
Related issue with names:
MC-213911Can confirm
Here's an alternative fix with no weird mirroring effects at some angles crop - alt fix.json
.
can confirm
The simpliest fix would be allowing grass and flowers to be placed on sand and gravel (MC-223826). In real life you can find some plants can grow on sandy and gravelly soils, and in Minecraft it would allow for more decoration options.
This is also a parity issue, as in Bedrock axolotl buckets have different names depending on the axolotl variant (for example: "Bucket of Adult Cyan Axolotl", "Bucket of Baby Leucistic Axolotl")
Also affects potted azaleas and potted flowering azaleas
MC-129428 is still open and was triaged by Mojang, and
MC-173015was fixed. Saplings and mushrooms are growable plants, while dead bushes are simplier ground cover blocks, more similar to flowers and grass.I've dug into the Minecraft code (version 1.17.1-pre1, decompiled using Mojang's mappings) and found the cause. I've come up with a possible fix, but I'm not entirely sure it will work, as I've had no way to test it and my Java knowledge is extremely limited and extremely rusty.
Code analysis
com.mojang.brigadier.exceptions.CommandSyntaxtExceptions.java
The getContext method returns the last 10 characters of a faulty inputted command, followed by "<-
[HERE]". "<[HERE]" is defined directly in the code, so it's not translatable. This is intended, Brigadier is meant to be a standalone library which can be used by other pieces of software, so it should not directly reference any Minecraft classes or assets. However, this is the reason why "<-[HERE]" is not translatable in the parse error message.public String getContext() { if (this.input == null || this.cursor < 0) { return null; } StringBuilder stringBuilder = new StringBuilder(); int n = Math.min(this.input.length(), this.cursor); if (n > 10) { stringBuilder.append("..."); } stringBuilder.append(this.input.substring(Math.max(0, n - 10), n)); stringBuilder.append("<--[HERE]"); return stringBuilder.toString(); }net.minecraft.client.gui.components.CommandSuggestions.java
The getExceptionMessage method prepares the parse error message by inputting the cursor position and the command context in the translation string command.context.parse_error ("in position %s: %s"). The command context is returned by the getContext method from the Brigadier library, so it includes the hardcoded "<--[HERE]".
private static FormattedCharSequence getExceptionMessage(CommandSyntaxException commandSyntaxException) { Component component = ComponentUtils.fromMessage(commandSyntaxException.getRawMessage()); String string = commandSyntaxException.getContext(); if (string == null) { return component.getVisualOrderText(); } return new TranslatableComponent("command.context.parse_error", component, commandSyntaxException.getCursor(), string).getVisualOrderText(); }Possible fix
com.mojang.brigadier.exceptions.CommandSyntaxtExceptions.java
I suggest fixing it by adding a new method which only returns the last 10 characters of the input command, whithout appending anything after it. The game will use this method - instead of getContext - to prepare the parse error message.
getContext now will simply append "<--[HERE]" to the output of getRawContext.
public String getContext() { StringBuilder stringBuilder = newStringBuilder(this.getRawContext()); stringBuilder.append("<--[HERE]"); return stringBuilder.toString() }net.minecraft.client.gui.components.CommandSuggestions.java
getExceptionMessage will now reference getRawContext instead of getContext.
private static FormattedCharSequence getExceptionMessage(CommandSyntaxException commandSyntaxException) { Component component = ComponentUtils.fromMessage(commandSyntaxException.getRawMessage()); String string = commandSyntaxException.getRawContext(); if (string == null) { return component.getVisualOrderText(); } return new TranslatableComponent("command.context.parse_error", component, commandSyntaxException.getCursor(), string).getVisualOrderText(); }en_us.json
The string command.context.parse_error should then be changed to include "<--[HERE]", allowing translators to translate it properly and change the word order if needed.
"command.context.parse_error": "in position %s: %s<--[HERE]",still an issue in the most recent versions
Fixed in 1.17.30.22 by adding separate strings for awkward/thick/mundane potions, and all types of splash and lingering potions.
The generation of ground vegetation seems a bit off in general, probably due to 3D biomes.
A bunch of extreme hills sub-biomes were missed in the experimental snapshots and weren't renamed. I imagine we should report them separately if they don't get renamed along with the other extreme hills in the next snapshots, but I'll report them here for now, in case Mojang reads these comments.
It seems to be fixed, it didn't seem to be an issue in 39a either (except at biome borders)
Can confirm
Can confirm
The new look of the pipe symbol is correct, as it's a pipe and not a broken bar (¦ U+00A6). Adding spaces or color-coding the command suggestions would be the ideal fixes
Paths and farmland are fine, they are affected by ambient occlusion (their sides are darkened towards the bottom). They don't cast a shadow, which is a separate issue that affects other partial blocks as well (slabs, stairs etc) -
MC-139621