Adding mods is adding redundant content. It's already present in mods, why spend time forcing it on everyone?
The mod api was still a long way off when pistons were added, this is no longer the case. When all the hassle of installing mods is gone there's really no reason to add any mod to vanilla.
Why bother updating Minecraft at all. Minecraft is already finished. People who want it can already have it.
/sarcasm
This is a false dichotomy, a better comparison would be, "Why bother adding sheep? The game already has sheep. People who want it can already have it."
And at the same time, why would the Mod API make people opposed to adding mods to vanilla?
Because it would unnecessarily force content on everyone rather than simply making it available to those who want it. It would also be a huge waste of Jeb's time. Perhaps he can explain it better than I can.
Adding mods is adding redundant content. It's already present in mods, why spend time forcing it on everyone?
The mod api was still a long way off when pistons were added, this is no longer the case. When all the hassle of installing mods is gone there's really no reason to add any mod to vanilla.
Isn't it required that everybody have every mod a SMP server has? I don't know how the client would make use of the data being sent otherwise. Adding good mods that lots of people use, but are not forced to, makes things simpler (pistons being a good example of such a mod.)
Integrating certain mods into the game should increase compatibility with other mods, as the other mods can count on the data being there all the time.
It's good to add mods that add a few optional blocks with many useful applications. It's not good to add mods that add a bunch of blocks that are useless and forced upon the player.
A lot depends on how good the API actually is. Will it really make cross-mod and SMP compatibility that much better?
Rollback Post to RevisionRollBack
Mostly moved on. May check back a few times a year.
Adding mods is adding redundant content. It's already present in mods, why spend time forcing it on everyone?
The mod api was still a long way off when pistons were added, this is no longer the case. When all the hassle of installing mods is gone there's really no reason to add any mod to vanilla.
Adding mods is not adding redundant content unless you already have the mod installed when it is added to the game.
And once again, I bring up Pistons.
"It's already present in mods, why spend time forcing it on everyone?"
Why don't you answer your own question? They've already done it.
And it wasn't because of the lack of an official mod API. There were plenty of unofficial ones around. It was because Notch/Jeb thought of Pistons as a good addition to vanilla Minecraft.
Because it would unnecessarily force content on everyone rather than simply making it available to those who want it. It would also be a huge waste of Jeb's time. Perhaps he can explain it better than I can.
Every single update does that. Jeb "unnecessarily" forces content on us every update because of how he wants to make Minecraft. If Jeb wants to make mods officially part of Minecraft, like what happened with Pistons, what is stopping him?
Buildcraft pipes (and generators + electric furnaces if done right) are the only things that are non-gameplay intrusive and should be introduced to the game, at least at some point.
what I meant was that he should add SOME of the things not everyting.
just like pipes engines and stuff like that.
Adding mods is adding redundant content. It's already present in mods, why spend time forcing it on everyone?
The mod api was still a long way off when pistons were added, this is no longer the case. When all the hassle of installing mods is gone there's really no reason to add any mod to vanilla.
This is a false dichotomy, a better comparison would be, "Why bother adding sheep? The game already has sheep. People who want it can already have it."
Because it would unnecessarily force content on everyone rather than simply making it available to those who want it. It would also be a huge waste of Jeb's time. Perhaps he can explain it better than I can.
http://www.gamasutra.com/view/feature/6627/talking_the_future_of_minecraft.php
Integrating certain mods into the game should increase compatibility with other mods, as the other mods can count on the data being there all the time.
It's good to add mods that add a few optional blocks with many useful applications. It's not good to add mods that add a bunch of blocks that are useless and forced upon the player.
A lot depends on how good the API actually is. Will it really make cross-mod and SMP compatibility that much better?
Mostly moved on. May check back a few times a year.
And once again, I bring up Pistons.
"It's already present in mods, why spend time forcing it on everyone?"
Why don't you answer your own question? They've already done it.
And it wasn't because of the lack of an official mod API. There were plenty of unofficial ones around. It was because Notch/Jeb thought of Pistons as a good addition to vanilla Minecraft.
Every single update does that. Jeb "unnecessarily" forces content on us every update because of how he wants to make Minecraft. If Jeb wants to make mods officially part of Minecraft, like what happened with Pistons, what is stopping him?
Nothing.
Nothing at all.
what I meant was that he should add SOME of the things not everyting.
just like pipes engines and stuff like that.