Diamond generation is still rare after 1.17.2

I am also seeing this issue in 1.17.2. I started a whole new world up after the update on 22nd to check if this was now playable, and I used the same seed as a pre 22nd world I’d spent countless hours in where I found 2 diamonds. Early in this latest release/ world I found 6 diamonds in one spot and believed this showed signs of being resolved. I have now spent about 6 actual hours mining at Y 10 and have not found any more diamonds. 
This still appears not to be working properly as compared to the frequency of diamond discovery at the same levels pre 1.17 release. 

In order to check my claims I created a brand new map/savegame and used the fill command to clear 0<y<20 of all dirt, stone, water, lava, etc. and was able to find about 60 diamonds total within thousands of blocks. (Roughly a 140x20x140 area - I may have done the math wrong but I believe this is hundreds of thousands)

In order to check my claims I created a brand new map/savegame and used the fill command to clear 0<y<20 of all dirt, stone, water, lava, etc. and was able to find about 60 diamonds total within thousands of blocks. (Roughly a 140x20x140 area - I may have done the math wrong but I believe this is hundreds of thousands)

@unknown: Back on 24 June you said "The gamesave was created since the most recent patch on the console, so new chunks I'd imagine." That doesn't follow. Once generated, chunks can only be modified by the effects of world simulation, because regenerating them according to changes in the world generation logic would likely wipe out anything done by players, mobs, etc.

In regard to your new map and exposing ores between Y=0 and 20, from the date of that comment I expect you did that experiment under 1.17.2, in which case the ore distribution should be as given for 1.18 according to this chart on the wiki. As you can see, diamonds are very rare from Y=0 to 16 and absent from there to Y=20, so your latest observations apparently match expectations.

EDIT I forgot to account for the Caves and Cliffs Experimental toggle. What I said above only applies if your world has that toggle turned on. If you don't, please comment to tell me so.

@unknown: Back on 24 June you said "The gamesave was created since the most recent patch on the console, so new chunks I'd imagine." That doesn't follow. Once generated, chunks can only be modified by the effects of world simulation, because regenerating them according to changes in the world generation logic would likely wipe out anything done by players, mobs, etc.

In regard to your new map and exposing ores between Y=0 and 20, from the date of that comment I expect you did that experiment under 1.17.2, in which case the ore distribution should be as given for 1.18 according to this chart on the wiki. As you can see, diamonds are very rare from Y=0 to 16 and absent from there to Y=20, so your latest observations apparently match expectations.

EDIT I forgot to account for the Caves and Cliffs Experimental toggle. What I said above only applies if your world has that toggle turned on. If you don't, please comment to tell me so.

@unknown: If you still aren't able to explain the problem you see after reviewing the expanded note in the description at the top of the report, please provide the world seed, location, size and direction of the area you were mining, and whether you have the Caves & Cliffs Experimental toggle turned on.

@unknown: If you still aren't able to explain the problem you see after reviewing the expanded note in the description at the top of the report, please provide the world seed, location, size and direction of the area you were mining, and whether you have the Caves & Cliffs Experimental toggle turned on.

this is still a consistent issue. I have tried new chunks in old world as well as creating several new worlds and having the same problem. I am playing 1.17 with experimental gameplay on. I have looked up the ore generation and it seems most common above y=90, which the majority of the world does not even generate that high. Coal ore should be most common around the same levels that the ores that require it are generated in. 
I don’t think anybody is happy about having to now create 5 mines rather than just one, but it would be fine if it were actually possible to get the ores we need. 
i should also note that all of the coal I have found so far is next to open air blocks (which I understand it should be the exact opposite) and that I have strip mines at y= -59, 5, 11, 16, & 36 because different sources recommend different levels for mining.

this is still a consistent issue. I have tried new chunks in old world as well as creating several new worlds and having the same problem. I am playing 1.17 with experimental gameplay on. I have looked up the ore generation and it seems most common above y=90, which the majority of the world does not even generate that high. Coal ore should be most common around the same levels that the ores that require it are generated in. 
I don’t think anybody is happy about having to now create 5 mines rather than just one, but it would be fine if it were actually possible to get the ores we need. 
i should also note that all of the coal I have found so far is next to open air blocks (which I understand it should be the exact opposite) and that I have strip mines at y= -59, 5, 11, 16, & 36 because different sources recommend different levels for mining.

@unknown: Unfortunately, you didn't provide all the information we need, as discussed in the note at the top. Without the missing information, we can't draw any conclusions from your summary. We need the details.

You say you've created several new worlds with this problem. All we need you to do is to attach one of them, tell us the coordinates of one or more areas you mined in it, and tell us which ore(s) you believe do not occur at the expected rate there. If the world is too big to upload, just give us the seed and the setting of the Caves & Cliffs toggle along with the coordinates and ore types.

We will use this information to count the exact number of ore blocks of the kind(s) you identify in a large enough volume toovercome the effects of local variation, and compare that to the appropriate distribution as given by Mojang's charts. If we agree that there's a consistent tendency to be too few or too many, we'll submit it to the developers (probably as a new bug report, but we'll link to it from here).

@unknown: Unfortunately, you didn't provide all the information we need, as discussed in the note at the top. Without the missing information, we can't draw any conclusions from your summary. We need the details.

You say you've created several new worlds with this problem. All we need you to do is to attach one of them, tell us the coordinates of one or more areas you mined in it, and tell us which ore(s) you believe do not occur at the expected rate there. If the world is too big to upload, just give us the seed and the setting of the Caves & Cliffs toggle along with the coordinates and ore types.

We will use this information to count the exact number of ore blocks of the kind(s) you identify in a large enough volume toovercome the effects of local variation, and compare that to the appropriate distribution as given by Mojang's charts. If we agree that there's a consistent tendency to be too few or too many, we'll submit it to the developers (probably as a new bug report, but we'll link to it from here).

@unknown: You are spamming useless comments all over multiple tickets. Please read our Guidelines to learn hose to use the bug tracker. This is not a chat site. Comments should only be used to provide information needed by the developers, not to talk to other users.

@unknown: You are spamming useless comments all over multiple tickets. Please read our Guidelines to learn hose to use the bug tracker. This is not a chat site. Comments should only be used to provide information needed by the developers, not to talk to other users.

Resolving as Awaiting Response. Please reopen the ticket if you can reproduce the issue in the latest versions (1.17.11 Hotfix or 1.17.30.25 Beta) in a new world.

Resolving as Awaiting Response. Please reopen the ticket if you can reproduce the issue in the latest versions (1.17.11 Hotfix or 1.17.30.25 Beta) in a new world.

1.17.11 has already been marked as affected.

1.17.11 has already been marked as affected.

@unknown Has anyone confirmed that this issue occurs for new worlds in 1.17.11? If not, I'd like the ticket to remain as AR until we get a reliable way to reproduce it without importing older worlds.

@unknown Has anyone confirmed that this issue occurs for new worlds in 1.17.11? If not, I'd like the ticket to remain as AR until we get a reliable way to reproduce it without importing older worlds.

I haven't seen anything yet.