Titles basically says it. 1.8 has made modding a pain therefore most modders are staying on 1.7. Without the community all moving on to 1.8 i'm undecided whether I should bother spending time all that time converting everything to new format.
Honestly, that is completely up to you. The big reason that all the community has not all moved to 1.8, is that 1.8 was a huge change to many core mechanics to minecraft. If 1.7 was any indication, which also was a huge change with the removal of preassigned ID values, and eventually, all active modders will convert their mod to the new format, or do a complete redesign under the new format.
I am a new modder, I am currently working on a mod in 1.8. Though I did first start in 1.7.10, and there are plenty of differences. I alot of stuff I learned in 1.7.10 worked in 1.8, I just had to adjust to what has changed, and modify my code to work with the new version.
I'd say that most modders are now moving on to 1.8, or actually maintaining both. A lot of tutorials are updated already for 1.8, and most mod download sites show a lot under 1.8.
As mentioned above, 1.7.10 was also a big change and a lot of people then tried to stick with 1.6.4 but ultimately 1.7.10 got a lot of momentum.
Also I found that some mods take a while to develop and perfect and you need to really think about what people will be using a year from now, not what they're using right now.
The Meaning of Life, the Universe, and Everything.
Join Date:
4/3/2015
Posts:
54
Member Details
Well, depends on something, such as if you're trying to make mods for the community or yourself. If your'e wanting to play 1.8 and have mods, than obviously port to 1.8. 1.8 isn't actually so horrible, most everything I've done in it was either from updating other pieces of code, or looking at source and it was pretty easy, time consuming, but easy usually. Though one thing to keep in mind, most "tutorials" for 1.8 are most likely how to add a block / item, and that alone. On the bright side is that I can help you with a lot of stuff for 1.8 if you do choose to go that way.
If you're new to Java and/or programming, go with 1.7.10 as there are more guides and example sourcecode out there. Trade off is that you'll have a pain updating to 1.8 or later since so much has changed, but you can worry about that once you get more experienced with Java (and/or guides and such are updated).
I'm not new to java or modding, my main thought is that I want my mod to be used with others. Hence why i would make it for 1.7, but thinking about it my mod is so early on that by the time its at a level of release people will have moved onto 1.8
I'm not new to java or modding, my main thought is that I want my mod to be used with others. Hence why i would make it for 1.7, but thinking about it my mod is so early on that by the time its at a level of release people will have moved onto 1.8
Most modders tend to develop for one or both of the two latest major versions of Minecraft(1.7.10 and 1.8 at the moment), once a new major version is out and the version of their preferred modloader for it is stable they move to the new latest two major versions. 1.9 is not going to be much different from 1.8 internally, so learning 1.8 is probably a good idea.
Most modders tend to develop for one or both of the two latest major versions of Minecraft(1.7.10 and 1.8 at the moment), once a new major version is out and the modloader version for it is stable they move to the new latest two major versions. 1.9 is not going to be much different from 1.8 internally, so learning 1.8 is probably a good idea.
Forge, not ModLoader. ML is dead and has been since 1.6.2.
Rollback Post to RevisionRollBack
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
I am aware of modloader's death, I was meaning all the loaders used today(Forge, LiteLoader, M3L in the future maybe).
Fair enough, but just be warned that saying modloader (similar to ModLoader) without a space is different to mod loader; someone may assume you mean Risu's ModLoader, rather than mod loaders in general.
Rollback Post to RevisionRollBack
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
Titles basically says it. 1.8 has made modding a pain therefore most modders are staying on 1.7. Without the community all moving on to 1.8 i'm undecided whether I should bother spending time all that time converting everything to new format.
Honestly, that is completely up to you. The big reason that all the community has not all moved to 1.8, is that 1.8 was a huge change to many core mechanics to minecraft. If 1.7 was any indication, which also was a huge change with the removal of preassigned ID values, and eventually, all active modders will convert their mod to the new format, or do a complete redesign under the new format.
I am a new modder, I am currently working on a mod in 1.8. Though I did first start in 1.7.10, and there are plenty of differences. I alot of stuff I learned in 1.7.10 worked in 1.8, I just had to adjust to what has changed, and modify my code to work with the new version.
I'd say that most modders are now moving on to 1.8, or actually maintaining both. A lot of tutorials are updated already for 1.8, and most mod download sites show a lot under 1.8.
As mentioned above, 1.7.10 was also a big change and a lot of people then tried to stick with 1.6.4 but ultimately 1.7.10 got a lot of momentum.
Also I found that some mods take a while to develop and perfect and you need to really think about what people will be using a year from now, not what they're using right now.
Well, depends on something, such as if you're trying to make mods for the community or yourself. If your'e wanting to play 1.8 and have mods, than obviously port to 1.8. 1.8 isn't actually so horrible, most everything I've done in it was either from updating other pieces of code, or looking at source and it was pretty easy, time consuming, but easy usually. Though one thing to keep in mind, most "tutorials" for 1.8 are most likely how to add a block / item, and that alone. On the bright side is that I can help you with a lot of stuff for 1.8 if you do choose to go that way.
If you're new to Java and/or programming, go with 1.7.10 as there are more guides and example sourcecode out there. Trade off is that you'll have a pain updating to 1.8 or later since so much has changed, but you can worry about that once you get more experienced with Java (and/or guides and such are updated).
I'm not new to java or modding, my main thought is that I want my mod to be used with others. Hence why i would make it for 1.7, but thinking about it my mod is so early on that by the time its at a level of release people will have moved onto 1.8
Most modders tend to develop for one or both of the two latest major versions of Minecraft(1.7.10 and 1.8 at the moment), once a new major version is out and the version of their preferred modloader for it is stable they move to the new latest two major versions. 1.9 is not going to be much different from 1.8 internally, so learning 1.8 is probably a good idea.
Please don't PM me asking for help, I will just redirect you to the appropriate forum, where there are others who are far more skilled than me.
This is not the signature you are looking for.
Banners and such things
Forge, not ModLoader. ML is dead and has been since 1.6.2.
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
My Github page.
The entire Minecraft shader development community now has its own Discord server! Feel free to join and chat with all the developers!
I am aware of modloader's death, I was meaning all the loaders used today(Forge, LiteLoader, M3L in the future maybe).
Please don't PM me asking for help, I will just redirect you to the appropriate forum, where there are others who are far more skilled than me.
This is not the signature you are looking for.
Banners and such things
Fair enough, but just be warned that saying modloader (similar to ModLoader) without a space is different to mod loader; someone may assume you mean Risu's ModLoader, rather than mod loaders in general.
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
My Github page.
The entire Minecraft shader development community now has its own Discord server! Feel free to join and chat with all the developers!
Technically speaking we're talking about API's anyway, the "loader" part is 90% transparent to us