Jump to content

Recommended Posts

Posted

I wanted to made Custom Ore and I make a new ore.

I want to gen it.

I found this  

 

At here 8:50, There are CountRangeConfig and my intellij doesn't suggest me to use that

package com.frost.frost.world.gen;


import com.frost.frost.Frost;
import com.frost.frost.blocks.FrozeOre;
import net.minecraft.block.BlockState;
import net.minecraft.world.biome.Biome;
import net.minecraft.world.gen.feature.OreFeatureConfig;
import net.minecraftforge.eventbus.api.SubscribeEvent;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.event.lifecycle.FMLLoadCompleteEvent;
import net.minecraftforge.registries.ForgeRegistries;

@Mod.EventBusSubscriber(modid = Frost.MOD_ID, bus = Mod.EventBusSubscriber.Bus.MOD)
public class ModOreGen {

    @SubscribeEvent
    public static void generateOres(FMLLoadCompleteEvent event){
        for (Biome biome : ForgeRegistries.BIOMES){

            //Nether Gen
            if (biome.getCategory() == Biome.Category.NETHER) {

            }
            //End Gen
            else if (biome.getCategory() == Biome.Category.THEEND){
            }
            //Overworld Gen
            else {
            }
        }

    }

    private static void genOre(Biome biome, int count, int bottomOffSet, int topOffset, int max, OreFeatureConfig.FillerBlockType filler, BlockState defaultBlockState, int size){
        CountRangeConfig
    }
}

How do I fix it

Posted

Hey i have been doing the same i been working backwards to find all the different inputs of the "boime.addfeature" functionality. Sorry if i am going at this wrong... i am new to coding in java. Here is what i found.

    private static void genOre(Biome biome, int count, int bottomOffset, int topOffset, int max, RuleTest filler, BlockState defualtBlockstate,int size){
        IPlacementConfig range =;
        ConfiguredPlacement config = Placement.field_242903_g.configure(range);
        OreFeatureConfig feature = new OreFeatureConfig(filler, defualtBlockstate, size);
        biome.func_242427_a(GenerationStage.Decoration.UNDERGROUND_ORES,Feature.ORE.withConfiguration(feature).withPlacement(config));
    }
}

 

So firstly biome.addFeature is func_242427 in 1.16.3 ( I don't know if this is the same for you but it is what i have) it takes in the generation stage which is same as the video.  Then the Feature.Ore.Oreconfig(feature) which is same as the video, as well as the with placement which is the same as the video. But CountRangeConfig functionality probably has changed to something else like the biome.addFeature has change to func_242427 (ignore the IPlacementConfig i haven't looked into it yet but i am going through the code of everything related to withPlacement).

Sadly i have to call it a day before i worked out what range is needed to be I hope this help you or someone else find the solution to this or just teach me i am doing it wrong for a vaild reason.

If you have further questions please ask i will get back as soon as i can.

Posted

Problematic Code 11. If you would like example implementations, look at the Features class. You will notice that there are some helper methods for placements as there can be multiple assigned to the same feature. Therefore, you can have a placement that handles the amount generate, the spread across the chunk, the height level in the chunk, etc. Do note that their order is important.

 

Second, do not use the above tutorial as a reference. It's outdated and uses terrible practices. It's better to just ask questions and infer from your own knowledge of Java than to follow someone else line by line.

Posted
  On 10/21/2020 at 8:07 PM, MkUltra said:

Hey i have been doing the same i been working backwards to find all the different inputs of the "boime.addfeature" functionality. Sorry if i am going at this wrong... i am new to coding in java. Here is what i found.

    private static void genOre(Biome biome, int count, int bottomOffset, int topOffset, int max, RuleTest filler, BlockState defualtBlockstate,int size){
        IPlacementConfig range =;
        ConfiguredPlacement config = Placement.field_242903_g.configure(range);
        OreFeatureConfig feature = new OreFeatureConfig(filler, defualtBlockstate, size);
        biome.func_242427_a(GenerationStage.Decoration.UNDERGROUND_ORES,Feature.ORE.withConfiguration(feature).withPlacement(config));
    }
}

 

So firstly biome.addFeature is func_242427 in 1.16.3 ( I don't know if this is the same for you but it is what i have) it takes in the generation stage which is same as the video.  Then the Feature.Ore.Oreconfig(feature) which is same as the video, as well as the with placement which is the same as the video. But CountRangeConfig functionality probably has changed to something else like the biome.addFeature has change to func_242427 (ignore the IPlacementConfig i haven't looked into it yet but i am going through the code of everything related to withPlacement).

Sadly i have to call it a day before i worked out what range is needed to be I hope this help you or someone else find the solution to this or just teach me i am doing it wrong for a vaild reason.

If you have further questions please ask i will get back as soon as i can.

Expand  

I can't find biome.func_242427

 

Posted

Look for biome.addFeature or similar, then.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted
  On 10/21/2020 at 8:07 PM, MkUltra said:

Hey i have been doing the same i been working backwards to find all the different inputs of the "boime.addfeature" functionality. Sorry if i am going at this wrong... i am new to coding in java. Here is what i found.

    private static void genOre(Biome biome, int count, int bottomOffset, int topOffset, int max, RuleTest filler, BlockState defualtBlockstate,int size){
        IPlacementConfig range =;
        ConfiguredPlacement config = Placement.field_242903_g.configure(range);
        OreFeatureConfig feature = new OreFeatureConfig(filler, defualtBlockstate, size);
        biome.func_242427_a(GenerationStage.Decoration.UNDERGROUND_ORES,Feature.ORE.withConfiguration(feature).withPlacement(config));
    }
}

 

