Ugdhar

Yes, (well, they don't HAVE to) but you are creating it twice as diesieben mentioned, once in the items registry event, and then once in your moditems. I was pointing out the one in ModItems you are using new Item() instead of new BlockItem(), but honestly you should probably just remove that one entirely, since you already create your blockitems in a loop in the item registry event. You should take a step back, I notice you have a LOT of code for having a broken block, which leads me to believe you've been doing a lot of copy & pasting. If you must copy & paste, only do small pieces of code at a time, to make sure they work, and to attempt to understand them as much as possible before moving on.

Do you have Java? If so, then you should google jarfix and download/run it to fix your jar file associations. If not, download java 8 hotspot from https://adoptopenjdk.net/

I'm not sure, but you make your blockitem (in ModItems) an Item, and not a BlockItem. Could that be the issue?

https://mcforge.readthedocs.io/en/latest/gettingstarted/structuring/

1. change your modid, make it longer and it cannot contain capital letters 2. all those places that should be your modid, make them be your modid, instead of random things that are similar to your modid.

Your modid still contains capital letters. Also, you aren't using the same modid throughout your mods.toml and code. in one place in another and another

Screenshots are a terrible way to share code, you should share using a github repo, or using the code tags (the <> above when you post a msg) That being said, I can just see enough from the screenshots to see you still have capital letters in your modid.

Your assets folder needs to be assets/MODID you have assets/mlm but your modid is minerslifemod *edit: make sure when you make changes, to push updated code, as well as post updated logs.

The json has nothing to do with the error. (*edit: besides the modid being wrong because it's caps) The error is because he's using caps in his modid. He showed a blockstate, and you posted a model, they're 2 different things for 2 different purposes.

I would not use a ! in your file paths. Try changing that, and see if it makes a difference.

I would use the latest MDK, not the recommended, there is new improvements and newer mappings in the latest. Please post the debug.log

Which version of Java did you get? You want Java 8. Also, it looks like you may have gotten 32 bit Java, and you definitely want 64 bit.

Please provide details, as well as your debug.log

https://gist.github.com/williewillus/30d7e3f775fe93c503bddf054ef3f93e has some info on 1.15 changes

1.12 is no longer supported due to age. Please update to a modern version (1.14.4/1.15.2) to receive support. More information on supported versions can be found in the LTS link at the top of every page.

I would guess that there is an adblocker or antivirus stopping the page from loading. In the list of all versions, there should be a small "i" to give you a direct download link if you must.

1.12 is no longer supported due to age. Please update to a modern version (1.14.4/1.15.2) to receive support. More information on supported versions can be found in the LTS link at the top of every page.

I couldn't tell you, but that is irrelevant. It has been made clear on this site that only the current and previous version are supported, and threads for outdated versions get locked by moderators, as they clutter up the forums for the people looking for help with the current versions. You're free to continue using outdated versions (much as someone could install and use Windows XP on their computer), but you will not receive support here for it (much like if you asked Microsoft for support for Windows XP; they would tell you to update). *edit: not to mention staying in the past, you miss out on new stuff, for example, being able to use VSCode out of the box. . . .

1.12 is no longer supported due to age. Please update to a modern version (1.14.4/1.15.2) to receive support. More information on supported versions can be found in the LTS link at the top of every page.

1.12.2 is no longer supported due to age. Please update to a modern version to receive support. More information can be found in the LTS link at the top of every page.

First, use the latest MDK, not recommended, there are a ton of bugfixes and newer mappings in the latest. Second, make sure you scan all the way through your logs. This is something you should always do when debugging code and stuff, it is not specific to forge modding. The issue is explained right there for you:

Please post a debug.log from a supported (1.14.4/1.15.2) version where the crash occurs.

Please show a screenshot of your mods folder, including the full address bar at the top.The debug.log you posted does not show any mods loading, so I'm guessing that they must be in the wrong folder.

What version are you using? I thought there was a gradle task to generate vscode runs.

Also, do you own kidkoder.net? If not, you should probably change your package name.