Ugdhar

Looks like you're trying to setup ore generation in your constructor, which is before any registry stuff has happened, so your ore doesn't exist. Try moving ore generation setup into FMLCommonSetupEvent Also, you should update to 1.15.2, as 1.14.4 is going to be out of support once there is a RB for 1.16.x.

Double check your system environment variables for I think it's JAVA_OPTS or something like that that is setting -Xmx2G

If you're trying to follow a tutorial, use these: https://wiki.mcjty.eu/modding/index.php?title=YouTube-Tutorials They're the most up to date, and best laid out, and are the ones suggested if you ask about tutorials on the forge discord. McJty is also one of the few tutorial makers that doesn't force you to sit there and watch a video, as he has a text based version to go with them.

Positive, any perceived order after Blocks -> Items could change at any time. I've seen people that know what they're talking about (including Lex) say it a million times.

Just to make sure this fact is known, the only order of registration that you can rely on is Blocks -> Items -> Everything else, in a non-specified order. The order of any other registrations besides blocks and items is subject to change, even between different runs.

There are no updates for the 1.16.1 mappings currently. It is being worked on.

Have you looked at the DefaultBiomeFeatures class? It is in the net.minecraft.world.biome package. It contains methods such as addForestTrees and addOakAndSpruceTrees that you can look at to see how vanilla generates trees.

The official documentation is not meant to be a tutorial. It's more of a getting started and concepts guide. If you click the "Youtube tutorial step by step" link on that page you linked to, you'll get the txt version of the tutorials.

Can you run the eclipse gradle task?

The gradle project is still not setup, if you right-click on the project, select Gradle -> Refresh Gradle Project it should fix that. If it errors, try the gradlew --stop from the commandline in your project folder. If it gives errors after that, please post them so we can see what's up.

I would start with the MDK, because it looks like you haven't got a mods.toml in your resources anywhere. You are also not using any sort of useful package name. Using the MDK as it comes will start you out with a skeleton project you can edit to your needs. Once you've extracted the appropriate MDK files into a folder, import that folder into eclipse as an existing gradle project. It will do it's thing (if it doesn't, from the cmd prompt in your project folder, try gradlew --stop then refresh gradle projects) When that finishes, run the genEclipseRuns gradle task. Then you'll be ready to rock.

What would an official example look like? I mean, we can read the sourcecode. . .I don't think it gets more official than that. I've found tons and tons of examples searching the forums and google for what I was looking for, sometimes even finding stuff I didn't know about. And as long as it's a supported version, we are free to ask questions here and on the forge discord. The forge docs give all the information needed to get a workspace setup, and as far as the basics, everyone that's ever made (or tried making) a tutorial at least makes it to blocks and items I guess what I should ask is, what exactly are you looking for? And of course, the forge documentation is on github, so if you'd like something added/changed, you can make contributions/pull requests.

Hopefully you make it further than most tutorial makers, who give up after all they cover the same stuff everyone else does! Best of luck to you!

There's no manual, but you can look at the code of both forge stuff and vanilla MC stuff within your IDE. It is also searchable. Also, if you are unaware, definitely learn features of your IDE like looking up call hierarchy (will show places where the method/field is called from) and looking up type hierarchy (will show the tree of super/subclasses for the selected class). Things like this are invaluable.

Step 1: Learn Java Here are some links to help you get started Official documentation: https://docs.oracle.com/javase/tutorial/ Absolute basics with an interactive editor: https://www.codecademy.com/learn/learn-java Ongoing online course with assignments: https://java-programming.mooc.fi/ Once you have worked on learning Java for a few weeks, use the Docs link at the top of the forums here, and start from the Getting Started section.

You should elaborate on this, you will likely get a better response

It's easy, but also not so easy. Firstly, it's going to be tougher in 1.16.1 with so many srg names still. It made my eyes bleed enough that I gave up, and am waiting for new/better mappings, or the new system to come out so I can at least contribute while my eyes bleed. But the way the overworld does it is in net.minecraft.world.gen.layer the LayerUtil class sets it all up (this is done in the OverworldBiomeProvider constructor) Then the BiomeProvider requests the biome from the layer in its getNoiseBiome method. (it's fairly complicated how it generates the world, you'd have to read through the code, I'm slooooowly working on understanding how the vanilla layer worldgen works) You CAN just override getNoiseBiome in your custom BiomeProvider, and return biomes there however you'd like. There's a reason there aren't "tutorials" all over the internet for doing this, because it's not really simple, no matter how you slice it *edit: Annnnd I missed a few of the methods you were unsure of. That's what I get for trying to think first thing in the am lol. Anyhow, looking at vanilla overworld provider, func_230320_a_ returns a new instance of your BiomeProvider and func_230319_a_ returns a Codec for your BiomeProvider. I can't explain the whole Codec thing in too much detail, because it's still really new to me, but from what I understand it handles serialization/deserialization of data, looks like maybe settings in this case. In the vanilla OverworldBiomeProvider it is set up at the top of the class, maybe someone can explain it, or if you look at it you can implement it.

The client-extra.jar is the one with the loot tables and such, the second forge jar is the launcher I believe.

1.7.10 is over 6 years old, and no longer supported. Please update to a modern version to receive support. More information on supported versions can be found in the LTS link at the top of every page (there is also a link within that page explaining changes with the release of 1.16.1)

This is still being worked on, so even if you cobble something together, there's a good chance it would break in the coming days/weeks while a dimension registration setup is designed/implemented. At the moment, from what I understand, there is only 1 very busy person that has the ability to do mappings stuff, so best thing is to just be patient, and they'll get updated eventually. There is a new system in the works that should make it much easier to update mappings, but again, people working on this for free when they have time, so we have to be patient. As 1.16.1 is still being worked on quite a bit, bugs being found/fixed, etc., there's not a definitive list of changes yet, I'm sure once things settle down, there will be. If you want bleeding edge info and discussion on the new version, I would suggest visiting the forge discord and seeing what's being discussed there.

Look for NBTExplorer (search google, it's a program someone wrote, I think i found it on the minecraft forums), it will allow you to open nbt files, or folders containing more than one, and browse/search through them. I've only messed with it a little, bit it should be what you need to help you find your box if you can find it in the file, you can probably get the position of it as well. There may be an easier way, or a way with commands, but this isn't something I've had to do myself, so am unsure of the different ways of doing it.

That is super weird, there are no crashes in those logs, they look like a normal startup. Is there a crashlog file in your .minecraft folder? Maybe try and cause the crash again and repost logs?

Please post your debug.log, preferably to an external site, and link to it here. It should have more information about what is happening.

It takes the same parameters as the way it worked before, except instead of creating a new instance of the class via new, you use the static create method.

The forums are a little glitchy, they're working on it Just dbl check if your post is there before you hit submit again Yes, in the .minecraft\logs folder, it might just be called "debug", if you're on windows and have (by default) file extensions turned off. It might be large, so you will probably want/need to post it on an external site like a github gist or pastebin or something and link to it here.