Ugdhar

This is because Twilight Forest, at least as far as curseforge is concerned, is not available for 1.16, so I'm guessing that whatever source you were looking at was either for an old version, or incomplete/in-progress. Sorry I don't have more help for you, I haven't messed with 1.16 that much, just started looking into it and tinkering with it. If I figure any dimension stuff out, or come across any decent references, I'll post back here for ya.

I think you mean subclass.

What have you tried? What is working/not working? I also know there are examples of this very thing if you search these forums, give it a go, you'll likely find your answer. And if it still doesn't work, post code, logs, and be verbose describing what is working/not working.

There does not appear to be a spoiler tag button in the forums editor anymore (it used to be a little eyeball button). Can this be put back? And at the very least, if not, how do you make one by hand? I don't get fancy with forum markup syntax, so I've got no clue.

Interesting, it used to be a little eyeball button at the top of where you edit a message, but it doesn't appear to be in the editor anymore. I guess you could try the quote or code tags, but I don't know if they collapse the same way spoiler does. Unfortunately I don't know how to add one inline by hand. Sounds like a good bug report for whoever works on the forums!

Before doing that, try as diesieben suggested and remove optifine, I didn't realize that was in there (one of the side effects of pasting your log directly into the post, too much scrolling down the page to catch everything).

I would try removing abnormals_core and see if that helps. Also, you should post logs on an external paste site, and link to them here, or at the very least use spoiler tags, to avoid a 10 mile long post.

What is causing that? Also, it's tough without being able to see the big picture, you really should put your project in a github repo and share the link here. A space, a comma that looks like a semicolon, a missing modid somewhere, all little things easilly missed, but potentially caught by a rubber duck debugging a github repo

That log doesn't look complete, post the entire debug.log file, it should have more information. *edit: also Is that the correct version for the version of Minecraft/Forge you're using?

Did you actually execute jarfix, or just download it? It must be executed in order to apply the fix. And are you sure you have java? If you open a command window, and type java -version does it say something? Also, instead of posting on a thread over a year old, you should create a new thread, your issue could be different even though it looks the same.

Nice job necroing a thread that's over 4 years old to complain lol

Even without a crash, there will still be a debug.log in the logs folder, post that to an external site (github gist, pastebin, etc) and post the link here so someone can check it out.

Don't copy it from the console, look in the logs folder in your project, there will be a debug.log in there that contains the information. Post it to an external site, like a github gist or something, and link back to it here, as it can be quite large/long.

You want to use the energy capability: https://mcforge.readthedocs.io/en/latest/datastorage/capabilities/ I haven't looked at capabilities in a while, so I'm not sure if the docs are up to date or not, but it should be enough to get you started!

Old versions are no longer supported on these forums:

1.12 is no longer supported due to age. Please update to a modern version to receive support. (I believe current/supported versions do not have ID limits) See the LTS link at the top of every page for more information on supported versions.

1.12 is no longer supported due to age. Please update to a modern version to receive support. See the LTS link at the top of every page for more information on supported versions.

Post the debug.log from the logs folder in a github gist or pastebin or something like that, and link to it here; someone will see it and be able to figure out what's going on.

There will be a log file generated by the server (even without a crash, it will be in the logs folder, probably called debug.log or latest.log); post that in a github gist or pastebin or something, and link to it here, someone will see it and probably know what's up.

Nope, it would be just debug.log, without any numbers in the name or the .gz at the end. If you are using Windows, it is possible the file will just be called "debug", and under the file type say it is a log file. Because Windows is awesome and hides file extensions by default. Also, please post logs to an external site (github gist is my personal favorite), and link to them here, as opposed to attaching files. Most people don't like downloading random compressed files off the internet.

Which parts are you not understanding? The explanation is very basic Java, and if you don't understand that, you are going to have a Very Bad Time trying to mod. Not trying to be mean, just stating facts. There isn't really a much easier way to explain what vemerion said without going to Java School (this isn't Java School, this is Forge School )

Post your debug.log it will explain why somewhere in there.

Here, this may help you if you're familiar with 1.12, as a LOT of stuff has changed since then. https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a

Look at vanilla resources in data/minecraft/tags/blocks for examples. Unfortunately I still haven't tinkered with data generators so I cannot tell you how they work, but they will generate the json for you via code so you do not have to write it by hand (which can be prone to typos/repetitiveness/etc)

You likely need to add leaves and logs tags jsons/datagens