Mod API not in 1.3?
- jppk1
- Closed
-
Will have to grab Eloraam and Todd on IRC, we should agree NOT to update to 1.3
-
Will have to grab Eloraam and Todd on IRC, we should agree NOT to update to 1.3
Don't forget Azanor!
-
If so, 1.2.5 is going to break the record in longest lasting stable Minecraft version, previously set by 1.7.3.
Spacetoad is pretty much gone, talk to Sengir.
-
If you do agree to not update, remember to put in BIG YELLOW LETTERS somewhere in the blog and the forum that IC2 will not update to 1.3 otherwise i fear for the worst.
-
during such time you should just disable forum registration it will kill 2 birds with one stone. the spambots, and the fly-by-night n00b posters.
-
If you do agree to not update, remember to put in BIG YELLOW LETTERS somewhere in the blog and the forum that IC2 will not update to 1.3 otherwise i fear for the worst.
Yes the BIG YELLOW LETTERS are good, and if then a Noob comes with that, i can engage Facepalmmode on my Profile.
-
Will have to grab Eloraam and Todd on IRC, we should agree NOT to update to 1.3
Did it work?
-
One of Mojang's devenlopers tweeted this something a couple of weeks ago:
"We'll probably have the API 1.4 now, so until then 1.3/these snapshots will be hard to update to." Link
Seems pretty typical and we propably won't have the mod API until MC 1.5, atleast that's my guess.
I hope you stay 1.2.5. I'm tired as fuck having to deal with Mojang's bullshit and lies. I mean have they ever done a update in history planned right? No. But since their player base is a bunch of 12 year olds who are getting off school now and cranky they gotta push an update out. Hell I have hardly seen any API so far and FFS if API is not coming out and they not been adding it into the main repo where has it been going? I doubt they were working on 2 repo's and going to merge such a massive change. Mainly because a lot of the API changes would hopefully make them realize of some major issues and actually rewrite parts of Minecraft for performance reasons.
IDK but ffs I hope you do not update to 1.3 and you guys ALL make a firm stand.
-
Is there another IC²-Update for 1.2.5 planned (not asking for date), because i'm tired of making these two Cablehotfixes for Frames and Gamereloading for every Machine i build.
Hint: It's a Splittercable, which cuts the line on Chunkreload (via CC-Computer) for one Second, to update the E-net WITHOUT breaking and replacing any Wire.
-
At risk of reviving a dead thread, it's been confirmed that the API isn't in 1.3:
QuoteAnd the most notable missing feature is the modding API.
If Mojang is going to ruin mod compatibility, I'd at least like the option to "downgrade" to 1.2.5 after 1.3 comes out.
-
I'd at least like the option to "downgrade" to 1.2.5 after 1.3 comes out.
It's called "back-up".
-
At risk of reviving a dead thread, it's been confirmed that the API isn't in 1.3:
If Mojang is going to ruin mod compatibility, I'd at least like the option to "downgrade" to 1.2.5 after 1.3 comes out.
At risk of geting ninjaed by "I dont now" before going to Bed.
I have a BackUp of the minecraft.jar for 1.2.5 so i can downgrade whenever i want.
-
At risk of geting ninjaed by "I dont now" before going to Bed.
I have a BackUp of the minecraft.jar for 1.2.5 so i can downgrade whenever i want.
You were ninja'd.
-
Quote
It's called "back-up".
I'm a bit more worried about what happens when people don't find about IC2, Redpower, etc. until after 1.3 comes out. (Or those who stupidly upgrade minecraft without realizing it'll break mod compatibility. God knows I did that after MC 1.0 came out. . .) -
I've stopped modding my main minecraft directory.
Now I use Magic Launcher and have all my mods in custom .minecraft directories that will not be affected when 1.3 comes out.
I'm going to update my main client as usual but I'll still be able to pretty much flip a switch in Magic Launcher to play 1.2.5 with mods as if nothing happened.
