1.20 Minecraft Forge Modding Tutorial - Blocks

In this video, I show you how to create our first block and create its loot table!
In the next video, we will create a creative tab and add our items to it as well as how you can add your items to vanilla creative tabs too. Remember, if you have any problems, please join the discord that is linked below!
Links:
Patreon: / turtywurty
Discord: / discord
Github: github.com/DaRealTurtyWurty/1...
Learn Java Links:
java-programming.mooc.fi/
www.codecademy.com/learn/lear...
docs.oracle.com/javase/tutorial/
Java Support Server:
/ discord
Misode (Loot table website):
misode.github.io/
Chapters:
0:00 - Intro
0:25 - Registry class
0:50 - DeferredRegister
1:30 - RegistryObject
2:45 - Block Properties
8:45 - Registering the registry
10:00 - Registering a BlockItem
12:30 - Blockstates
16:00 - Block Model
20:00 - Texture
20:35 - Translation files
21:10 - Item Model
22:50 - Data directory
23:15 - Loot tables
28:40 - Harvest Level/Tool Tags
34:00 - Testing
36:50 - Outro

[@Diremon2]

Wow, this guide is phenomenal! It's pretty rare to find a guide that actually takes the time to explain the "why?" and get more in-depth with how each part works. I greatly appreciate this!

[@TurtyWurty]

Glad you enjoyed it! I purposely try to take the time to explain how things work, and that's why the videos are sometimes longer than others you might find. I think its very important to understand the different concepts you are using rather than just using them without knowing.

[@FuzeEdits]

Loving the series so far keep it up.

[@coucoul38]

This is just like datapacks, but beefed up :D

[@fokinatorr_894]

Everything works fine except the texture of block isn't rednering for some reason

[@legoaggelos2722]

That intro is the best thing ever

[@logplug794]

Perfectly good video, keep going! In all of the videos you are trying to make everything detailed to be easy to understand, you make hard things much easier... But I still find weird facts about netherite, gold and diamond, iron, stone, wood tools, why some of them belong to minecraft/tags and some of them to forge/tags while all of them are completely vanilla features...

[@elnoob_master4244]

¡¡Awesome!! I'm waiting for the "add a mob into minecraft" tutorial jsjsjsj I've been creating blockbench entities and I'm excited to add them into my minecraft

[@TurtyWurty]

Entity Tutorial is definitely coming soon. A few more simpler things first and then it'll be out.

[@thederpykrafter]

will you please make a video on adding items to existing loot tables?

[@diegolopezesteban615]

I love your vídeos, pelase do more tutorials 😆

[@TurtyWurty]

Currently, I plan to release every Monday and Thursday at 5:50pm UTC. I can't guarantee that this schedule will stick, because honestly I find it very hard to stick to schedules. But I will try my best to keep this going as long as I can! 🙂

[@drakhooficial]

man awesome tutorial, but i think you should disable the Flatten Packages and modules option, it gets a little confusing where you are doing everything

[@luigiplayer1547]

hi, I want to change the destroy time of oak logs but its becoming super hard to achieve what do you think i can do?

[@disgust_jpeg1871]

holy goat

[@SrFlowzer]

I'm starting in this modding thing, and there are several videos on how to do the same things in different versions, does it vary a lot from one version to another? And if so, what can vary?

[@TurtyWurty]

Anything can change from version to version. Anything from how you register blocks to adding creative tabs to how you add biomes. Literally anything can change. Generally, you should follow tutorials for the version you are trying to use if possible. If that's not possible, then you can look at an older version, but the older you go, the harder it will be. For example trying to use anything pre-1.16.5 for 1.20 would be an insane task. Anything pre-1.12 and you would only be able to utilize a concept, not a single line of the code would work. You'll find that 1.19.3/4 is mostly the same as 1.20/1.20.1, so if you can find something in 1.19.3/4, then that will *probably* work for 1.20.

[@blinkybob6643]

Do you have any plans on making a tutorial about making blocks the NON- differed way? I can not figured out how to do it

[@TurtyWurty]

There is no reason to ever do that. So no.

[@adamtil2187]

Awesome tutorial, but how do I get two blocks to be mineable? I can't do more than two, that's what the error was saying.

[@professorpig1387]

You gotta do one on trees bro, I can't figure it out

[@legoaggelos2722]

Do you prefer 1.12.2 modding or 1.16/1.17/1.18/1.19/1.20 modding ?(sry for the random question)

[@TurtyWurty]

At the time, 1.12. But in hindsight, definitely modern versions. 1.12 just did everything really poorly and forge was lacking a lot of the crucial things that I use today. It was just a lot more work for almost everything in 1.12, and the only reason I think I liked it more back then would be because it was when I was just starting out, figuring out how to do everything - which is always a fun challenge. The pure fact of modern versions having the DeferredRegistry system is a big enough thing to be happy about tbh. Also things like block entities, GUIs and Menus are way easier now. Lots of stuff being data-orientated is also a massive plus, it makes a lot of world gen for example much much easier to do.

[@legoaggelos2722]

Ok.

[@Blackconnection-]

For some reason I don't get to make the mineables work. No matter what kind of pickaxe I configure, the block is always mineable with all pickaxes. Any idea why? Edit: I tested mining by hand aswell and to make it short: Currently I can mine the block with everything unless I copied a vanilla block property on block registration (see aswer to gustroismille7726).

[@gus3000spam]

- check for any typo in your filenames - check that your needs_iron_tool.json is in minecraft.tags.blocks, not in mineable

[@Blackconnection-]

@@gus3000spam Thanks for the response. Actually I figured something out. I had a typo within my needs_iron_tool.json. The block was written wrong as value. But even after changing that (and going through the whole configuration again) it did not work. But what I figured out was, unlike in the tutorial, I did not apply the copy of the diamonds block behaviour. Once I added that, it worked for me aswell. But meaning, for now, this datapacks which should override the tool block behaviour don't seem to work. Or did you managed to add a block wth own properties instead of making a copy of an existing ore? (Code: BlockBehaviour.Properties.copy(Blocks.DIAMOND_BLOCK when registering the your block). Addition to take into account: The data packs like "needs_iron_tool.json" or "needs_stone_tool.json" etc. seem only to work if you are using a vanilla block property for your block. If you don't used it, it won't work. Additionally, once a vanilla block property is used, the added "needs_stone_tool.json" for example overrides the property of the block mining behaviour. So I assume, you don't have any initial information without adding a block property of a vanilla block that you can override and therefor resulting in a block that is mineable by everything.

[@radekdocekal3238]

I had the same issue. But I found out there must be file "blocks eeds_iron_tool.json" and also file "blocks\mineable\pickaxe.json". Both files are mandatory.