So firstly biome.addFeature is func_242427 in 1.16.3 ( I don't know if this is the same for you but it is what i have) it takes in the generation stage which is same as the video.  Then the Feature.Ore.Oreconfig(feature) which is same as the video, as well as the with placement which is the same as the video. But CountRangeConfig functionality probably has changed to something else like the biome.addFeature has change to func_242427 (ignore the IPlacementConfig i haven't looked into it yet but i am going through the code of everything related to withPlacement).

Sadly i have to call it a day before i worked out what range is needed to be I hope this help you or someone else find the solution to this or just teach me i am doing it wrong for a vaild reason.

If you have further questions please ask i will get back as soon as i can.

Expand  

biome.generateFeatures (GenationStage.Decoration.UNDERGROUND_ORES, Feature.ORE.withConfiguration).withPlacement();
If you put config in 'Placement', you will get an error.

I want to fix it

Posted
  On 10/23/2020 at 3:46 AM, myounge said:

you will get an error

Expand  

And what's the error?

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted
  On 10/21/2020 at 10:18 PM, ChampionAsh5357 said:

Problematic Code 11. If you would like example implementations, look at the Features class. You will notice that there are some helper methods for placements as there can be multiple assigned to the same feature. Therefore, you can have a placement that handles the amount generate, the spread across the chunk, the height level in the chunk, etc. Do note that their order is important.

 

Second, do not use the above tutorial as a reference. It's outdated and uses terrible practices. It's better to just ask questions and infer from your own knowledge of Java than to follow someone else line by line.

Expand  


Hey Champion,

Thanks for the help so far i been looking into the Features class. Here is an example of ore_iron from that class. I am just struggling with how to implement this with the forge hook of BiomeloadingEvent is there as i wouldn't want to use biome.func_242427 / "addFeature" ?

public static final ConfiguredFeature<?, ?> field_243898_br = func_243968_a("ore_iron", Feature.ORE.withConfiguration(new OreFeatureConfig(OreFeatureConfig.FillerBlockType.field_241882_a, Features.States.field_244046_aj, 9)).func_242733_d(64).func_242728_a().func_242731_b(20));
Posted

Biomes are final classes now. The event hooks into the construction process of the biomes and hijacks it's creation allowing for extra entries or fields in the builders to be set. So, the builder contains the methods to add the features.

Also, you do not need to register the ConfiguredFeature. That's more for getting the JSON generated ones to grab the feature for the specific biome.

Finally, Problematic Code 1. You cannot be certain that the feature is present when constructing a static version of ConfiguredFeature. If your class is loaded before the Features are registered, then it will be problematic. This is not to mention the registries might be frozen at that point. However, this is irrelevant as you do not need to register it. This is just for future case.

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • ⚠️ DON'T CLICK THIS LINK OR ANYTHING RELATED TO THIS, IT HAS MALWARE IN THE LINK AND IT'S LIKELY A SCAM. ⚠️
    • ⚠️ DON'T CLICK THIS LINK OR ANYTHING RELATED TO THIS, IT HAS MALWARE IN THE LINK AND IT'S LIKELY A SCAM. ⚠️
    • I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Digital Hack Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Digital Hack Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Digital Hack Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Digital Hack Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. Contact : Whats...App : +.1 .4 7.4.3 5.3.7 7..1.9 Website : https://       digitalhackrecovery.com     Mail:            digitalhackrecovery         @techie.       com 
    • I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Digital Hack Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Digital Hack Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. I fight fires for a living, it's in my blood as a volunteer firefighter. But nothing could have prepared me for the fire that almost reduced my family's future to ashes. I had secretly accumulated $150,000 worth of Bitcoin over the years, intending to lock up my children's education and provide my wife with some leeway from our constant shift-work life. That was until a phishing attack struck me while I was out fighting a wildfire. The call had been on a hot afternoon. We were dashing to contain wildfires tearing across parched scrub lands. At such frantic moments, my phone pulsed with a security alert message from what looked like my Bitcoin wallet operator. Drenched with sweat, fatigue, and hyper adrenaline, I had clicked on the link and input my log-ins without questioning anything. I was tricked by hackers during my most vulnerable time. Hours later, returning to the station, I emptied my wallet. The harsh reality hit me with more force than any fire could ever have. My carefully saved safety net had vanished. My heart beat faster than the sirens. I felt as though I had failed my family. I explained my terror of burgers at our favorite local diner that evening to my friend. He leaned in close and whispered a single word: Digital Hack Recovery. He swore by their effectiveness, stating they worked miracles when his cousin had crypto stolen from him in a scam. I was skeptical old-school and desperate, so I called them. From the first call, their team treated me like family. They didn't only view figures; they viewed a husband and a father attempting to rectify a horrific error. They labored day and night, following stolen money through blockchain transactions like l detectives. Progress was made every day, translating intricate tech into fireman-speak. Ten days later, I got the call. “We recovered your Bitcoin.” I cried. Right there in the station, surrounded by smoke-stained gear, I let it all out. Relief. Gratitude. Hope they don't stop there. Knowing I worked in emergency services, Digital Hack Recovery offered to run an online security workshop for my entire fire department. They turned my disaster into a lesson that safeguarded my team. These folks don’t just recover wallets; they rebuild lives. They rebuilt mine. Contact : Wh.ats.Ap.p : +1 .4 .7  4 3. 5  3  .7 7.1.9 Website : https://     digitalhackrecovery.   com Mail:       digitalhackrecovery     @         techie.                     com  
    • Ran it one more time just to check, and there's no errors this time on the log??? Log : https://mclo.gs/LnuaAiu I tried allocating more memory to the modpack, around 8000MB and it's still the same; stopping at "LOAD_REGISTRIES". Are some of the mods clashing, maybe? I have no clue what to do LOL
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

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