Minecart Copper
Comments
because you need Silk Touch tools to get a grass block and breaking a grass block without said tools gives you dirt.... works pretty well As Intended
where you catch fire, place block. fire will become visible again. punch fire out or place block. It is a real PITA bug and game lagging bug if you get enough hidden fires going in a spot. Happens in the nether when exploding beds also.
I should also add, "my fix" I added the replace diorite/andesite/granite into the diamond_ore_feature.json before the update and had diamonds replace diorite. And after your update those diamonds spawned in the same spot only in stone this time since you fixed the over generation of the diorite and andesite.
But was it really completely fixed?? I am using the BDS Server program thing and I had reset my diamonds to the proper 8 vs 4 in the one file the day before the fix was released... And sort of a half way fix caused me to dig around some more. And in "Fixing it my way" I got diamonds to spawn where no diamonds were prior. I started a seed, and just kept restarting in creative and going to where I had found diamonds to investigate. What happened was, when I "fixed it" I didn't fix the diorite/andesite over spawn, tbh didn't even think of it! When You fixed it, diorite/andesite that had previously been there turned to stone and allowed for diamond generation again. But my question in regards to diamond ore spawning in now it still doesn't appear to be fixed prior to 1.17. And as a basis I am using this.
In the BDS files for the game version 1.16.201.02, file path ....bedrock-server-1.16.201.02\definitions\features\diamond_ore_feature.json the file says diamond can replace stone, andesite, diorite and granite. Which is what the Wiki also states.
"count": 8,
"places_block": "minecraft:diamond_ore",
"may_replace": [
{
"name": "minecraft:stone",
"states": {
"stone_type": "andesite"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "andesite_smooth"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "diorite"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "diorite_smooth"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "granite"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "granite_smooth"
}
},
{
"name": "minecraft:stone",
"states": {
"stone_type": "stone"
But now, in the 17.2.01 update that same pathway \bedrock-server-1.17.2.01\definitions\features\diamond_ore_feature.json looks like this:
"count": 8,
"replace_rules": [
{
"places_block": "minecraft:diamond_ore",
"may_replace": [
{
"name": "minecraft:stone"
And in the 1.17 pathway, bedrock-server-1.17.2.01\behavior_packs\vanilla_1.17.0\features\diamond_ore_feature.json it is saying,
"count": 8,
"replace_rules": [
{
"places_block": "minecraft:diamond_ore",
"may_replace": [
{
"name": "minecraft:stone"
}
]
},
{
"places_block": "minecraft:deepslate_diamond_ore",
"may_replace": [
{
"name": "minecraft:deepslate"
So diamond is still only able to replace plain stone and no other variants of stone like andesite, diorite and granite. And also, deepslate diamonds can only replace deepslate where as the online wiki suggested that deepslate diamond should also be able to replace tuff blocks.
So has this become the "New normal" for 1.17+ where diamond can only replace stone blocks and no variants? And deepslate diamonds will only be able to replace deepslate blocks and the Wiki is incorrect in an assumption that the tuff block would be replaceable?
So to be fixed "Prior to 1.17" diamond should have the chance to replace other stone variants again. Or am I understanding those files incorrectly?
campfire, nest and break the block above the nest if there is one so the smoke goes through. don't leave a space between fire and nest