Open 321nick opened 3 years ago
I think you could keep bedrock enabled for the dimension and instead use custom ore generation of very large stone "ore"-veins at y = 0...5 that replace bedrock blocks:
INIT() {
add("oregen", 0, "minecraft:bedrock", 1.25, 50, "minecraft:stone", "center", [1, 2, 5]#);
...
}
The arguments for the config command are as follows:
"oregen"
: we want to add ore generation 0
is the dimension ID for Overworld"minecraft:bedrock"
: the block to generate in1.25
is the average number of veins per chunk and controls how frequently there will be holes in bedrock layer.50
is number of blocks per vein, and controls the size of the holes. (50 is the default size for vanilla underground dirt blobs)"minecraft:stone"
: the block to generate as ore vein"center"
: height distribution mode[1, 2, 5]#
: min, center and max heights
The problem
Completely replacing the bedrock layer will probably lead to incompatability with BedrockOres, which generates factorio-esque deposits of ore on the bedrock layer
My solution
Allow for more nuanced bedrock replacement, IE instead of removing it entirely only make "holes" in the bedrock that the player can travel through too other dimensions
Why the existing features won't cut it
As far as i can tell both methods of disabling bedrock, wether through completely deactivating it or replacing it are global, and have no support for having only partial replacement of the bedrock layer
Additional context ill have too check in bedrock ores config if they dont have a workaround on their end, but i dont think they would.