Well- Heres my two cents
Given its been
almost 2 years since Dinnerbone was hired to build the API- so far there's ... nothing.
Ok ok, 1.3 merged SSP and SMP- yet client and server side mods needed, and server lag+bugs brought into SSP. Promise of API not delivered. Very difficult update for modders.
1.4- Promise of API- nothing API related actually added or mentioned
1.5 New launcher- mod installation gets a lot harder. Everyone must jump through a lot of unnecessary complexity or use a 3rd party programme.
1.6 Not much in the way of API progress here. Have to re-authenticate your account if you play via old launcher or 3rd party launcher (like FTB)
1.7 Not even a HINT of an API in the changelog. Almost every mod seems broken by this update.
So there's nothing usable. No early alpha versions. No
Real progress- just seems like a never ending cycle of hassle, false hope and rebuilding mods while everyone waits for the next version.
Which then begs the question- why update?
Why not wait however many versions until when/IF we ever get said API?
If we stick on 1.5 or 1.6
- More mod dev time dedicated to building mod content
- Stable/Unchanging code base- making more complex/in depth mods significantly more viable.
- By extension I'd guess happier mod devs- I don't know anyone who enjoys porting forward.
- No more waiting for version updates- just new content when it comes
- By extension no more losing worlds/progress
- You'll be able to play 'abandoned'/non-updating mods (Redpower, apparentlyThermal Expansion) with 'new' content.
- Most likely more cross-compatibility- 'a' version of Xmod with 'b' version of Ymod (Eg you don't like GregTech's plates but love Thaumcraft 4.) {ok- hypothetical example but you get the idea.}
So I hear you ask - '
What about the new vanilla content/fixes?'
Why not pull that back onto 1.6?
It sounds a lot easier than pushing everything forward onto 1.7.
Also if the largest MC modded community collectively decides to stick with a version- it'll certainly make a point.
You never know- DB might hear us and actually implement said API.
Edit- so it seems we're looking at a total of
more than 3 years of API conception and development. (
5th July 2010), yet nothing solid. Thanks guys.
