Milestone 0.1 is due in 9 days, but I think we'll be ready for a release before then. Just some bug squashing to do, which could be helped along by anyone who wants to do so.
I am going to post this here because it's the most immediately relevant topic for it, but I may end up starting a new topic entirely if it merits it. This is, I feel, something every person administrating a modded Minecraft server should check out and think about.
Earlier this week, in the land of the Almighty Bukkit: http://t.co/7Od0X5og
If that's too much of a read for you, let me summarize: LexManos and CPW made one final, last-ditch attempt at working for a copacetic solution for Forge and bukkit. And they got shut down, starting with this gem as an opener:
That's the bukkit team telling the Forge crew -- and by extension, every single one of us running a server with the mods made possible by Forge and FML -- that they do not consider us at all an important demographic. They don't care. They're too big/important/ineffable/<insert arrogant jerkish posturing adjective here> to give a damn about us, our communities, and the development tools that make them possible. That to them so much as asking for a simple directory of how they handle their mappings so a translation codex between bukkit and MCP could be nailed down once and for all is just too much and that we should be grateful for what scraps they give us.
They've also made it fairly clear that they see Forge -- and modded Minecraft by extension -- as a threat to their project, and in that circumstance they're going to bunker up rather than come to a mutually beneficial solution.
So what do we do?
First off, we stop asking people to handle bukkit ports of our favorite mods, as well as the forge framework itself. Bukkit wants nothing to do with modded Minecraft, they've broadcast this loud and clear, so we should wash our hands of them. There will be a point at which these unofficial ports will all fall down flat and go boom; that almost happened already and was salvaged by some other community members for this particular go-round. We need and deserve a better solution, one that doesn't depend on somebody outside of the projects to "save the day", and we should work towards attaining that.
Secondly, we should support and assist the Forge team in their endeavors to provide the kinds of server management functionality we're going to need now that it's obvious a compromise will never be reached. Let your voice be heard in threads like this one about what functionality you're going to need. Donate to the Forge mod developers, because other than our thanks that's all they're getting for doing this and they have bills to pay too (I'd post links but it's a bit hard retrieving them on my netbook here, so if somebody could provide those I'd greatly appreciate it) and they often don't get the spotlight for their silent work in the background. Stay on top of your favorite mods and their developers and assist them where possible or necessary in having mods compatible natively with the kinds of server management tools we'll be seeing coming in the near future.
And lastly, don't waste time or resources further trying to engage bukkit on this. Their stance has been laid bare: they wish to be known for their past accomplishments rather than for building bridges into the future. The paradigm of server and client in Minecraft changed in 1.3.2 and is certain to continue to evolve; bukkit has decided to remain as they are, content in being the big fish they see themselves as. I personally think they're merely fossilizing; nobody runs to the museum to shout at dinosaurs at how they're stupid fossils, and so we shouldn't go over there and do that either. Let's channel our energies as server admins and lovers of modded Minecraft towards making something new instead. Let future demographics judge these events.
Murum aries attigit. Let's "win" by supporting the forward-looking product here and cultivating the better community. They can keep their old server-only solution and their "upper hand". Maybe if we're successful enough we can even make them regret that stance, but at that point we'll all be running fully-integrated modded servers with the protections we all want and the gameplay we all enjoy, and with no more of these backroom shenanigans making the whole setup so fragile.
Edit: Added a quickie screenshot of the meat of the bukkit post, just in case it happens to get "misplaced" once somebody figures out how bad it looks.
I am going to post this here because it's the most immediately relevant topic for it, but I may end up starting a new topic entirely if it merits it. This is, I feel, something every person administrating a modded Minecraft server should check out and think about.
Earlier this week, in the land of the Almighty Bukkit: http://t.co/7Od0X5og
If that's too much of a read for you, let me summarize: LexManos and CPW made one final, last-ditch attempt at working for a copacetic solution for Forge and bukkit. And they got shut down, starting with this gem as an opener:
That's the bukkit team telling the Forge crew -- and by extension, every single one of us running a server with the mods made possible by Forge and FML -- that they do not consider us at all an important demographic. They don't care. They're too big/important/ineffable/<insert arrogant jerkish posturing adjective here> to give a damn about us, our communities, and the development tools that make them possible. That to them so much as asking for a simple directory of how they handle their mappings so a translation codex between bukkit and MCP could be nailed down once and for all is just too much and that we should be grateful for what scraps they give us.
They've also made it fairly clear that they see Forge -- and modded Minecraft by extension -- as a threat to their project, and in that circumstance they're going to bunker up rather than come to a mutually beneficial solution.
So what do we do?
First off, we stop asking people to handle bukkit ports of our favorite mods, as well as the forge framework itself. Bukkit wants nothing to do with modded Minecraft, they've broadcast this loud and clear, so we should wash our hands of them. There will be a point at which these unofficial ports will all fall down flat and go boom; that almost happened already and was salvaged by some other community members for this particular go-round. We need and deserve a better solution, one that doesn't depend on somebody outside of the projects to "save the day", and we should work towards attaining that.
Secondly, we should support and assist the Forge team in their endeavors to provide the kinds of server management functionality we're going to need now that it's obvious a compromise will never be reached. Let your voice be heard in threads like this one about what functionality you're going to need. Donate to the Forge mod developers, because other than our thanks that's all they're getting for doing this and they have bills to pay too (I'd post links but it's a bit hard retrieving them on my netbook here, so if somebody could provide those I'd greatly appreciate it) and they often don't get the spotlight for their silent work in the background. Stay on top of your favorite mods and their developers and assist them where possible or necessary in having mods compatible natively with the kinds of server management tools we'll be seeing coming in the near future.
And lastly, don't waste time or resources further trying to engage bukkit on this. Their stance has been laid bare: they wish to be known for their past accomplishments rather than for building bridges into the future. The paradigm of server and client in Minecraft changed in 1.3.2 and is certain to continue to evolve; bukkit has decided to remain as they are, content in being the big fish they see themselves as. I personally think they're merely fossilizing; nobody runs to the museum to shout at dinosaurs at how they're stupid fossils, and so we shouldn't go over there and do that either. Let's channel our energies as server admins and lovers of modded Minecraft towards making something new instead. Let future demographics judge these events.
Murum aries attigit. Let's "win" by supporting the forward-looking product here and cultivating the better community. They can keep their old server-only solution and their "upper hand". Maybe if we're successful enough we can even make them regret that stance, but at that point we'll all be running fully-integrated modded servers with the protections we all want and the gameplay we all enjoy, and with no more of these backroom shenanigans making the whole setup so fragile.
Edit: Added a quickie screenshot of the meat of the bukkit post, just in case it happens to get "misplaced" once somebody figures out how bad it looks.
I am going to post this here because it's the most immediately relevant topic for it, but I may end up starting a new topic entirely if it merits it. This is, I feel, something every person administrating a modded Minecraft server should check out and think about.
Earlier this week, in the land of the Almighty Bukkit: http://t.co/7Od0X5og
If that's too much of a read for you, let me summarize: LexManos and CPW made one final, last-ditch attempt at working for a copacetic solution for Forge and bukkit. And they got shut down, starting with this gem as an opener:
That's the bukkit team telling the Forge crew -- and by extension, every single one of us running a server with the mods made possible by Forge and FML -- that they do not consider us at all an important demographic. They don't care. They're too big/important/ineffable/<insert arrogant jerkish posturing adjective here> to give a damn about us, our communities, and the development tools that make them possible. That to them so much as asking for a simple directory of how they handle their mappings so a translation codex between bukkit and MCP could be nailed down once and for all is just too much and that we should be grateful for what scraps they give us.
They've also made it fairly clear that they see Forge -- and modded Minecraft by extension -- as a threat to their project, and in that circumstance they're going to bunker up rather than come to a mutually beneficial solution.
So what do we do?
First off, we stop asking people to handle bukkit ports of our favorite mods, as well as the forge framework itself. Bukkit wants nothing to do with modded Minecraft, they've broadcast this loud and clear, so we should wash our hands of them. There will be a point at which these unofficial ports will all fall down flat and go boom; that almost happened already and was salvaged by some other community members for this particular go-round. We need and deserve a better solution, one that doesn't depend on somebody outside of the projects to "save the day", and we should work towards attaining that.
Secondly, we should support and assist the Forge team in their endeavors to provide the kinds of server management functionality we're going to need now that it's obvious a compromise will never be reached. Let your voice be heard in threads like this one about what functionality you're going to need. Donate to the Forge mod developers, because other than our thanks that's all they're getting for doing this and they have bills to pay too (I'd post links but it's a bit hard retrieving them on my netbook here, so if somebody could provide those I'd greatly appreciate it) and they often don't get the spotlight for their silent work in the background. Stay on top of your favorite mods and their developers and assist them where possible or necessary in having mods compatible natively with the kinds of server management tools we'll be seeing coming in the near future.
And lastly, don't waste time or resources further trying to engage bukkit on this. Their stance has been laid bare: they wish to be known for their past accomplishments rather than for building bridges into the future. The paradigm of server and client in Minecraft changed in 1.3.2 and is certain to continue to evolve; bukkit has decided to remain as they are, content in being the big fish they see themselves as. I personally think they're merely fossilizing; nobody runs to the museum to shout at dinosaurs at how they're stupid fossils, and so we shouldn't go over there and do that either. Let's channel our energies as server admins and lovers of modded Minecraft towards making something new instead. Let future demographics judge these events.
Murum aries attigit. Let's "win" by supporting the forward-looking product here and cultivating the better community. They can keep their old server-only solution and their "upper hand". Maybe if we're successful enough we can even make them regret that stance, but at that point we'll all be running fully-integrated modded servers with the protections we all want and the gameplay we all enjoy, and with no more of these backroom shenanigans making the whole setup so fragile.
Edit: Added a quickie screenshot of the meat of the bukkit post, just in case it happens to get "misplaced" once somebody figures out how bad it looks.