Scratch

-Eyetwitch- WHO ARE THE YOGSCAST!?!? xD I'm rather annoyed about how I don't know who they are. It's quite embarrassing. xD

ImagineIt wrote:

schusteralex2 wrote:

VERY important question: All my controls are set to Button one and I can't change them, and I can't move, hit or anything. What can I do to fix this 

How can you not change them? Press escape, options and then controls.

I did that, it just keeps only showing button 1 -_-

imnotbob wrote:

fireheartocean wrote:

-Eyetwitch- WHO ARE THE YOGSCAST!?!? xD I'm rather annoyed about how I don't know who they are. It's quite embarrassing. xD

Minecrafters who post videos on YouTube (rather hilarious, but they swear)

Aha. Thanks for the information.    I'd watch one of their videos, but I'd have to turn my sound on and my parents would most likely tell me to turn it off if it had swears in it. 

meowmeow55 wrote:

So, most of you probably know by now that the Bukkit team has been hired by Mojang and are now hard at work making an API for Minecraft. (If you don't, you really ought to be keeping up with this sort of stuff. Read here and here for the "official" news. You'll see why I used quotes around that word in a little while.)

So, that's cool and all, right? Mojang makes an official API, plugins can be updated as soon as an update comes out and not have to wait for a mod API to update, and everybody's happy. Right? Wrong! obvious hint is obvious

First of all, it's going to be heck porting all the Bukkit plugins over to the new Mojang API. The new API will be nothing like Bukkit, as the Bukkit team can't just "move" their project into Minecraft. "Why?" you ask. "Bukkit was such an awesome project! They're sure not gonna chuck it out!" Well, guess what? They have to. The Bukkit API is licensed under the GNU Public License (GPL), which disallows use of the code in closed-source projects unless everyone who contributed to it gives permission. But there's no way all these people are gonna be giving permission. It's just not feasible.

Not to mention CraftBukkit (the server part of the Bukkit project) is "technically" illegal, since it includes the copyrighted Minecraft server code. So, after a year of looking the other way, Mojang just went ahead and hired the Bukkit folks, leaving this issue in the dust.

Oh, and there most likely won't be a Bukkit compatibility plugin for this new API, either, making it even more painful.

