It's up to you, but I suggest you start with java, because it's the underlying language of Minecraft and Forge, and you'll find the most documentation for it.
To be FAR less lmgfy, I will say that you don't need to really know java per se. The more technical the mod, the more intense your coding ability must be. I haven't written in C++ since undergrad (graduated 2004), but I code scripts regularly in Matlab (not a full fledged language but w/e). After watching several tutorials and coding along with them I'm writing a mod implementing new tools, armor, and materials - all with recipes and creative tabs and the whole nine yards. Whenever I brain fart on what to do next I can sometimes pick up the slack by googling (e.g., I had to initialize a List<String> so I googled "initialize List<String> in java").
Bottom line you need to be able to think analytically about the code (I'm a mathematics professor) and I strongly suggest that you code along-side the tutorials rather than downloading their source code.
To be FAR less lmgfy, I will say that you don't need to really know java per se. The more technical the mod, the more intense your coding ability must be. I haven't written in C++ since undergrad (graduated 2004), but I code scripts regularly in Matlab (not a full fledged language but w/e). After watching several tutorials and coding along with them I'm writing a mod implementing new tools, armor, and materials - all with recipes and creative tabs and the whole nine yards. Whenever I brain fart on what to do next I can sometimes pick up the slack by googling (e.g., I had to initialize a List<String> so I googled "initialize List<String> in java").
Bottom line you need to be able to think analytically about the code (I'm a mathematics professor) and I strongly suggest that you code along-side the tutorials rather than downloading their source code.
I recommend to have a strong understanding of the Java language BEFORE attempting to code a mod. Lists and initialization are basic Java knowledge and you won't get very far without knowing that.
Personal suggestion is that you should be able to create a really simple game before doing a mod that has something more functional than a hopper.
And I don't mean purely in programming, but also planning, concept art, style design and coding discipline in general.
It may sound a little bit overkill but it really helps when you get to actually coding as you will be able to concentrate just on that and not in 20 design and feature mechanic decisions.
Rollback Post to RevisionRollBack
Not doing mc modding that much anymore because I am making a full blown game that does not have limitations that mc has. (rip Magiology for now)
I may come back if MC fixes it's rendering pipeline.
Im getting different comments and its just a big mess of random things I dont know what to do.
Can someone try to explain what I should do?
Everyone has learnt to mod in different ways, and have come from different backgrounds with varying knowledge of Java and programming in general, so you're going to get lots of different responses on what they prefer.
I personally learnt Java at university and had good enough technical skills to watch some modding tutorials and picked up modding reasonably quickly. Funny enough, I ended up making a game in C# for university after I started modding, so I was able to take my modding experience into making the game. So that experience can go both ways.
I think you should find your own way to learn Java and work on a small project which challenges you. Once you feel you know enough Java, try some Forge modding tutorials (like some from this thread here) and go from there
Or you can get/take a source code from other modders and all you have to do is read them and understand it. If you fail to understand a specific part
of that code, you can always use google to search for it. Some people like this method and I am one of them.
Rollback Post to RevisionRollBack
If I am helpful to you in my replies, you can give thanks to me if you want to. It makes me feel like I helped a person in need. You can do that by clicking the upvote button in my comments.
Or you can get/take a source code from other modders and all you have to do is read them and understand it. If you fail to understand a specific part
of that code, you can always use google to search for it. Some people like this method and I am one of them.
That's fine if you already know Java. Looking at other mod's source code is something I do when I need to know how to do something specific, that I know another mod already does something similar. But you can't learn to mod from this... you're just copying code with no idea why you're using it then. And you're at the danger of doing something complex that a mod author does which isn't necessary - in the beginning, you need to go through tutorials to understand the basics, and find your own way of making a mod.
Well for a starter, even though I haven't learned java yet when I was learning, I just read the source codes from other authors. Understanding how they work is much easier compare to listening to someone who is in youtube trying to explain. Plus there are some instance wherein there are no tutorials of that particular things you want to do in your mod in which you will rely on other source codes of the author to help you. Understanding java has never been really much hard for me but I don't know when it comes to other people.
Rollback Post to RevisionRollBack
If I am helpful to you in my replies, you can give thanks to me if you want to. It makes me feel like I helped a person in need. You can do that by clicking the upvote button in my comments.
I don't know what everyone else is saying, but all I'm gonna say is to practice, all you need to know is that the language is Java. There are countlessamounts of tutorials out there on starting to program Minecraft mods. The only differences are the Minecraft versions. Just begin coding, it'll be hard and you won't understand it but neither did the rest of us. When I started programming Minecraft mods, I didn't know a single thing about Java, now I'm making games, programs, and I can code Java in my sleep. If it weren't the hours and hours I stressed over where the equals sign in the program goes, I wouldn't have known how well to code.
TL;DR: Just practice, practice, practice. Oh, and practice.
I don't know what everyone else is saying, but all I'm gonna say is to practice, all you need to know is that the language is Java. There are countlessamounts of tutorials out there on starting to program Minecraft mods. The only differences are the Minecraft versions. Just begin coding, it'll be hard and you won't understand it but neither did the rest of us. When I started programming Minecraft mods, I didn't know a single thing about Java, now I'm making games, programs, and I can code Java in my sleep. If it weren't the hours and hours I stressed over where the equals sign in the program goes, I wouldn't have known how well to code.
TL;DR: Just practice, practice, practice. Oh, and practice.
You're not meant to unless you know what you're doing and you're allowed to. What they're referring to is how a lot of modders tend to keep their mods open source, and so you can view the code online wherever it's hosted (normally on GitHub). A link to the site will normally be located on the mod's project page.
You're not meant to unless you know what you're doing and you're allowed to. What they're referring to is how a lot of modders tend to keep their mods open source, and so you can view the code online wherever it's hosted (normally on GitHub). A link to the site will normally be located on the mod's project page.
But if its open source, I should be allowed right?
But if its open source, I should be allowed right?
Not necessarily. You still need to abide by any licenses they may have in the repository. There will most likely be a main one in the root directory, and they may also state different licenses for separate files (which will be located at the top within the file) I believe. Although the per file thing is normally rare and only for specific things, but may still happen.
Not necessarily. You still need to abide by any licenses they may have in the repository. There will most likely be a main one in the root directory, and they may also state different licenses for separate files (which will be located at the top within the file) I believe. Although the per file thing is normally rare and only for specific things, but may still happen.
I want to learn how to create mods, so I wonder what I need to learn the language mods are written in?
I don't have knowledge about anything related to coding, except that I know a few things, but its nothing to help me.
So mods are written in Java. Thanks
Or Scala...
Or kotlin.
It's up to you, but I suggest you start with java, because it's the underlying language of Minecraft and Forge, and you'll find the most documentation for it.
To be FAR less lmgfy, I will say that you don't need to really know java per se. The more technical the mod, the more intense your coding ability must be. I haven't written in C++ since undergrad (graduated 2004), but I code scripts regularly in Matlab (not a full fledged language but w/e). After watching several tutorials and coding along with them I'm writing a mod implementing new tools, armor, and materials - all with recipes and creative tabs and the whole nine yards. Whenever I brain fart on what to do next I can sometimes pick up the slack by googling (e.g., I had to initialize a List<String> so I googled "initialize List<String> in java").
Bottom line you need to be able to think analytically about the code (I'm a mathematics professor) and I strongly suggest that you code along-side the tutorials rather than downloading their source code.
Word.
You did! because I googled and found this forum!
I recommend to have a strong understanding of the Java language BEFORE attempting to code a mod. Lists and initialization are basic Java knowledge and you won't get very far without knowing that.
My plan for learning code mods is first to know Java very good. Thanks for your support.
Personal suggestion is that you should be able to create a really simple game before doing a mod that has something more functional than a hopper.
And I don't mean purely in programming, but also planning, concept art, style design and coding discipline in general.
It may sound a little bit overkill but it really helps when you get to actually coding as you will be able to concentrate just on that and not in 20 design and feature mechanic decisions.
Not doing mc modding that much anymore because I am making a full blown game that does not have limitations that mc has. (rip Magiology for now)
I may come back if MC fixes it's rendering pipeline.
I am confused right now.
Im getting different comments and its just a big mess of random things I dont know what to do.
Can someone try to explain what I should do?
Everyone has learnt to mod in different ways, and have come from different backgrounds with varying knowledge of Java and programming in general, so you're going to get lots of different responses on what they prefer.
I personally learnt Java at university and had good enough technical skills to watch some modding tutorials and picked up modding reasonably quickly. Funny enough, I ended up making a game in C# for university after I started modding, so I was able to take my modding experience into making the game. So that experience can go both ways.
I think you should find your own way to learn Java and work on a small project which challenges you. Once you feel you know enough Java, try some Forge modding tutorials (like some from this thread here) and go from there
Or you can get/take a source code from other modders and all you have to do is read them and understand it. If you fail to understand a specific part
of that code, you can always use google to search for it. Some people like this method and I am one of them.
If I am helpful to you in my replies, you can give thanks to me if you want to. It makes me feel like I helped a person in need. You can do that by clicking the upvote button in my comments.
That's fine if you already know Java. Looking at other mod's source code is something I do when I need to know how to do something specific, that I know another mod already does something similar. But you can't learn to mod from this... you're just copying code with no idea why you're using it then. And you're at the danger of doing something complex that a mod author does which isn't necessary - in the beginning, you need to go through tutorials to understand the basics, and find your own way of making a mod.
Well for a starter, even though I haven't learned java yet when I was learning, I just read the source codes from other authors. Understanding how they work is much easier compare to listening to someone who is in youtube trying to explain. Plus there are some instance wherein there are no tutorials of that particular things you want to do in your mod in which you will rely on other source codes of the author to help you. Understanding java has never been really much hard for me but I don't know when it comes to other people.
If I am helpful to you in my replies, you can give thanks to me if you want to. It makes me feel like I helped a person in need. You can do that by clicking the upvote button in my comments.
I don't know what everyone else is saying, but all I'm gonna say is to practice, all you need to know is that the language is Java. There are countless amounts of tutorials out there on starting to program Minecraft mods. The only differences are the Minecraft versions. Just begin coding, it'll be hard and you won't understand it but neither did the rest of us. When I started programming Minecraft mods, I didn't know a single thing about Java, now I'm making games, programs, and I can code Java in my sleep. If it weren't the hours and hours I stressed over where the equals sign in the program goes, I wouldn't have known how well to code.
TL;DR: Just practice, practice, practice. Oh, and practice.
Hello!
How do I extract code?
I knew this comment would pop up
You're not meant to unless you know what you're doing and you're allowed to. What they're referring to is how a lot of modders tend to keep their mods open source, and so you can view the code online wherever it's hosted (normally on GitHub). A link to the site will normally be located on the mod's project page.
But if its open source, I should be allowed right?
Not necessarily. You still need to abide by any licenses they may have in the repository. There will most likely be a main one in the root directory, and they may also state different licenses for separate files (which will be located at the top within the file) I believe. Although the per file thing is normally rare and only for specific things, but may still happen.
So how do I open one?