A bit less than a year ago, I tried to make a bukkit plugin, but the hook I needed hadn't been implemented (and wouldn't be for a few months), causing me to resort to using redstone updates for the desired functionality.
Hopefully that will have changed, but if they try to completely replace modding with a single API like the previous bukkit, and don't leave the possibility of directly making mods similar to how they are now (as a last resort, if the API provided is lacking some functionality), then I forsee a very large community of people who will refuse to update...
Also, I really hope that the API implementation does not impose any overhead on SSP. I only get a decent framerate as it is, and I'm a bit worried that they'll create something that works well for servers, but causes irregular framerates when it has to share the system with the client.
I hope it turns out well, but I'll remain sceptical until/unless I see good results.
Rollback Post to RevisionRollBack
CraftGuide, recipe viewer with a scrollbar! (Resizable window, too, if you prefer playing with a smaller GUI scale and are tired of GUIs only occupying a tiny square in the centre)
Hey guys, remember when bukkit was really cool? Remember? Before Mojang ruined it? Anyone? Oh, right. No one browses the forums anymore because the joining of Bukkit and Mojang killed minecraft.
I fail to see how this is going to "kill Minecraft". Seriously.
Bukkit is still going to be open source, and the old ways of accessing classes of Minecraft will continue until Mojang decides to use something other than Java for developing the game. What is going to be ruined?
The worst situtation is that Bukkit might be forked if the "community" doesn't like where Mojang takes that part of the modding community, so they decide to really push the open source nature of the project with a new team of Bukkit developers. That has happened with projects like Open Office, and the "right to fork" is always something available for any open source project like Bukkit. If you don't like the direction some resources like this are going, you can always do the fork yourself. If you lack the skills to make that fork, that isn't my problem or anybody else's.
I don't like this at all. This is basically the death knell of the Minecraft community, along with most SMP servers. The proposed API is set to be closed-source, which kills the community aspect completely (and it's not like Bukkit ever gave a damn about the community either, what with their history of ignoring and neglecting the users of their product). That leaves the Spout project as the only viable option for most people who want to run a multiplayer server, and there's a very good chance that Mojang will shut them down to avoid competition, claiming it as a "benefit for the users". For the near future, 1.2 will be the end of Bukkit. For the long term, this could potentially mean the downfall of Minecraft entirely, depending on how the new API turns out.
And even that doesn't look like a given. Closed-source? Single-core (which is terrible in terms of performance)? A complete dismantling of any sense of community? A total lack of communication between Bukkit/Mojang and what remains of the userbase (the former already has a great track record in that regard)? And we'll STILL have considerable delays between patch version releases and the API patch? It's feasible that I could be playing 1.4 on singleplayer mode before the 1.3 server files are ready.
Either way, the best case scenario is that the community will die (or fracture if Spout is permitted to live), and the next three to six months will be a bigger cluster**** than ever before. Personally, as it stands now, I might just abandon Minecraft entirely, because this will certainly spell the demise of the server I help to run. I don't have enough faith in the Bukkit team to make a product that will be worth the incoming community flux and the lobotomizing of many servers. For example, here is a quote from Grum speaking about the official API, taken from Spout's IRC channel:
[13:40:49] <Grum> I personally do not see much benefit in making it opensource at this moment
[13:42:03] <Grum> you dont need to opensource to have the community
[13:42:06] <Grum> see Bukkit
This sort of ignorance is what will kill Minecraft's future. It's ironic that Bukkit was created because they wanted an open source, community driven project... and now after the community props them up, they abandon it in favor of closed-source paychecks.
Don't misinterpret my doomsday prophecies as me hating on Bukkit or Mojang; I hope that I'm 100% wrong on all of this. I want more than anything to see this endeavor succeed beyond my wildest dreams... but I simply cannot see that vision being anything more than a fantasy. For now, all I can really do is wait. If this API turns out to be a failure, then we'll all be relying on Spout to serve as the flagship client for developers. And if Mojang forces Spout to shut down, then this partnership will have alienated every single one of Minecraft's SMP players.
I don't think you understand what an API is. A closed source API didn't stop Blizzard's WoW community of modders for client side stuff. It didn't stop Elder Scrolls modders, Fallout, etc. A closed source API doesn't shut out modders. It's an API. It's purpose to to provide an controlled interface to developers, not shut them out.
.Net is a closed source API. So is all of DirectX. XNA is a closed source api also and thousands upon thousands of games are built on it.
An API is an API. I don't think you quite understand the purpose of an API.
This is good. I wonder if this means that bukkit plugins can contain new items and blocks. That would open up a whole new set of opportunities for Bukkit Plugin Developers.
Rollback Post to RevisionRollBack
Go ahead! Call me a nerd! Just keep in mind that I'll be laughing my ass off when you're collecting my garbage in 20 years!
I'll only say "cool!" if it means plug-ins on Vanilla. If not, I will be as mad as before with no plug-ins on my awesome Vanilla server.Well, pretty cool, I guess. Stil waitng for the answer to my question...
I'm just hearing about this. Worst news I've heard in a while. If they make things closed-source, all plugins will have to update any lower-level NMS code every single damn time there's a minor update, or alternatively wait for the bukkit devs to implement an API for it.
Judging by how incredibly fast they do it now (which is stupidly slow), this is going to cause issues. A lot of issues.
This sounds pretty damn great. I'd love to see Bukkit and vanilla MC SMP make a sweet little baby together. I mean let's face it plug ins for vanilla SMP servers would be the icing on the cake.
Well I read half of it and tbh couldn't be bothered reading the rest but if I'm correct does that mean some bukkit features will be implemented into the server files? And congratulations bukkit team I'm happy for you. I mean it
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHopefully that will have changed, but if they try to completely replace modding with a single API like the previous bukkit, and don't leave the possibility of directly making mods similar to how they are now (as a last resort, if the API provided is lacking some functionality), then I forsee a very large community of people who will refuse to update...
Also, I really hope that the API implementation does not impose any overhead on SSP. I only get a decent framerate as it is, and I'm a bit worried that they'll create something that works well for servers, but causes irregular framerates when it has to share the system with the client.
I hope it turns out well, but I'll remain sceptical until/unless I see good results.
CraftGuide, recipe viewer with a scrollbar! (Resizable window, too, if you prefer playing with a smaller GUI scale and are tired of GUIs only occupying a tiny square in the centre)
Rarity: OH IT IS ON!
Mojang join with Canary TOO!
I help out when I can.
I fail to see how this is going to "kill Minecraft". Seriously.
Bukkit is still going to be open source, and the old ways of accessing classes of Minecraft will continue until Mojang decides to use something other than Java for developing the game. What is going to be ruined?
The worst situtation is that Bukkit might be forked if the "community" doesn't like where Mojang takes that part of the modding community, so they decide to really push the open source nature of the project with a new team of Bukkit developers. That has happened with projects like Open Office, and the "right to fork" is always something available for any open source project like Bukkit. If you don't like the direction some resources like this are going, you can always do the fork yourself. If you lack the skills to make that fork, that isn't my problem or anybody else's.
Version 2.1 now updated for MC 1.6.2
Also, check out my minecraft items in my shop
CraftBukkit | Adventure Maps | RPG Map | AutoCraft | FalseBook | Towny | Economy
I don't think you understand what an API is. A closed source API didn't stop Blizzard's WoW community of modders for client side stuff. It didn't stop Elder Scrolls modders, Fallout, etc. A closed source API doesn't shut out modders. It's an API. It's purpose to to provide an controlled interface to developers, not shut them out.
.Net is a closed source API. So is all of DirectX. XNA is a closed source api also and thousands upon thousands of games are built on it.
An API is an API. I don't think you quite understand the purpose of an API.
Join My Server At: 122.58.84.237
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumJudging by how incredibly fast they do it now (which is stupidly slow), this is going to cause issues. A lot of issues.
Disapprove.
I hope bukkit will be main host for servers
-
View User Profile
-
View Posts
-
Send Message
Curse Premium