Ugdhar

I just downloaded it, so the problem is definitely with your computer/internet. Can you post screenshots or something so we can see exactly what the error is? And just to make sure, be sure you are only downloading from files.minecraftforge.net and not somewhere else.

Have you tried anything yet? I haven't tried doing this myself recently, but I would start looking at the vanilla code. Items (including tools) are registered in the Items class (net.minecraft.item package), which should get you started following the code path back to how vanilla tools are made. If what you try doesn't work, come back, post a link to your code (a working github repo is the hands down best way to share your code to get help), as well as logs of your current run (if it runs but doesn't work right or throws errors in the log while running)

I updated my build.gradle forge/mappings version yesterday, this is what my line looks like: And it worked no problemo. Good luck!

Recipes go in data, not assets Same for loot tables, and I forget if there's anything else, check the vanilla stuff and see what they put in there edit: dug this link out, has some good info on a lot of the changes since 1.12: https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a

Experience, really. The longer you've worked with programming, the easier it becomes to follow the paths of code, to guess where to start looking, and of course understanding the code that you are looking at. When I run into something I don't know/can't immediately figure out, I search google and/or here, using class/method names, full/partial error messages that I may get. Sometimes just typing in "minecraft forge <what i want to do>" will yield results. It's pretty amazing the amount of questions that get asked on here that are literally less than 2 pages of google/forums searching away! And when that doesn't work, coming here with a link to code, full logs, and a decent description of what has been tried and what the end goal is, will typically get answers. As long as you aren't asking basic Java questions, and it's current forge related stuff, people here are pretty helpful when you ask the right questions.

Start a new thread, and post what you're getting at the console, or perhaps a screenshot.

You should start your own thread instead of posting in another thread. That being said, I run gradlew eclipse and then gradlew genEclipseRuns (both commands are needed) from a cmdline/powershell before importing existing gradle project into my eclipse workspace. I've run into issues where the sources do not get attached to the jars for some reason, but running the setup tasks a second time magically makes them appear for me.

If you are talking about on twitch, there is a dropdown for "game version" when you are browsing modpacks, so you can pick 1.14.4 or 1.15.2. And there's nothing that says people can't USE older versions. You just won't get support here for it. Same as if you installed Windows 95 or MS-DOS on a computer, if you cried to Microsoft that it didn't work, and it should because you found software on some website for it, they'd tell you to pound sand and buy Windows 10. Also, constantly swearing doesn't make you heard, it makes you look like a child. Chill out.

I'll be honest, I have not done a lot with blockstates, or even tried the forge blockstates. For the simple blocks I made while messing around with stuff, I essentially just copied the way vanilla did it. Hopefully someone else can point you in the right direction. If you want to check out the vanilla blockstates, I found I can access them by opening .minecraft/versions/1.15.2.jar as a zipfile.

Just for grins what if you make your package name all lowercase?

Well, there's definitely something broken, I honestly am not sure what considering everything looks like it should. I don't use intellij so I don't know if there's something in the project setup that could be broken. Double check for invisble/hidden spaces in package names maybe? If it were me, I would probably start with a fresh MDK, and drop my src folder into it and do the setup from scratch.

Yes, always new logs, always, no matter how little you change.

If you changed your modid, it is still trying to use your old hm mod id.

Can you post updated logs too please?

Nevermind, you posted another screenshot lol

We need more information. Where did you get this base mod on github? Could you post a link to it so we know where you're starting from? What are you trying to achieve? Do you know Java? (if not, this is where you have to start)

Show screenshots of your project setup including package/file names

Is that installer jar in your mods folder? If it is, remove it. Also always post new logs when you get a new error

Almost, that looks like an old archived one. See if you can find one that just says "debug", or "debug.log", it won't be a zipped up file. Either post it to something like a github gist and post the link here, or paste it between spoiler tags (the eyeball button)

In the logs folder in your .minecraft game folder (or another folder if you changed it in the Installation settings)

You would first need to run the forge installer for the version you are planning to use. Then make an Installation in the minecraft launcher, I would point it to a new game folder (i.e. .minecraft-NEW or something). Make sure you are selecting the forge game version. Create (or once you run once it will create it for you) a mods folder in this folder, and download mods for the appropriate version from curseforge. When you are trying, what exactly are you doing, and what's the exact problem? Details, error messages, and screenshots are helpful P.S: I don't use a mac, but overall the process is largely the same regardless of OS.

Code - This can just be an instance of the Block class if your block doesn't do anything special. Texture Blockstate Model Loot Table You will also want an Item model (no blockstate there!), and register a BlockItem, if the block is able to go in your inventory. And as far as I can tell, these do look similar to 1.12, at least for the most simple of blocks.

1.12 is no longer supported due to age. 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.

1.12 is no longer supported due to age. 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.