So I spent forever trying to figure this out so hopefully this solves the problem for those of you in the same situation.

So we use the BiomeLoadingEvent to catch when biomes are loading and add our ConfiguredFeature. Ore Generation like so:

public class WorldGen {

    public static final ConfiguredFeature<?, ?> yourOre = Feature.ORE.withConfiguration(
            new OreFeatureConfig(OreFeatureConfig.FillerBlockType.BASE_STONE_OVERWORLD, YourRegistryHandler.YOUR_ORE.get().getDefaultState(), 4)) //vein size
            .range(12).square() //maximum y level where ore can spawn
            .count(3); //how many veins maximum per chunck

    public static void generateOre(final BiomeLoadingEvent event) {
        BiomeGenerationSettingsBuilder generation = event.getGeneration();
        if (event.getCategory().equals(Biome.Category.ICY)) { //OPTIONAL IF STATMENT allows you to generate ores in specfifc biome types for exmaple icy biomes
            generation.withFeature(GenerationStage.Decoration.UNDERGROUND_ORES, yourOre);
        }
    }
}

Now we need to know where to register this event do NOT use EventBus it will crash your mod on startup by trying to register generation before registering your ore block instead we register this in our main class like so:

//if you use the mdk this function will be pre generated so we only add our refrence here
private void setup(final FMLCommonSetupEvent event) {
        // some preinit code
        LOGGER.info("HELLO FROM PREINIT");
        LOGGER.info("DIRT BLOCK >> {}", Blocks.DIRT.getRegistryName());
  	MinecraftForge.EVENT_BUS.addListener(EventPriority.HIGH, WorldGen::generateOre); //our refrence
    }

 

ALTERNITIVE use if you are generating a bunch of ores in the same way

 

public class WorldGen {

  public static final List<ConfiguredFeature<?, ?>> yourOreList = new ArrayList<>();
  
  public static void init() {
      yourOreList.add(Feature.ORE.withConfiguration(
            new OreFeatureConfig(OreFeatureConfig.FillerBlockType.BASE_STONE_OVERWORLD, YourRegistryHandler.YOUR_ORE_1.get().getDefaultState(), 4)) //vein size
            .range(12).square() //maximum y level where ore can spawn
            .count(3); //how many veins maximum per chunck
      );
      
      yourOreList.add(Feature.ORE.withConfiguration(
            new OreFeatureConfig(OreFeatureConfig.FillerBlockType.BASE_STONE_OVERWORLD, YourRegistryHandler.YOUR_ORE_2.get().getDefaultState(), 4)) //vein size
            .range(12).square() //maximum y level where ore can spawn
            .count(3); //how many veins maximum per chunck
      );

    public static void generateOre(final BiomeLoadingEvent event) {
        BiomeGenerationSettingsBuilder generation = event.getGeneration();
        for (ConfiguredFeature ore : yourOreList) {
          generation.withFeature(GenerationStage.Decoration.UNDERGROUND_ORES, ore);
        }
    }
}

You still register in the same way.

 

Hope this helps.

Edited March 28, 20214 yr by Koolade446
Format error

This will crash if loaded before blocks are registered and will bottleneck world gen for other mods. The ConfiguredFeature needs to be registered to the associated WorldGenRegistries registry. It also should be made after all registries have passed (e.g. FMLCommonSetupEvent) and registered there via Registry::register since there is no forge associated registry. This can be done by lazily storing the value and resolving it within the common setup.

1. I know that’s why the listener is added in CommenSetup

2. Thank you for the information I will use this method in the future

31 minutes ago, Koolade446 said:

1. I know that’s why the listener is added in CommenSetup

Listeners should be added in the constructor. Make the field lazy instead of relying on classloading.