Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Posted

Hi, after my last thread, someone on the Forge Discord server gave me some code to generate ores. However, this code doesn't appear to be generating my block anywhere, and I was wondering if anyone could tell me why.

 

Here is my code:

OreGen class:

package linky132.waywardcraft;

import net.minecraft.block.BlockState;
import net.minecraft.util.registry.Registry;
import net.minecraft.util.registry.WorldGenRegistries;
import net.minecraft.world.gen.GenerationStage;
import net.minecraft.world.gen.feature.ConfiguredFeature;
import net.minecraft.world.gen.feature.Feature;
import net.minecraft.world.gen.feature.OreFeatureConfig;
import net.minecraftforge.event.world.BiomeLoadingEvent;
import net.minecraftforge.eventbus.api.SubscribeEvent;

import java.util.ArrayList;

public class OreGen
{
    public static final ArrayList<ConfiguredFeature<?,?>> ORE_GENERATORS = new ArrayList<>();

    public static void register()
    {
        registerOreGenerator(RegistryHandler.SALT_BLOCK.get().getDefaultState(),16,200,"salt_block");
    }

    public static void registerOreGenerator(BlockState blockState, int patchSize, int maxHeight, String name)
    {
        Registry<ConfiguredFeature<?, ?>> registry = WorldGenRegistries.CONFIGURED_FEATURE;
        ConfiguredFeature<?,?> configuredFeature = Feature.ORE.withConfiguration(new OreFeatureConfig(OreFeatureConfig.FillerBlockType.BASE_STONE_OVERWORLD,blockState,patchSize)).range(maxHeight).square().func_242731_b(157);
        ORE_GENERATORS.add(configuredFeature);
        Registry.register(registry,WaywardCraft.MODID + name,configuredFeature);
    }

    @SubscribeEvent
    public void loadBiomes(BiomeLoadingEvent event)
    {
        for(ConfiguredFeature<?,?> feature : ORE_GENERATORS)
        {
            event.getGeneration().withFeature(GenerationStage.Decoration.UNDERGROUND_ORES,feature);
        }
    }
}

 

Main mod class:

package linky132.waywardcraft;

import net.minecraftforge.common.MinecraftForge;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.event.lifecycle.FMLCommonSetupEvent;

@Mod(WaywardCraft.MODID)
public class WaywardCraft
{
    public static final String MODID = "waywardcraft";

    public WaywardCraft()
    {
        MinecraftForge.EVENT_BUS.register(this);

        RegistryHandler.init();

        MinecraftForge.EVENT_BUS.register(new OreGen());
    }
    void commonSetup(FMLCommonSetupEvent event)
    {
        event.enqueueWork(this::afterCommonSetup);
    }
    private void afterCommonSetup()
    {
        OreGen.register();
    }
}

 

Thank you.

Edited by Linky132

Have you checked if this:

    @SubscribeEvent
    public void loadBiomes(BiomeLoadingEvent event)
    {
        for(ConfiguredFeature<?,?> feature : ORE_GENERATORS)
        {
            event.getGeneration().withFeature(GenerationStage.Decoration.UNDERGROUND_ORES,feature);
        }
    }

is actually fired or not?

Check out the port of the BetterEnd fabric mod (WIP): https://www.curseforge.com/minecraft/mc-mods/betterend-forge-port

  • Author

Thanks for replying. I just checked it by using a print method, and the funny thing is that the "loadBiomes" method is firing, but the contents of the for loop are never executed. Any idea why that could be?

Edited by Linky132

  • Author

Huh, that's weird, apparently the list is empty. That doesn't make sense, though, since configuredFeature is being added to it, and looks to be valid. I can also confirm that it's not a problem with my block, as it also doesn't work with vanilla blocks. Any ideas?

  • Author

Aha, so that's the problem! the afterCommonSetup method is never called, which is probably due to the commonSetup method not being called either. I assume I did something wrong with the event bus or the listener?

  • Author

Okay, so using that information, I tried replacing the forge bus line with

FMLJavaModLoadingContext.get().getModEventBus().register(new OreGen());

but it resulted in an error while loading the mod, basically just saying:

java.lang.IllegalArgumentException: Method public void linky132.waywardcraft.OreGen.loadBiomes(net.minecraftforge.event.world.BiomeLoadingEvent) has @SubscribeEvent annotation, but takes an argument that is not a subtype of the base type interface net.minecraftforge.fml.event.lifecycle.IModBusEvent: class net.minecraftforge.event.world.BiomeLoadingEvent

 

You had this in your class constructor:

    public WaywardCraft()
    {
        MinecraftForge.EVENT_BUS.register(this);

        RegistryHandler.init();

        MinecraftForge.EVENT_BUS.register(new OreGen());
    }
    

With the third line you are registering the OreGen class to the Forge bus, this means that loadBiomes will correctly listen to the BiomeLoadingEvent (FORGE bus).

With the first line you are instead registering the main mod class (this) to the Forge bus, so any event handler in the main class will listen only to Forge bus events, but FMLCommonSetupEvent is fired on the MOD bus. So you need to register you main class to the MOD bus, which you can get from:

FMLJavaModLoadingContext.get().getModEventBus();

Instead of subscribing your whole class, you can also add listeners to the Mod bus with:

FMLJavaModLoadingContext.get().getModEventBus().addListener(your_listener_method)

 

Check out the port of the BetterEnd fabric mod (WIP): https://www.curseforge.com/minecraft/mc-mods/betterend-forge-port

  • Author

That fixed it!! I can finally move on from ore generation! 😂 Thank you so much for your help!!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.