Lame! Thats what I hate the most about minecraft, the way constant updates screws up everything. I have no interest whatsoever in vanilla minecraft and couldnt care less about what minor new additons they add. I cant tell any difference from 1.2.5 and 1.4.7. If I were a modder Id stick with one version for a long while cuz its not like starting a new world is something you do every single day. And I wouldnt remove links to older versions either...
I guess that's why you're not a modder. There is a vast difference between 1.2.5 and 1.4.7. Besides, updates have tech additions (the new creative menu, and singleplayer commands) and bugfixes.
And guess what?
No one cares that you don't care about additions.
Code still changes.
As for the older versions, to many morons like you were asking for updates for a depreciated version of a mod. It's mDiyo's decision.
I downloaded ThaumCraft 3.0.5.a for Minecraft 1.5.2 and it crashes my Minecraft when I log in. I have the current Forge and my other mods (Forestry,Rei's Minimap,Buildcraft),are all updated too, I don't know what causes it but I get this message after the Mojang Logo disappears.. http://www.flickr.com/photos/95743775@N04/8737475389/in/photostream/lightbox/
I know its not my other mods because if I take all my other mods out of the "mods" folder in the ".minecraft" folder its stills shows the same message.
Post above give better info than mine, he actually knows the link.
You obviously do not have the current forge. You have the latest recommended version, not the latest. Sheesh, people keep mixing them up.
The correct download page only has the list of releases on it, nothing else at all.
Just look for a page that's white, with the versions listed as just plain text, with 4 blue downloads, each with an asterisk next to it.
Yea, the old tools that will be coming back haven't been added yet. But, you don't have infinite free diamonds, or easy ways of getting end-game level tools.
I'd request that people get over EE2.
But, sometimes, people are obsessive, and don't realize when nerfs are needed.
It's annoying.
I love how EE3 is going. EE2 was way to OPed in my opinion. Not sure why anyone still wants it, it's practically using NEI, or TMI. This though, it's very hard to get the 8 minum (Is that how it's spelled?) shards. Making it a practical, but expensive way of getting stuff.
GJ, those EE2 fanboys don't know what they're talking about.
I'll try and get to the 1.5.2 update and bugfixes this week, but then things will probably go quiet for while... for a good reason though I need to start working on 3.1.
I need to start working on 3.1.
1
I guess that's why you're not a modder. There is a vast difference between 1.2.5 and 1.4.7. Besides, updates have tech additions (the new creative menu, and singleplayer commands) and bugfixes.
And guess what?
No one cares that you don't care about additions.
Code still changes.
As for the older versions, to many morons like you were asking for updates for a depreciated version of a mod. It's mDiyo's decision.
1
Post above give better info than mine, he actually knows the link.
You obviously do not have the current forge. You have the latest recommended version, not the latest. Sheesh, people keep mixing them up.
The correct download page only has the list of releases on it, nothing else at all.
Just look for a page that's white, with the versions listed as just plain text, with 4 blue downloads, each with an asterisk next to it.
1
Bah.
1
Exactly. Build 304 is stable, and every IC2 mod/compatability mod, has been updated/updating to use this build.
1
Yea, the old tools that will be coming back haven't been added yet. But, you don't have infinite free diamonds, or easy ways of getting end-game level tools.
I'd request that people get over EE2.
But, sometimes, people are obsessive, and don't realize when nerfs are needed.
It's annoying.
1
Please.
Thank you.
2
GJ, those EE2 fanboys don't know what they're talking about.
Edit: What fuel would the calcificator/audel use?
1
It's been said on almost every page, and asked constantly.
THEY HAVEN'T BEEN RELEASED YET.
Which, as they aren't in the .jar, SHOULD BE OBVIOUS.
1
Not yet.