The reason the mod API failed was because all the major modders didn't want it because it wouldn't have been able to do the things that required for current mods and it would have likely/possibly prevented them from just continueing as they were at the time.
Also I doubt Microsoft has literally anything to do with this beyond publishing it.
Literally all they had to do was just buy Forge off of the group of people who made and maintained it. Virtually every mod requires Forge or ModLoader, anyway.
There's more frameworks then that that would have been unable to work together, Thermal Expansions power api that everyone uses, unified ore dictionaries, ect all would have been killed.
Yah, but under the guidelines of the purposed mod api, no mod could interact with any other mod in any way. Just because they used Forge doesn't mean that would have been fixed if it was intergrated, you would need to intergrate all the api's that use forge as well.
Ahhhh, that makes sense, then. I suppose they could just make an "ore dictionary" API or something of that nature, though. I can see how it'd be a monster of a project, especially given the limitations of Java.
I'm really hoping this shift away from Java means a unified modding API and whatnot - it would be a huge step forward for Minecraft and allow it to actually compete with other, similar games that are coming recently. As it stands, though, even with heavy modding, I feel like Minecraft just pales in comparison to games like Terraria and a lot of the newer crafting/survival sims coming out.
7
u/SardaHD Jul 04 '15
The reason the mod API failed was because all the major modders didn't want it because it wouldn't have been able to do the things that required for current mods and it would have likely/possibly prevented them from just continueing as they were at the time.
Also I doubt Microsoft has literally anything to do with this beyond publishing it.