So, once you've read those two posts I linked above, now read the Spout newspost on the same subject. Now you've got a whole different view from the Bukkit and Mojang folks (pretty much the same one I'm trying to convey), and citations to back it up (so if you find yourself contesting what I'm saying, go see if Afforess mentioned it there, and click on the link). Bukkit's a zombie now; it'll be maintained for a little while, but once the Mojang API is up and running, bam! out Bukkit goes. (Unless someone decides to pick it up, of course, but that's not likely.)

Now what does Spout have to do with this? Well, just a few months ago, the Spout team decided to start writing their own Minecraft server from scratch (well, forked from the Glowstone project, but that was from scratch too). This means no Notch code to have legal issues with! (The team gets all their info from Minecraft Wiki documentation and protocol specs, so they're not even looking at the source code.) Eventually, they decided that all the Minecraft-related API and protocol/mobs/etc. would go into a plugin dubbed Vanilla (to keep the trademarked name "Minecraft" out of it), and Spout would be a voxel generic server that anyone could port any game to. And they're actually getting somewhere with it!

But enough ranting about Spout. The point is, they are actually going to have a BukkitBridge plugin, so the Spout server will be a good option for those who wish to easily transfer their server over once Bukkit goes under.

Also, this new API will be closed source, of course, since Minecraft itself is. Not a big deal, you think? Take a look at the list of Bukkit contributors again. (Oh yeah, and here's the CraftBukkit contributors too.) Bukkit wouldn't be even close to what it is today without the help of those people. With the new API being closed source, all that help is gone. The Bukkit team did turn down some pull requests for strange reasons, but at least there was a significant amount of help from the community. But when you have a closed-source project, you have no outside assistance. If you're a plugin dev and you find a bug in the new API, you won't be able to just report it on Github and/or fix it yourself. That had the bug fixed in probably under a week. Now, you will have to rely on a probably not-frequently-checked ticket system (look at this!) and maybe wait months for your bug to be fixed!

So, to sum it all up (i.e. TL;DR  ): The transfer to the new Minecraft server API from Bukkit is going to be far from painless. If any of you were around for the Hey0 to Bukkit transition (not me!  ), you know what I mean; it's going to be much the same thing. The Bukkit team is starting over because of licensing issues, and the way the API is designed is completely and wholly their decision (which could be good or bad depending on how you look at it).  I highly recommend reading at least a smattering of the comments on the Spout and/or Bukkit newsposts, and also the licensing discussion thread on the Spout forum if you want to go even deeper into the subject. (There are probably numerous other places to look, most likely in the Bukkit forum, but I'll leave it up to you to find those. Well, okay, here's another thread.)

Anyways, apologies for the excruciatingly long-winded post! Just really felt like I needed to get this side of the story out there. Personally, I'm probably gonna go with Spout when it's released. How about you?

you really went to town on this bukkit rant man :]

agscratcher wrote:

meowmeow55 wrote:

So, most of you probably know by now that the Bukkit team has been hired by Mojang and are now hard at work making an API for Minecraft. (If you don't, you really ought to be keeping up with this sort of stuff. Read here and here for the "official" news. You'll see why I used quotes around that word in a little while.)

So, that's cool and all, right? Mojang makes an official API, plugins can be updated as soon as an update comes out and not have to wait for a mod API to update, and everybody's happy. Right? Wrong! obvious hint is obvious

First of all, it's going to be heck porting all the Bukkit plugins over to the new Mojang API. The new API will be nothing like Bukkit, as the Bukkit team can't just "move" their project into Minecraft. "Why?" you ask. "Bukkit was such an awesome project! They're sure not gonna chuck it out!" Well, guess what? They have to. The Bukkit API is licensed under the GNU Public License (GPL), which disallows use of the code in closed-source projects unless everyone who contributed to it gives permission. But there's no way all these people are gonna be giving permission. It's just not feasible.

Not to mention CraftBukkit (the server part of the Bukkit project) is "technically" illegal, since it includes the copyrighted Minecraft server code. So, after a year of looking the other way, Mojang just went ahead and hired the Bukkit folks, leaving this issue in the dust.

Oh, and there most likely won't be a Bukkit compatibility plugin for this new API, either, making it even more painful.

So, once you've read those two posts I linked above, now read the Spout newspost on the same subject. Now you've got a whole different view from the Bukkit and Mojang folks (pretty much the same one I'm trying to convey), and citations to back it up (so if you find yourself contesting what I'm saying, go see if Afforess mentioned it there, and click on the link). Bukkit's a zombie now; it'll be maintained for a little while, but once the Mojang API is up and running, bam! out Bukkit goes. (Unless someone decides to pick it up, of course, but that's not likely.)

Now what does Spout have to do with this? Well, just a few months ago, the Spout team decided to start writing their own Minecraft server from scratch (well, forked from the Glowstone project, but that was from scratch too). This means no Notch code to have legal issues with! (The team gets all their info from Minecraft Wiki documentation and protocol specs, so they're not even looking at the source code.) Eventually, they decided that all the Minecraft-related API and protocol/mobs/etc. would go into a plugin dubbed Vanilla (to keep the trademarked name "Minecraft" out of it), and Spout would be a voxel generic server that anyone could port any game to. And they're actually getting somewhere with it!

But enough ranting about Spout. The point is, they are actually going to have a BukkitBridge plugin, so the Spout server will be a good option for those who wish to easily transfer their server over once Bukkit goes under.

Also, this new API will be closed source, of course, since Minecraft itself is. Not a big deal, you think? Take a look at the list of Bukkit contributors again. (Oh yeah, and here's the CraftBukkit contributors too.) Bukkit wouldn't be even close to what it is today without the help of those people. With the new API being closed source, all that help is gone. The Bukkit team did turn down some pull requests for strange reasons, but at least there was a significant amount of help from the community. But when you have a closed-source project, you have no outside assistance. If you're a plugin dev and you find a bug in the new API, you won't be able to just report it on Github and/or fix it yourself. That had the bug fixed in probably under a week. Now, you will have to rely on a probably not-frequently-checked ticket system (look at this!) and maybe wait months for your bug to be fixed!

So, to sum it all up (i.e. TL;DR  ): The transfer to the new Minecraft server API from Bukkit is going to be far from painless. If any of you were around for the Hey0 to Bukkit transition (not me!  ), you know what I mean; it's going to be much the same thing. The Bukkit team is starting over because of licensing issues, and the way the API is designed is completely and wholly their decision (which could be good or bad depending on how you look at it).  I highly recommend reading at least a smattering of the comments on the Spout and/or Bukkit newsposts, and also the licensing discussion thread on the Spout forum if you want to go even deeper into the subject. (There are probably numerous other places to look, most likely in the Bukkit forum, but I'll leave it up to you to find those. Well, okay, here's another thread.)

Anyways, apologies for the excruciatingly long-winded post! Just really felt like I needed to get this side of the story out there. Personally, I'm probably gonna go with Spout when it's released. How about you?

I'm surprised you didn't reach the length limit.

The length limit is actually much longer, though I believe the longest technical term ever took something of 7 times that once when someone posted it.

samtwheels wrote:

soupoftomato wrote:

agscratcher wrote:

I'm surprised you didn't reach the length limit.

The length limit is actually much longer, though I believe the longest technical term ever took something of 7 times that once when someone posted it.

Why are you quoting it?

Is fun.

samtwheels wrote:

I'm playing SkyBlock now.

SkyBlock mainly consists of the player mindlessly mining cobblestone from a generator.

imnotbob wrote:

fireheartocean wrote:

-Eyetwitch- WHO ARE THE YOGSCAST!?!? xD I'm rather annoyed about how I don't know who they are. It's quite embarrassing. xD

Minecrafters who post videos on YouTube (rather hilarious, but they swear(Like, alot.))

slinger wrote:

samtwheels wrote:

I'm playing SkyBlock now.

What is "SkyBlock"?
Nevermind, I found it. It looks cool 

I got to the nether in it 

I have the most amazing cobblestone generator on it, I worked for ages on it. So basically you stand where the cobblestone spawns, and just look down and keep breaking (there are protection rails so you don't go in the lava). Since you're inside it, you very rarely lose stone to the lava, but if it falls in the other directions, it'll go into a waterway system, which send all the lost stone to a collection point in front of the generator. It also has a furnace under the spawned stone, so you can hold down the mouse to break the cobbie without breaking the block beneath it.

Last edited by werdna123 (2012-03-25 08:30:59)

16Skittles wrote:

WindowsExplorer wrote:

slinger wrote:

What is "SkyBlock"?
Nevermind, I found it. It looks cool 

I got to the nether in it 

how? There's a small amount of lava, not enough!

Reuse.

@werdna: My cobble stone gen is very simple, and GUARENTEED not to lose any.

WindowsExplorer wrote:

16Skittles wrote:

WindowsExplorer wrote:

I got to the nether in it 

how? There's a small amount of lava, not enough!

Reuse.

@werdna: My cobble stone gen is very simple, and GUARENTEED not to lose any.

How does it work?

Agg725 wrote:

Lol my brother plays minecraft. It looks really fun. I'm even working on a "Minecraft Survival Guide" XD

If your writing a guide, you should buy it. Experience is better than watching a brother.