I would go with 1.7.10 or 1.8 (experimental) as they are latestI am new to the mod creating system but know alot about mods and was wondering the advantages of midding in 1.5, 1.6.4, 1.7.2, 1.7.10, or even 1.8 I know there was something in 1.7 that people didn't like about for the nodding system
I wouldn't go with 1.8.I would go with 1.7.10 or 1.8 (experimental) as they are latest
Meh if he is starting now I doubt he will have something good by the time 1.8 becomes the new 1.7 without some helpI wouldn't go with 1.8.
The 1.8 forge builds are experimental, and there will definitely be at least a few more 1.8 Vanilla builds. I don't think it's really worth it until 1.8 becomes stable.Meh if he is starting now I doubt he will have something good by the time 1.8 becomes the new 1.7 without some help
Although, if he starts on any other version, he'll have a heck of a time porting to 1.8.The 1.8 forge builds are experimental, and there will definitely be at least a few more 1.8 Vanilla builds. I don't think it's really worth it until 1.8 becomes stable.
Hence why I suggested itAlthough, if he starts on any other version, he'll have a heck of a time porting to 1.8.
thanks this was my first thought but wasn't sure if 1.8 was possible yet so I might as well start with itHence why I suggested it
It is experimental so it may have a few bugs, but knowing Lex it shouldn't have major onesthanks this was my first thought but wasn't sure if 1.8 was possible yet so I might as well start with it
ForgeGradle exists for 1.6.4, but it's in v9.11.1.964 rather than v9.11.1.965 (don't ask me why).
based on your info I'll start my simple mods in 1.6 and as I get better quickly transverse to 1.8 when my builds get more complicated. This is so I'm ready for the versions ahead instead of getting to in depth with MCP so the GRADLE is easy to transition to.No point in trying to learn 1.8 yet. There's nothing really released and probably only a handful or two of people know the internal changes at this point, so you'd have a hard time getting any questions answered. I'm still trawling through it myself and only just now think I'm at a point where I could make babby's first API.
There's nothing particularly wrong with starting with 1.7, because you'll be familiarizing yourself with the Gradle build system, which I assume is here to stay. And there's the whole lack of block and item IDs to have to worry about, which could potentially save you from needing to learn config files altogether for a while. I guess it mostly depends on whether you're one of those individuals who has performance problems with 1.7, which might make it less enjoyable to work with.
1.5 offers no real advantage over 1.6 that I can think of, unless you really hate horses or the newer resource pack format. 1.6 and below still use the MCP build system rather than Gradle, which honestly might be easier to learn on, especially if you've already played with MCP itself before. You can also still edit the base classes to help you figure out how things in the game work along the way, which is locked down in 1.7 unfortunately.
I also recommend just getting MCP and playing with the game directly, especially with 1.7 (and probably up) where Forge won't let you. This way you can get a feel for how the game is laid out without worrying about Forge, and change basically anything you want to see how it affects the game. But if you really want to add your own blocks or items into the game right away, then this probably wouldn't be the best route to focus on.