The preferred solution for this issue would be to have specific tuff versions of ores.
When replacing tuff, ores generate with a stone background instead of the characteristic deepslate that is intended of this y region. This is due to tuff being in the wrong block tag. Tuff appears to sometimes be replaced with proper deepslate ores, but this is rare (one example attached) and is probably caused by actual deepslate coincidentally being in that position..
This could be cheaply fixed by simply making that which replaces tuff be deepslate instead, but a preferable, much more elegant solution would instead be to add tuff versions of ores.
Linked issues
is duplicated by 39
relates to 3
Attachments
Comments 17
The color of the stone ores is a much better match to tuff than the deepslate ores – just a thought. Even if this is unintentional, I think it should stay.
This is the same in all cases. There is always a normal ore where tuff is generating. I think this was intended as it is also easier on the eyes and because it seems to be so consistent in the generation.
@unknown, see MC-216735.
Ok, I will let Mojang see this report and see me showing people the change log that says that this isn't a bug
Well, adding Tuff versions would be like adding andesite, diorite and granite versions of them. I mean, they would be nice for building, but really maybe it would just be better to leave things simple.
(Personally I would like to have ores for all stones, maybe some exclusive to some stone in specific, but that should go to the feedback site. Anyway, I'll be happy if they add more variations, just to make the environment better.)
@unknown
MC-164101 had a Mojang Priority and an assignee, it was still marked as WAI
Can confirm.