Diamond ores are very rare

In Caves and Cliffs beta, there's a change to ore generation. No longer it's just the mine at Y12 thing. It was Y32 to Y0 with peak around Y12, but now it's Y64 to Y-64 and Y0 being the peak. Plus they can be skipped generating if they would generate exposed to air.

Yes, i am aware of these generation changes of the ores but should it also affect the generation when the button to activate or deactivate the new caves is also deactivated?

Great question. I'm not sure myself.

I believe it shouldn't affect, because as the Caves and Cliffs update will be divided into two parts, the first being just the blocks and mobs and the second being the update of the world and structures, the generation of ores should be normal as long as I don't activate the function of generating the new caves and mountains.
So I think it is a bug, as I do not believe that the generation would be so affected this way until the end of the year when the second part of the update comes out.

Here's another test I did. For him, I followed the same protocol as the first test (using the / fill command to remove blocks that were not diamond ore) but this time I ran the test in two situations: 1) Using the latest official version of Minecraft Bedrock Edition, 1.16.221; 2) Using the last beta version released until the date of this comment, at 1.17.0.54, without activating the Caves and Cliffs button.
Methodology: I separated a random seed for the test and assigned a random region for the experiment. After that, I designated a 50 X 50 area to remove unwanted stone blocks and ores, keeping only diamond ores. To ensure this, the / fill and replace command was used. Finally, the bubbles of diamond ores were marked with redstone blocks, 1 for each set.
Results: It is clearly noticeable a considerable reduction in the presence of diamond ores, not only in numbers but also in the quantity grouped (unfortunately I forgot to take the prints showing the quantity present in each cluster, but if they repeat the process they will be able to easily perceive).
This was the methodology I used to fortify my argument that the generation of diamond ores was, in some way, hindered. For added security, I ask that, if possible, those who see this post, perform a similar test on other maps and bring more information to reinforce or refute the post.
The seed used for the test was: 1356942840
The coordinates used were: X 2702, Y 91, Z -123 to X 2652, Y 91, Z -73.

The images referring to this test have been attached to this post.

Maybe 🤔

Very thorough look. Nicely done!

Well, I have a certain notion that most of those who report bugs here, especially betas, like me are more experienced players, and I also understand that an increase in the difficulty of finding certain resources is something that we would like, but we also have to think about those who play more casually and for less time than us. I spent almost five hours mining as I always did, looking in caves and making tunnels, to find just five diamonds. This is clearly something that would greatly detract from the experience of those who have less time to spend during a day and they could take up to a week if they did not know how to search correctly.
According to a quick count that I made, based on the general quantity and using the prints I brought showing the difference in the generation of diamond ores, I was able to make a numerical comparison in theory. The number of diamond ores in an area of ​​50 x 50 varies from 35-45 for version 1.16.221 and from 10-15 for beta version 1.17.0.54.
I believe it is clear that if it was a deliberate reduction or a bug that was maintained it would be very harmful for players with less time and experience, not to mention that it is a very big difference for an area of ​​3 chunks x 3 chunks
Note: The comparison of the number of ores was made based on my experience with the quantity in the generated sets, that is, in general the large sets have from 5 to 8 ores, and in the beta, if I am not visible the probability of having another just below is low.
Note²: A margin of error has been added to ensure that the numbers are not outside the actual values.
As a guarantee, if those who read it still have doubts, please run the experiment and perform the counting.

It june 8th, and finding diamonds are still a problem. ive been playing in my new world for 6 hours now and have only found 7 diamonds... ive gone to countless caves and crevasses to find nothing. ive been in one cave ( currently still am ) for 2 hours going through every possible way to Y12-y16 and still nothing.

Definitely rarer than they should be. New world loaded but with same seed as have been playing on for last year and my wife has just found the first two diamond ore blocks in around 10hrs of play whereas in previous version we were well on the way to getting kitted out by that time.
Have checked all the usual spots (Y level, near lava, etc) but only found these two blocks of diamond ore next to each other in an abandoned mineshaft.

Ive been mining for 4 hours and only 3 diamonds on the oficial release (1.17.2.0). I knew there was something wrong. Tried joining the beta (1.17.10.22 beta) and the generation of diamonds appeared to be solved.

Does anyone know when they will update it?

My friends and I started a new realm and this is definitely an issue because none of us are able to find to anymore than like 8 each or more than 2 per vain and I went mining for like 3-4 hours and only found 2. We were thinking it was because with the new caves coming out later, the new best mining y axis is like -64 or something, so diamonds were pushed down to -64 without there being a -64 if thats even possible. Hope this issue gets fixed soon

This issue will be fixed in 1.17.10.

When will 1.17.10 be released? I really want to play survival but it sucks because I can't find diamonds even though I mine for hours.

