I guess first, it goes without saying that the leave of absence I started back in mid-October to "re-prioritize my life" is over a bit earlier than the mid-December point I initially stated. Really, I guess I sort of caved when I hit the point realizing that the holidays at work are almost over, the semester is almost finished and a 1.8 version of Spigot and Craftbukkit are finally available for Minecraft. As such, I wanted to get our Minecraft server updated to this long awaited release as soon as safely possible. I say safely because this was a big, big update to the game. The changes made to it you can't immediately see just playing were far from trivial, and the extent of executive meddling and disenfranchised developers made this update extremely hard to do.
Back in September (and I made a previous entry covering this topic) the Bukkit team basically looked at how drastic this update was for Bukkit and collectively said, "nope." Dinnerbone, however, said "yup--I'll do it, faggots. We own you." Again, when Mojang brought on the Bukkit team back in 2011, they secretly agreed that acquiring their devs meant acquiring the Bukkit project altogether. This meant for nearly three years, Mojang was having an extensible server platform built for their game for free while Bukkit's contributors were blisfully unaware that Mojang owned the project.
Craftbukkit, let's face it, is a dead avenue. Spigot worked a great job updating the Bukkit API to 1.8 for the present, but the code is tainted now between the lead devs calling it quits and copyright issues regarding a contributor's code. In the long term, The Outpost will likely switch to the Sponge project which will hopefully succeed Bukkit. The Spigot team were clever, though. It is currently not legal (not that I actually the minutest ounce of a flying fuck about software piracy) to distribute compiled .jars using Wesley "Wolverness" Wolfe's code. It's isn't illegal, however, to distribute tools which download and compile the server client-side. It's neglibly a bit more tedious than downloading the actual server the way you used to be able to, but being able to update to 1.8 makes it worth learning a few new tricks.
So as I stay up late working on updating The Outpost to 1.8 (and am glad to come back to YouChew. Felt like so much longer than a month) I'd like to run over what you should expect in this 1.8 update. First off--Plugins WILL BREAK. What I'm offering up tonight when I restart the server with a shiny new Spigot 1.8 jar is essentially an "enhanced vanilla" version of Minecraft that currently lacks some of our more favorite plugins until I've tested them all out and am satisfied with their performance and compatibility. At the moment, this means no guns, no movecraft, no mob/pvp arena, no cannon's, no machines like the drill or Raildriver, no MCMMO. Yet. Maybe they'll come back. It depends as while I'm updating seeing what will still work and what won't. I don't want to purposefully put broken plugins on an infantile server platform while Spigot 1.8 grows. The key to going into this update that I wanted was stability over features. They can come later.
For the Creative players who frequent old_youchew_survival, you still have tools like WorldEdit and Asyncworldedit. However, because of some dependencies I'd prefer not to leave out to fully update to the newest version of WorldEdit, the new blocks 1.8 brings cannot be WorldEdit'ed in and must be placed by hand. I apologize for the inconvenience, but it was necessary to stay back a version to keep a plugin which hooks into our block logger that logs changes made to the world with WorldEdit. When it and asyncworldedit are updated (as asyncworldedit is a dependency of this plugin) I will then update to the newest WorldEdit.
At this point I'm rambling. I need to get some sleep and I have classes tomorrow. The main point is that YouChew's Minecraft server is now updated to 1.8. You can connect to it at the-outpost.me. If there's any immediate, glaring problems while playing I haven't outlined yet here then please let me know in the Minecraft thread itself! I'll resolve them as best I possibly can. Thanks for being patient with both Robotnikthingy and I. It's been a long wait to finally get our hands on a proper 1.8 server release that doesn't suck ballsack like Mojang's own, and I hope you enjoy it! Go tame a bunny! Go conquer an ocean monument! Make banners! New Doors! Armor stands! Ain't life grand?!
Back in September (and I made a previous entry covering this topic) the Bukkit team basically looked at how drastic this update was for Bukkit and collectively said, "nope." Dinnerbone, however, said "yup--I'll do it, faggots. We own you." Again, when Mojang brought on the Bukkit team back in 2011, they secretly agreed that acquiring their devs meant acquiring the Bukkit project altogether. This meant for nearly three years, Mojang was having an extensible server platform built for their game for free while Bukkit's contributors were blisfully unaware that Mojang owned the project.
Craftbukkit, let's face it, is a dead avenue. Spigot worked a great job updating the Bukkit API to 1.8 for the present, but the code is tainted now between the lead devs calling it quits and copyright issues regarding a contributor's code. In the long term, The Outpost will likely switch to the Sponge project which will hopefully succeed Bukkit. The Spigot team were clever, though. It is currently not legal (not that I actually the minutest ounce of a flying fuck about software piracy) to distribute compiled .jars using Wesley "Wolverness" Wolfe's code. It's isn't illegal, however, to distribute tools which download and compile the server client-side. It's neglibly a bit more tedious than downloading the actual server the way you used to be able to, but being able to update to 1.8 makes it worth learning a few new tricks.
So as I stay up late working on updating The Outpost to 1.8 (and am glad to come back to YouChew. Felt like so much longer than a month) I'd like to run over what you should expect in this 1.8 update. First off--Plugins WILL BREAK. What I'm offering up tonight when I restart the server with a shiny new Spigot 1.8 jar is essentially an "enhanced vanilla" version of Minecraft that currently lacks some of our more favorite plugins until I've tested them all out and am satisfied with their performance and compatibility. At the moment, this means no guns, no movecraft, no mob/pvp arena, no cannon's, no machines like the drill or Raildriver, no MCMMO. Yet. Maybe they'll come back. It depends as while I'm updating seeing what will still work and what won't. I don't want to purposefully put broken plugins on an infantile server platform while Spigot 1.8 grows. The key to going into this update that I wanted was stability over features. They can come later.
For the Creative players who frequent old_youchew_survival, you still have tools like WorldEdit and Asyncworldedit. However, because of some dependencies I'd prefer not to leave out to fully update to the newest version of WorldEdit, the new blocks 1.8 brings cannot be WorldEdit'ed in and must be placed by hand. I apologize for the inconvenience, but it was necessary to stay back a version to keep a plugin which hooks into our block logger that logs changes made to the world with WorldEdit. When it and asyncworldedit are updated (as asyncworldedit is a dependency of this plugin) I will then update to the newest WorldEdit.
At this point I'm rambling. I need to get some sleep and I have classes tomorrow. The main point is that YouChew's Minecraft server is now updated to 1.8. You can connect to it at the-outpost.me. If there's any immediate, glaring problems while playing I haven't outlined yet here then please let me know in the Minecraft thread itself! I'll resolve them as best I possibly can. Thanks for being patient with both Robotnikthingy and I. It's been a long wait to finally get our hands on a proper 1.8 server release that doesn't suck ballsack like Mojang's own, and I hope you enjoy it! Go tame a bunny! Go conquer an ocean monument! Make banners! New Doors! Armor stands! Ain't life grand?!