Fixing Our Command Properly - Fabric Modding Minecraft 1.21.1 | #38

[@kosmosskibidi]

underrated af, keep it up!

[@TheMentorCodeLab]

Thanks a lot. Comments like this are the real motivation. I just hope people help me with introducing the channel to others soon lol

[@wChris_]

Why are you suing the Blocks name, if you could use the Block itself directly? so instead of "stone" use Blocks.STONE. Then there is no need to get the Translation Key, which may not always be the same as the blocks name.

[@TheMentorCodeLab]

I Agree that translation key was not the best approach and if you check the final code on repository, it is changed and no longer is using the translation key. Also, it's possible to use Blocks class directly, it's totally a valid solution. However, what if you would want to open the doors for mod pack developers utilizing config systems. Specially for config systems, you can't utilize the classes and their attributes directly anymore. What I'm trying to do in this video, is to show different alternative ways of handling what is registered in the Registry system. The final application is up to viewers because it will change case by case based on people's needs. For example, another approach could be utilizing tags and add every block into a tag and this way mod pack developers would be able to handle things if they need. As I said, the aim here is to show people different ways of doing the same thing.