I investigated the differences in diamond ore generation between 1.16.221 and 1.17.0. I generated fresh worlds with the same seed in both versions and used rbedrock to compare 49 chunks centered around the world spawn in both versions. I then identified all locations that where diamond ores in either world (both normal and deepslate) in either world. I then grabbed the blocks in these locations in both world and constructed a table to highlight the differences.

A couple observations:

1. The distribution of ores has not changed between versions. If it had changed you would see locations in 1.17 that had diamond ores that didn't have ores in 1.16. But you don't. This is confirmed by looking at the jsons for diamond ore features, which still creates one ore cluster per chunk between y=0 and y =15.

2. However, 64% of the diamond ore blocks have gone missing, and in their place is stuff like stone (which they should replace according to the jsons) and deepslate (which they don't replace according to the jsons, but maybe they should).

My guess on what is happening: deepslate is causing ore generation to stop. So when the algorithm encounters deepslate, it stops trying to place diamonds. This is why some stone blocks are not being converted into diamonds.

Update: I was looking in the wrong location for feature descriptions. Turns out the in 1.17.0 diamond ore veins were made smaller (4 blocks instead of 8 blocks). But this has been fixed in 1.17.10.

We have gone through multiple seeds on Nintendo Switch and PS4 and had this same issue. 

The diamonds always spawn in clumps of 1 or two.  We have found more Emeralds and geodes on some seeds.  It’s quite frustrating as the 2 - 8 rule no longer applies. 

I expected changes with the full update, but with a scaled back one something didn’t go right here. 

When it is fixed, in 1.17.1 will we have to go out to areas already not explored/visited - or will they be able to do a mini reset of chunks not actually interacted with? 

Alright, since people are still questioning why, this is how the diamond ore generation got reduced to literally half of what it is intended to. The "count" was set to 4 instead of the default 8 in the diamond_ore_feature.json file, which is likely caused by copying the same files from the experimental caves behavior packs.

@mrs-turambar / c c page - This is a great question I'm also curious about. I've been avoiding exploring any further in the world I created (but already spent a lot of time in) because I don't want to generate new chunks that also have no diamonds. This is a game-breaking bug for anyone starting a new world or mining in a new place, and I don't think it's getting the attention it deserves. The spawn rate may have been cut in half, but the likelihood of finding diamonds during standard branch mining is probably 1/10th what it normally would be because vein size is so small. 

At the momento im not playing minecraft, i started a new world and if i play it then when they fix the diamond stuff then i will have alot of chunks with the old generation ... I have my old world from 1.16 that i dont want to mine because i dont want to generate new world.  Kinda annoying that i cant play now because i really dont want new chunks loaded with the bugged diamond stuff. 

Also really rare on XBOX VERSION

I added 2 screenshots. Same seed, same location, diamond ores exposed.
One is from 1.16.221 and one is from 1.17.0.

Painfully reduced. I am glad to see that this is being treated as a bug and not closed as “works as intended”

There is no need for new comments as this is already fixed in the 1.17.10.21 beta/upcoming 1.17.10 release, unless you can show that this still occurs in the latest 1.17.10 beta. We do not know when the full 1.17.10 release will occur, but based on previous releases, if Mojang releases betas for a newer version, you can expect it to arrive within a week or two of those betas. When the update arrives, you will have to generate new chunks/explore new areas to find the normal diamond ore sizes.

What's your seed?

I haven't really seen this bug yet, but I'll make sure to take a screenshot soon on my Nintendo Switch, and I'll soon convert the image to my device.  I'll edit this comment when I'm finished.

I'm pretty sure what is going on is that when they added 1.17 they added the new generation so diamonds a more common below y 0 which is not accessible so we have to wait for mojang to revert ore generation (except maybe copper)

I been wondering is it also a java problem so that i temporary play jave till this is fixed

Update just came out

oh

but is it fixed?

wait no it is not out i checked my updates and it is not

The hotfix that came out today was only for Switch, it did not fix this issue.

Is it fixed for switch?

Usually switch gets minecraft updates first, so maybe today everyone else will get it. It says the current version on switch is 1.17.1

can you confirm it is fixed on switch

I'll check in 10 mins

Today's hot fix update for switch was only to fix an issue specific to Nintendo Switch.
This issue with ore generation has already been fixed in the beta version and will likely be in a stable release in the near future (no date can be given).

As mentioned before, this ticket does not require anymore comments, if you would like to discuss the issue, please have the conversation else where.

Comments that do not follow the bug tracker guidelines will be removed, most notably comments that do not add new information to the report.

Thanks

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Please note: This is a bug tracker not a community forum. If you would like to discuss this issue, please do so elsewhere.

Please review these guidelines for using the bug tracker: https://help.minecraft.net/hc/en-us/articles/360049840492-Mojang-Bug-Tracker-Guidelines
They are a great source of useful information on how to contribute here, what this site is for and gow it should be used.
Please do not ask when updates will come out, we often don't know until you know.
Please do not complain about issues as this site is for reporting not a place to express your feelings about an issue.
Failure to comply with these guidelines may result in loss of bug tracker privileges. This is a warning.

Just to be clear:
Comments that add new information about the issue are okay to add (ex this issue still effects the next stable release)
Comments that do not will be removed.

As said before, this ticket does not need any more comments. If you want to discuss this bug, go to elsewhere, such as Mojira on Reddit, or the Mojira Discord.

What happened was that the new ore generation was accidentally implemented so diamonds are now much rarer because they are supposed to be more common in deepslate levels, and we don't have them yet.

Further comments on this ticket are useless as this issue has been fixed in the Beta and will be fixed for everybody in the next retail update, which will probably be 1.17.10. The bug tracker staff do not know when that will happen, though it will probably be soon. Please be patient.

Reminder: The bug tracker is not a discussion site. Comments here should be addressed to the staff or developers and should provide additional information that might help the developers find and fix the problem. We also allow sharing workarounds you've found, since that can help the developers too. Other comments are considered off-topic and will be removed.

For discussion between players, please use a site designed for that, such as the Community Support Discord.

This is now fixed in 1.17.2 on all platforms. 1.17.2 was released today.

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?

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.

I honestly am also starting to doubt that this is 100% fixed, but I can't say for sure. I did some tests of my own and I can confirm that the diamond ore generation is definitely better, but I think I'm gonna have to come up with a new method of finding and mining them.

I've been mining a bit lower than usual and I've found a bunch of diamonds in less than an hour, so maybe try to mine on levels 6-11 instead of 12-15! Hope this helps! 

Generally the problem before was that blobs were harder to find AND they were much smaller.  So when you did find them, it was less lucrative...a double whammy so to speak.  In worlds created in 1.17, I NEVER saw a Diamond blob larger than 3, and most were singles/doubles.  During the 1.17.0 diamond struggles, I saw that Java was having more success at lower levels...  On a world where I needed the "starter 5" diamonds (pick and enchanting table), I resorted to making a tunnel at Y5 below all my Y11 tunnels and had much more success finding ore, but still smaller blobs.

My testing is EXTREMELY small sample size and all anecdotal as I play on ps4, but can confirm that 1.17 ore blobs that were 1-3 on average are now almost all 4+ blob sizes on the same seed...  Sizes back to normal.  As to how many blobs I'm finding (the replace issue), I'm not sure I can comment on that yet.  But I stopped strip mining for tons of diamonds a long time ago and just exploit villager trading for diamond gear now.  I know not everyone plays that way.  Would be nice to know if the "Replace" part of the change is intended or also a bug.

This is definitely fixed. I've been mining today, and within an hour I found two blobs of 8 one of 5, and one of 3. In other words, more diamonds in one hour than I'd found in over ten hours of mining before this fix. With my fortune 3 pickaxe this translated to over 30 pieces of diamond! All I had to do was mine for long enough that new generation had to occur. I was mining at y=11. Thanks Mojang, I've now got my diamond armour and tools and have a reason to go looking for netherite again 🙂

Maybe a stupid question but do I need to make a new world after the fix to find more diamonds, or is the world I made before the fix updated? 

I was about to ask the same question Jill. I have no clue.

Jill and Cyberz,

You simply need to load new chunks. That can be done by either starting a new world or visiting new areas on your old map. If you are sticking to your old world, depending on how much you have already explored, it may be worth travelling through the nether to get to new areas faster. Any chunks that have already loaded in any world prior to the patch will remain as they were.

Hope that helps.

Yes that does help. Thank you so much!

I've been trying to catch up to all the questions on this ticket, but you all are going too fast for me. Thank you for being patient, and special thanks to those of you attempting to answer each other's questions. I think everything that's been said so far is correct.

@unknown: I understand your reasoning and think your question is worth pursuing, but Mojang has applied a fix which everybody agrees (or at least doesn't dispute) improves the situation, so they consider the original problem fixed at this time. It may be that they consider this fix good enough for the time being, and as we already know the ore generation will change again in 1.18, so we don't have a good reason to disagree with calling this report resolved. Instead, what I think should happen is that you create a new ticket assuming that diamond ore is intended to replace andesite and diorite, and giving your reasoning, along with evidence that the replacement isn't happening in 1.17. Mojang will then decide what their intention is and resolve the issue appropriately. Bear in mind, though, that the resolution might be letting the 1.18 changes be how they fix it.