You should generally not have to make your readers google an entire quote... but whatever.
Oh so now we're on to the white knight thing? I'm not even defending the game this time. It seems like I am the last person on this miserable forum who actually likes minecraft. Everyone else seems to "like" minecraft but they find a way to complain about it at every turn and antagonize those who are content.
Complaining is the tool that makes your Minecraft better.
Many of the people here who consider complaining a valuable tool (and a natural occurrence of the human psyche), do not necessarily agree to all forms of complaining. There's a minimum of decency, respect and addressing rules that must be followed for a complaint to be considered legitimate, even if demonstrably wrong.
This game sucks. This update ruined minecraft! I'm off! Isn't not even close to be a legitimate complaint. I really dislike what they did to the enchantment system. I think they are destroying this feature, followed by some explanation, is a legitimate complaint, even if it someone demonstrates it to be wrong.
On the other hand, just because complaining can drive a game to become better, that doesn't mean praising hasn't a place. And one should always exert both if they can. As a software developer myself I can't tell you how important criticism is to me, but how it warms my heart and motivates me to hear the occasional praise.
Forgive me for being n00b, but what's the difference?
You're not being a noob, they are being stupidly nit-picky. To the general public, they are the same thing. The only people that make a big stink about the terminology are forum jockeys that want to show off their CompSci education (or pretend they have one). This same population will liberally abuse words like "literally" and "per se", but will suddenly get pedantic when it comes to video games.
He means EvilSeph and Tahg. Both bukkit developers. Tahg explicitly said he left mojang due to differences in the direction of the game and constant changes of focus (source). I too wouldn't be surprised EvilSeph left for similar reasons. It's a common occurrence when the farewell message includes such laconic words as "pursuing other interests".
It is important to note that EvilSeph was the primary developer interfacing with the mod developer community and working on trying to gather the ideas submitted to Mojang from the mod developers for creating the API. With him gone, all of that interaction is basically lost as well as any consensus about what needs to be even put into the API.
What the API really does, ultimately, is to turn Minecraft from a game into a pretty interesting game engine that other games can be built around (with of course licensing from Mojang). I can cite other examples of game engines that have been done like this before, but I will also suggest that the window of opportunity for Mojang is closing.
A good example of a "game built on Minecraft" is Millenaire, which is definitely a different kind of game playing experience than vanilla Minecraft. IndustrialCraft is still another very different game based upon Minecraft (and obviously using the base Minecraft engine). This is what modding has done, and what the API is going to open up even more. It is definitely to the best interest of Mojang from at least an economic viewpoint to encourage development of these kind of additional experiences and indeed to open up those experiences beyond those willing to take the plunge and be willing to even install mods on their computer.
One of the problems that I see with perhaps both what is going on with the Mojang developers (I really hope not) as well as with many of those who talk about the API is the belief that somehow the entire API needs to be handed down as if created by God carved on stone tablets and be completely finished in one complete action. If that is the thought process going on, the API will never be done as there will always be flaws and problems with any approach taken.
What I'm interested in seeing with the Minecraft API is to get just the bare bones basics of the API started. I'm not talking anything fancy, but instead being able to do something simple like creating a new "big dumb block". I'm talking something which can read in a texture from an image file, apply that texture (or textures) upon some sides of a new block, and add the recipe for that block into the game so players can use your "mod" with your fancy "new block". If not this simple task, then something very similar which has a very clear scope and can provide the kernel concepts of an API. Seriously, how hard is it for Mojang to get this basic funcationality started?
**Something** in this case really is better than nothing, and even if this tentative first step into an API is completely scrapped at least it gives room for legitimate discussion of what needs to go into the API both by those using the API as well as the developers themselves. At the moment, we have nothing at all except for some rough API functions that likely will never be used either. The complaints above are valid as it has been literally years of talking but nothing to debate other than even **IF** the API should be implemented in the first place. Most would argue that it should be added, but in this case talk is cheap.
I'm even arguing that the "behind the scenes" rewriting of Minecraft is not really being done for the benefit of the API precisely because there is no apparent roadmap for how it is going to be used in the API either. There are valid reasons (mainly for ease of updating the game for the developers themselves) for many of the changes that have taken place, so it isn't a wasted effort even if the API is never implemented. The real unfortunate thing right now, and what really is a problem, is that even 3rd party API like Risugami's ModLoader and even Forge are now broken with regards to the current version of Minecraft. There is also hesitation on the part of some in the mod community to push ahead with fixing MCP or the other API libraries if the official API is just around the corner.
I guess it is about time for Mojang to put up or shut up. I really would like the question in the OP to be answered in this case: Is the Minecraft API actually being developed or not?
Mostly, yes. They're human too, and if I was hired by Mojang, I probably wouldn't have a lot of motivation to work my butt off. I'd be playing Minecraft all day, and I'd fix and update only the things that bothered me personally in the course of my own gameplay.
As a (I guess I have to say 'former') developer, I can tell you with certainty it doesn't work that way (at least at this scale). You have a database full of bug reports that usually get triaged by a project manager. Usually certain bugs get assigned to a specific person that handles certain types of bugs well, but otherwise you just go down the list fixing what you can. The sad reality is that most projects are short by a developer or two, so the bug list just tends to build up over time. Also, some bugs just can't be fixed within a reasonable amount of effort. Sure you could recode an entire project to address some fundamental problem, but no one is going to do that. You might as well create a whole new one at that point. So what I am saying is, I doubt they are spending all their time playing Minecraft. Also, some projects (like the plug-in API) might not ever happen despite assurances to the contrary. To be honest, I am not comfortable speculating either way.
I really would like the question in the OP to be answered in this case: Is the Minecraft API actually being developed or not?
As you astutely observed chances are they aren't developing it. Their laconic statements on the matter seem more like cop out attempts at admitting this much. Jeb says that technically they are working on the Plugin API because they are making a bunch of changes to the code. We say that technically all changes to the code end up influencing the API development, which means his argumentation isn't convincing at all. He's just shifting the cause for the consequence.
The more I think about it, the more I'm convinced my question serves no purpose. It was already answered before I put it up by years of complete neglect of this feature.
Likewise I'm not (at all!) convinced by the argument that they are working on it, trying to perfect it, outside the main development. This is simply not true. To their credit they never said this. It's folks here that are saying it. But it's just not true when we suffered in 1.7.2 a big change to the code base announced by them as a necessary step in the making of the Plugin API that broke all mode support. Had they been working on the Plugin API outside the main trunk, this change would have never happened.
In particular, the new naming convention is necessary not just for a potential plugin API. It is welcomed by forge and mod makers that will have now a way to finally avoid id conflicts and it is a way to avoid the limitations of reaching the upper bound of a numbering system. All in all, this particular change can be thought of as entirely unrelated to the Plugin API and done solely for other purposes. Because quite frankly at this stage I can't see how it can be claimed by anyone that the mod API is being developed.
Too bad Mojang is trying to avaoid developing the Mod/Plugin Api.
Also, it's even worse that they still update Minecraft while the few people that are working on the Api are making little progress ,as they will never attempt to finish it.
I always wanted the Mod/Plugin API because installing mods for multiplayer is a pain, and plug-ins can't do enough.
Well, I guess now it's only going to be a dream.
*Also, bump
The last few updates, especially 1.7 has laid down some solid foundations for the API. So we will get it. Baby steps.
I came here expecting to read some short posts. Why is it that every time someone disagrees with someone else on the internet we have to resort to writing paragraphs of text. I wish MinecraftForum was ADHD friendly ._.
TBH, I hope it is in development, for the sake of developers worldwide.
Why is it that every time someone disagrees with someone else on the internet we have to resort to writing paragraphs of text.
Blaise Pascal once wrote "I have only made this letter longer because I have not had the time to make it shorter."
I hope that helps clear it out for you that succinct thoughts are hard and take time to come by. Especially in a debate between opposing points of view and where cherry picking is an usual (and wrong) tactic against your opponent.
It's also considered rude to comment on people's posts size. Besides, if you don't like to read, web forums probably aren't the place for you. The posts in this thread aren't even close to be considered walls of text. With that attitude of yours, I suggest perhaps you don't read a good 75% of the threads on these forums.
The Meaning of Life, the Universe, and Everything.
Join Date:
5/22/2012
Posts:
57
Member Details
I think when they lost EvilSeph, somewhere the decision was made that the command block is now the "API," and that's why they're expanding its functionality so much, to include WorldEdit-like functions.
Will people ever stop asking this question? Will people ever be patient? Find out after commercial sign.
There is patient and then there is Duke Nuke'em Forever patient. I think the question about the API falls into this latter category. Perhaps kids in grade school today will be using the API when they graduate from college.
Will people ever stop asking this question? Will people ever be patient? Find out after commercial sign.
This question doesn't exist out of lack of patient. I think you misunderstand what is being discussed. This question is -- and has been -- raised because the developers themselves speak nonchalantly about a feature that ends up never existing. It's been promised for years. It started with Notch himself.
2 years ago, shortly after being hired by Mojang for the explicit purpose of developing the Plugin API, Dinnerbone gave a Q&A on reddit. As you'd expect most of the questions directed at him were about the API. And he answered them all. Right there and then, a lot of what was expected to become the Plugin API was laid out. But we haven't seen anything. Absolutely anything. And this was 2 years ago. Not 6 months. Not 1 year. It was 2 years ago. Minecraft itself took this time to grow from a concept game java applet posted to the TIGSource forums in 2009 to a final release product in 2011. Most of which time it was developed by a single person.
And I'm not even considering all that was said before Dinnerbone. If we were to put the whole Plugin API into perspective we would have to trace it back to Notch in 2010.
But you would not see these questions appearing from time to time if the developers themselves didn't speak about it. No one in here is coldhearted. Many of us can understand if they just said the whole Plugin API idea has to be taken aside. Temporarily or indefinitely (although I suspect the latter could raise a few questions on how would think work with Forge). It's the apparent lack of candor that is being questioned here. I mean, did we really need to hear that the reason they made the changes to the naming system was to pave the way for the Plugin API, when it is obvious there's no Plugin API being developed? There's so many more important reasons for that most welcomed change to have happened. Why did we need to hear an half-truth?
Of course it helps the Plugin API. But that doesn't mean one thing if that plugin API isn't being developed. I may model the coolest 3D tanks to pave the way for my awesome strategy game. But that won't mean a thing if I don't actually develop the strategy game.
There's no impatience in my question. I've lived with the Plugin API promises since 2010. I'm on the Duke Nukem Forever phase, as King Korihor put it above me. What there is is an actual honest question. Is, or is it not being developed. Of course you may accuse me of false pretenses because I apparently already know the question to that answer. And I would have to agree with you to some extent. My question was from the very start pretty much a rhetoric question. What really drives me is a dislike of feeling cheated by this false idea the developers keep passing that they are working on a Plugin API.
Maybe I'm just being naive, or trying to remain positive, but here's my opinion for what it's worth:
It seems to me that re-writing the code of Minecraft to the point that the vanilla game itself can be considered a Plugin is going to take a long time, especially if Mojang had intended to keep up the additions to the survival aspect of the game. It may very well be that some of the commands and map-making oriented changes are merely by-products of these changes to the coding.
As for trying to determine who was doing what, and when, we may eventually get to see one of those shiny graphical representations of the coding process, and if such information were immediately available to anyone who happened to be interested, then we would already have our answers.
I'd like to finish by pointing out that nobody is perfect, not even our beloved Minecraft development team, and it's very likely that mistakes, setbacks, and even outright reversals may have been made along the way that have hindered the process of finally making the toy we can literally play with as we please.
There is no official source in which states the API is not being developed. There are, however, many sources that state that the API is being developed. What other reason caused the change of numerical ID's? Simplifying mapmaking isn't such a large reason to make such a sudden change. I do see why anyone would accuse the devs of not developing said API, as we don't constantly receive news from it. If every snapshot had "Progress to API has been made," (similar to the "Removed Herobrine" line) there would be less accusations; although, I believe many would be suspicious that every snapshot had the same exact line, yet they see no actual change. I prefer the devs add more content and fix more bugs than a whole half a year's worth of only developing the API and completing it.
If they were to not actually release an API, they would have told us so. This removes all the hopeless thoughts of an API, and people would continue with their lives as they already do now.
Many of us can understand if they just said the whole Plugin API idea has to be taken aside. Temporarily or indefinitely (although I suspect the latter could raise a few questions on how would think work with Forge). It's the apparent lack of candor that is being questioned here. I
What's particularly annoying is that if they'd just fix the obfuscated names changing with every update, they'd have a functioning API in Forge. Not the best, sure, but functioning. Most of the Forge code patches could just be integrated into the source.
Rollback Post to RevisionRollBack
Geographicraft (formerly Climate Control) - Control climate, ocean, and land sizes; stop chunk walls; put modded biomes into Default worlds, and more!
RTG plus - All the beautiful terrain of RTG, plus varied and beautiful trees and forests.
What other reason caused the change of numerical ID's? Simplifying mapmaking isn't such a large reason to make such a sudden change.
The removal of numeric IDs is one of the most important changes to the game in recent times. It's, at least in my opinion, by far the best thing in the whole 1.7 branch. Even better than the new biomes, and the new blocks. Personally, I simply love this change in the game and my love for it has nothing to do with the Plugin API (for one, because as you know, we don't actually have a Plugin API).
This change can take effect immediately and is going to take effect immediately on many mod makers that can right now start changing their mods to support it. So long item ids clashes. One of the most ubiquitous problems with modding. With our without the Plugin API, with or without Forge, the change to items IDs is already a great benefit to the modding community.
If they were to not actually release an API, they would have told us so. This removes all the hopeless thoughts of an API, and people would continue with their lives as they already do now.
I would hope so. I think the problem is however a bit more complex. If Mojang comes out and openly says the Plugin API is a dropped project, questions will arise about how are we going to support mods in the future. Will we ever be dependent on Forge? Will the Forge team be able to always respond to code changes? Will code changes like 1.7.2 that invalidate Forge rapid response happen more often?
There's a certain backlash that Mojang risks if they openly admit they were not going to develop the Plugin API anymore. It's just not pretty to see a game developer refusing to provide mod support for their game. So, in a way I can understand why Mojang is reluctant in admitting it. But I do agree they should just say it and be done with it. Maybe even strike a deal with the forge team along with a non disclose contract to save some (not necessarily all) of their troubles in deobfuscating the code.
EDIT: Just saw Zeno410 reply above me and that's pretty much in line with my reasoning. All this could be avoided and Mojang be freed from an obvious headache if they thought out ways to facilitate the work of the Forge team, or simply incorporate their work in Minecraft. After all, someone already did a Plugin API. And they didn't even have access to the code. It's only Mojang that doesn't, despite all their promises.
On a more realistic note, the changes to the engine and mechanics have been amazing thus far, so i'm not a complete cynic.
Complaining is the tool that makes your Minecraft better.
Many of the people here who consider complaining a valuable tool (and a natural occurrence of the human psyche), do not necessarily agree to all forms of complaining. There's a minimum of decency, respect and addressing rules that must be followed for a complaint to be considered legitimate, even if demonstrably wrong.
This game sucks. This update ruined minecraft! I'm off! Isn't not even close to be a legitimate complaint. I really dislike what they did to the enchantment system. I think they are destroying this feature, followed by some explanation, is a legitimate complaint, even if it someone demonstrates it to be wrong.
On the other hand, just because complaining can drive a game to become better, that doesn't mean praising hasn't a place. And one should always exert both if they can. As a software developer myself I can't tell you how important criticism is to me, but how it warms my heart and motivates me to hear the occasional praise.
You're not being a noob, they are being stupidly nit-picky. To the general public, they are the same thing. The only people that make a big stink about the terminology are forum jockeys that want to show off their CompSci education (or pretend they have one). This same population will liberally abuse words like "literally" and "per se", but will suddenly get pedantic when it comes to video games.
It is important to note that EvilSeph was the primary developer interfacing with the mod developer community and working on trying to gather the ideas submitted to Mojang from the mod developers for creating the API. With him gone, all of that interaction is basically lost as well as any consensus about what needs to be even put into the API.
What the API really does, ultimately, is to turn Minecraft from a game into a pretty interesting game engine that other games can be built around (with of course licensing from Mojang). I can cite other examples of game engines that have been done like this before, but I will also suggest that the window of opportunity for Mojang is closing.
A good example of a "game built on Minecraft" is Millenaire, which is definitely a different kind of game playing experience than vanilla Minecraft. IndustrialCraft is still another very different game based upon Minecraft (and obviously using the base Minecraft engine). This is what modding has done, and what the API is going to open up even more. It is definitely to the best interest of Mojang from at least an economic viewpoint to encourage development of these kind of additional experiences and indeed to open up those experiences beyond those willing to take the plunge and be willing to even install mods on their computer.
One of the problems that I see with perhaps both what is going on with the Mojang developers (I really hope not) as well as with many of those who talk about the API is the belief that somehow the entire API needs to be handed down as if created by God carved on stone tablets and be completely finished in one complete action. If that is the thought process going on, the API will never be done as there will always be flaws and problems with any approach taken.
What I'm interested in seeing with the Minecraft API is to get just the bare bones basics of the API started. I'm not talking anything fancy, but instead being able to do something simple like creating a new "big dumb block". I'm talking something which can read in a texture from an image file, apply that texture (or textures) upon some sides of a new block, and add the recipe for that block into the game so players can use your "mod" with your fancy "new block". If not this simple task, then something very similar which has a very clear scope and can provide the kernel concepts of an API. Seriously, how hard is it for Mojang to get this basic funcationality started?
**Something** in this case really is better than nothing, and even if this tentative first step into an API is completely scrapped at least it gives room for legitimate discussion of what needs to go into the API both by those using the API as well as the developers themselves. At the moment, we have nothing at all except for some rough API functions that likely will never be used either. The complaints above are valid as it has been literally years of talking but nothing to debate other than even **IF** the API should be implemented in the first place. Most would argue that it should be added, but in this case talk is cheap.
I'm even arguing that the "behind the scenes" rewriting of Minecraft is not really being done for the benefit of the API precisely because there is no apparent roadmap for how it is going to be used in the API either. There are valid reasons (mainly for ease of updating the game for the developers themselves) for many of the changes that have taken place, so it isn't a wasted effort even if the API is never implemented. The real unfortunate thing right now, and what really is a problem, is that even 3rd party API like Risugami's ModLoader and even Forge are now broken with regards to the current version of Minecraft. There is also hesitation on the part of some in the mod community to push ahead with fixing MCP or the other API libraries if the official API is just around the corner.
I guess it is about time for Mojang to put up or shut up. I really would like the question in the OP to be answered in this case: Is the Minecraft API actually being developed or not?
Version 2.1 now updated for MC 1.6.2
As a (I guess I have to say 'former') developer, I can tell you with certainty it doesn't work that way (at least at this scale). You have a database full of bug reports that usually get triaged by a project manager. Usually certain bugs get assigned to a specific person that handles certain types of bugs well, but otherwise you just go down the list fixing what you can. The sad reality is that most projects are short by a developer or two, so the bug list just tends to build up over time. Also, some bugs just can't be fixed within a reasonable amount of effort. Sure you could recode an entire project to address some fundamental problem, but no one is going to do that. You might as well create a whole new one at that point. So what I am saying is, I doubt they are spending all their time playing Minecraft. Also, some projects (like the plug-in API) might not ever happen despite assurances to the contrary. To be honest, I am not comfortable speculating either way.
As you astutely observed chances are they aren't developing it. Their laconic statements on the matter seem more like cop out attempts at admitting this much. Jeb says that technically they are working on the Plugin API because they are making a bunch of changes to the code. We say that technically all changes to the code end up influencing the API development, which means his argumentation isn't convincing at all. He's just shifting the cause for the consequence.
The more I think about it, the more I'm convinced my question serves no purpose. It was already answered before I put it up by years of complete neglect of this feature.
Likewise I'm not (at all!) convinced by the argument that they are working on it, trying to perfect it, outside the main development. This is simply not true. To their credit they never said this. It's folks here that are saying it. But it's just not true when we suffered in 1.7.2 a big change to the code base announced by them as a necessary step in the making of the Plugin API that broke all mode support. Had they been working on the Plugin API outside the main trunk, this change would have never happened.
In particular, the new naming convention is necessary not just for a potential plugin API. It is welcomed by forge and mod makers that will have now a way to finally avoid id conflicts and it is a way to avoid the limitations of reaching the upper bound of a numbering system. All in all, this particular change can be thought of as entirely unrelated to the Plugin API and done solely for other purposes. Because quite frankly at this stage I can't see how it can be claimed by anyone that the mod API is being developed.
The last few updates, especially 1.7 has laid down some solid foundations for the API. So we will get it. Baby steps.
Venit, quessit, induravit.
TBH, I hope it is in development, for the sake of developers worldwide.
(p.s. I don't actually have ADHD).
Blaise Pascal once wrote "I have only made this letter longer because I have not had the time to make it shorter."
I hope that helps clear it out for you that succinct thoughts are hard and take time to come by. Especially in a debate between opposing points of view and where cherry picking is an usual (and wrong) tactic against your opponent.
It's also considered rude to comment on people's posts size. Besides, if you don't like to read, web forums probably aren't the place for you. The posts in this thread aren't even close to be considered walls of text. With that attitude of yours, I suggest perhaps you don't read a good 75% of the threads on these forums.
And that means what exactly? That we shall get the plugin api soon? Is that what you are saying?
Praise be to Spode.
There is patient and then there is Duke Nuke'em Forever patient. I think the question about the API falls into this latter category. Perhaps kids in grade school today will be using the API when they graduate from college.
Version 2.1 now updated for MC 1.6.2
This question doesn't exist out of lack of patient. I think you misunderstand what is being discussed. This question is -- and has been -- raised because the developers themselves speak nonchalantly about a feature that ends up never existing. It's been promised for years. It started with Notch himself.
2 years ago, shortly after being hired by Mojang for the explicit purpose of developing the Plugin API, Dinnerbone gave a Q&A on reddit. As you'd expect most of the questions directed at him were about the API. And he answered them all. Right there and then, a lot of what was expected to become the Plugin API was laid out. But we haven't seen anything. Absolutely anything. And this was 2 years ago. Not 6 months. Not 1 year. It was 2 years ago. Minecraft itself took this time to grow from a concept game java applet posted to the TIGSource forums in 2009 to a final release product in 2011. Most of which time it was developed by a single person.
And I'm not even considering all that was said before Dinnerbone. If we were to put the whole Plugin API into perspective we would have to trace it back to Notch in 2010.
But you would not see these questions appearing from time to time if the developers themselves didn't speak about it. No one in here is coldhearted. Many of us can understand if they just said the whole Plugin API idea has to be taken aside. Temporarily or indefinitely (although I suspect the latter could raise a few questions on how would think work with Forge). It's the apparent lack of candor that is being questioned here. I mean, did we really need to hear that the reason they made the changes to the naming system was to pave the way for the Plugin API, when it is obvious there's no Plugin API being developed? There's so many more important reasons for that most welcomed change to have happened. Why did we need to hear an half-truth?
Of course it helps the Plugin API. But that doesn't mean one thing if that plugin API isn't being developed. I may model the coolest 3D tanks to pave the way for my awesome strategy game. But that won't mean a thing if I don't actually develop the strategy game.
There's no impatience in my question. I've lived with the Plugin API promises since 2010. I'm on the Duke Nukem Forever phase, as King Korihor put it above me. What there is is an actual honest question. Is, or is it not being developed. Of course you may accuse me of false pretenses because I apparently already know the question to that answer. And I would have to agree with you to some extent. My question was from the very start pretty much a rhetoric question. What really drives me is a dislike of feeling cheated by this false idea the developers keep passing that they are working on a Plugin API.
It seems to me that re-writing the code of Minecraft to the point that the vanilla game itself can be considered a Plugin is going to take a long time, especially if Mojang had intended to keep up the additions to the survival aspect of the game. It may very well be that some of the commands and map-making oriented changes are merely by-products of these changes to the coding.
As for trying to determine who was doing what, and when, we may eventually get to see one of those shiny graphical representations of the coding process, and if such information were immediately available to anyone who happened to be interested, then we would already have our answers.
I'd like to finish by pointing out that nobody is perfect, not even our beloved Minecraft development team, and it's very likely that mistakes, setbacks, and even outright reversals may have been made along the way that have hindered the process of finally making the toy we can literally play with as we please.
If they were to not actually release an API, they would have told us so. This removes all the hopeless thoughts of an API, and people would continue with their lives as they already do now.
What's particularly annoying is that if they'd just fix the obfuscated names changing with every update, they'd have a functioning API in Forge. Not the best, sure, but functioning. Most of the Forge code patches could just be integrated into the source.
Geographicraft (formerly Climate Control) - Control climate, ocean, and land sizes; stop chunk walls; put modded biomes into Default worlds, and more!
RTG plus - All the beautiful terrain of RTG, plus varied and beautiful trees and forests.
The removal of numeric IDs is one of the most important changes to the game in recent times. It's, at least in my opinion, by far the best thing in the whole 1.7 branch. Even better than the new biomes, and the new blocks. Personally, I simply love this change in the game and my love for it has nothing to do with the Plugin API (for one, because as you know, we don't actually have a Plugin API).
This change can take effect immediately and is going to take effect immediately on many mod makers that can right now start changing their mods to support it. So long item ids clashes. One of the most ubiquitous problems with modding. With our without the Plugin API, with or without Forge, the change to items IDs is already a great benefit to the modding community.
I would hope so. I think the problem is however a bit more complex. If Mojang comes out and openly says the Plugin API is a dropped project, questions will arise about how are we going to support mods in the future. Will we ever be dependent on Forge? Will the Forge team be able to always respond to code changes? Will code changes like 1.7.2 that invalidate Forge rapid response happen more often?
There's a certain backlash that Mojang risks if they openly admit they were not going to develop the Plugin API anymore. It's just not pretty to see a game developer refusing to provide mod support for their game. So, in a way I can understand why Mojang is reluctant in admitting it. But I do agree they should just say it and be done with it. Maybe even strike a deal with the forge team along with a non disclose contract to save some (not necessarily all) of their troubles in deobfuscating the code.
EDIT: Just saw Zeno410 reply above me and that's pretty much in line with my reasoning. All this could be avoided and Mojang be freed from an obvious headache if they thought out ways to facilitate the work of the Forge team, or simply incorporate their work in Minecraft. After all, someone already did a Plugin API. And they didn't even have access to the code. It's only Mojang that doesn't, despite all their promises.