Uh... what's the question? Why am I comparing Microsoft and Mojang, and for what reasons? Why am I comparing two numbers, which may or may not be in relation to potential version numbers for the game? This seems rather pointless.
I'm not sure what exactly is going on with these companies, but from what I see Minecraft is shutting down Bukkit and Spigot as a way to shutdown P2W servers, that's their scapegoat for really just wanting to promote minecraft realms imo. If I'm wrong someone just tell me because this things over my head with all this legal crap.
You could not be any less correct on the subject. You could have written a recipe for carrot cake and been closer to the mark. Mojang isn't trying to shut anybody down - quite the opposite - and absolutely nothing in this entire situation has anything to do with pay-to-win servers.
Ayup. This guy has "Future Disgruntled Employee" written all over him. I wouldn't touch him with a 39.5 foot pole.
He's the kind of person who, the second he was fired or laid off from a company, a security guard would have to escort him away from his computer, because he absolutely would have a malicious backdoor in his code that he'd fire off on his way out.
Undoubted this guy has no idea what he has caused. Witch hunts may be forbidden among the web nor do I support such, but with a sized community of that Minecraft has, you ask for trouble on an large scale pulling things like this for no reason other than some butt-hurt reason and greed is all I see. Hopefully things can go by peacefully, but of all things, I do not really such happening so easy.
That's the unfortunate thing about all of this. Mojang acted in good faith for years, allowing licensing and redistribution of a community project that knowingly redistributed their server jar, of which they had the complete authority to shut down at any time. After CraftBukkit was bought from Curse (which didn't shut down the project either, even though they as a company were liable for the illegal redistribution of code copyrighted to Mojang), complete legal protection was given to the project. Due to licensing issues with the content contributors, was there still a grey area? Absolutely, but status quo was remained in check, and even after EvilSeph left Mojang under less-than-ideal circumstances, nobody messed with that status quo because it benefits nobody.
Well, now there is someone to benefit: Wolfe announced his terms, and that was that nobody from here on out can redistribute his code contributions unless the Mojang server code becomes open source. The status quo was broken over not a moral or ethical argument, but over a childish manifesto. Any legitimate arguments that he could have had are just out the window, and one that opens the door to copycats who agree with him who also contributed to Spigot or Bukkit. Once one person tries to pull the rug out on the operation that has always, from day one, operated illegally but under good faith from all parties, by can't more people try the same?
Unless, of course, the claim is crushed by lawyers doing lawyery things, and chills the mood on throwing up claims. It'll be interesting to see what happens from here.
Unfortunately, Spigot also had a claim made against them. There's no good will involved if you're burning every bridge on your way out of the community. One can make some type of a retribution case out of Mojang not revealing to the greater Bukkit team their ownership of the project, but there's no excuse for filing claims against fellow plugin developers right out of the blue.
From the looks of the DMCA request, it looks like one of the Bukkit devs is saying that because CraftBukkit contains some Minecraft server information, the code contains information copyrighted by him without permission. I might be reading that wrong though.
But it looks like Mojang isn't shutting it down, at worst they will just need to work around and remove that developer's code, get permission to use it, or take it to court.
You got it right. Wolvereness filed a DMCA copyright claim (with no indications of there being any talks with Mojang) over believed incompatibilities with Mojang's ownership of Bukkit and how he had originally submitted that code in the GPL license. In all honesty, filing a copyright claim immediately a project that was going to close down is brought back on life support sounds like he's throwing nails where instead private discussion should have been had instead. Considering Jeb claims that this was sudden and without all his knowledge, I'd toss this into the same spite pile that EvilSeph's recent unfounded allegations against Mojang's EULA policies went.
I do like the transition that occured at some point, when the Plugin API - of which most have always had the wrong ideas about in what it is to its implementation and development - became less of a symbol of what could be, and more a symbol of, "Oh my god, Mojang is going to ruin everything by forcing modders and plugin makers to put in work for future compatibility". It seems to be a much more prevalent view, and I for the life of me can't understand why. It's never one from the actual plugin developers, but rather, fans being upset for them.
But then again, this topic is based off of the premise that 'If something bad happens that I have no direct role in, will more bad things happen that I also won't have any role in?' which is a bit silly. It's an odd mixture of doomsaying mixed with being upset at what other people may do in regards to that doomsaying. "If everything goes wrong, and the very worst is assumed in absolute, what will happen?!" Well, an unideal situation, that's what.
Which is why I questioned what was the non-mojang bukkit team developing for the past 2 years? It sounds like Mojang was using them as free development, which is super shady dealings.
That's a highly accusatory way of looking at the situation. Mojang had direct ownership of the project, but because of that, they also not only then provided blanket legal protection over it - so that whatever the hell EvilSeph was claiming would most certainly not be the case - but they also allowed the project to go on undisturbed for years. The fact that nobody even knew about the ownership should go to show that Mojang didn't sully up a community endeavor. I know of plenty of companies that would have tried to reach out and overmanage something like that.
Bukkit was from the community, for the community, and EvilSeph and his partner developers were more than happy to work on it as if it were their baby. It's just that now EvilSeph got bored of it, attempted to hit the ejector seat by blaming Mojang for a nonsense situation that he had no reason not to know about, and now Grum and Dinnerbone have to step in to officially unofficially support the project just because of it. Not that it's too much of a problem; them having the insight of code changes as they occur in real time, and having the full unobfuscated source code as a base should do nothing but help the project in the long run.
I think it's stupid. When the Nether was first being developed, Zombie Pigmen were originally going to have blood on them, instead of whatever they have on them now. Notch himself said he didn't want Minecraft to have blood in it. Seems like it's a shame to ruin something that someone already worked to do.
Wow someone made a thread about missing void fog. :/ wat.
Someone made a thread angry at Notch when he gave pigs snouts, saying that the 3D snouts were ruining a part of the game's charm and selling out. Ain't no change goes unhated around here.
Are you kidding ? Forgetting to switdch to the proper version is a very easy mistake...
It's an easy mistake to make, but also one that can be very easily prepared for. If several players are using an account, or if mods are being used on one or more profiles, then I have no sympathy for those without the foresight to back up their save files regularly. When it comes to PC gaming, and especially when it comes to messing with mods and updates on PC games, backing up save files is a necessity, and if that's a hard learned lesson, so be it.
I still stand by my original premise, however: Going back in time with updates on any game has never been a sound idea, and always presents some challenges, and ones developers are unlikely to fix because, at the end of the day, it isn't really their problem. Players choose to roll back the updates on existing save files from more recent versions of the game, and players need to be self-aware of their actions any time game data is changed like that.
0
1
You could not be any less correct on the subject. You could have written a recipe for carrot cake and been closer to the mark. Mojang isn't trying to shut anybody down - quite the opposite - and absolutely nothing in this entire situation has anything to do with pay-to-win servers.
0
If we are going to talk about multiple issues, then, which was it that the claim was filed for?
0
He's the kind of person who, the second he was fired or laid off from a company, a security guard would have to escort him away from his computer, because he absolutely would have a malicious backdoor in his code that he'd fire off on his way out.
0
1
That's the unfortunate thing about all of this. Mojang acted in good faith for years, allowing licensing and redistribution of a community project that knowingly redistributed their server jar, of which they had the complete authority to shut down at any time. After CraftBukkit was bought from Curse (which didn't shut down the project either, even though they as a company were liable for the illegal redistribution of code copyrighted to Mojang), complete legal protection was given to the project. Due to licensing issues with the content contributors, was there still a grey area? Absolutely, but status quo was remained in check, and even after EvilSeph left Mojang under less-than-ideal circumstances, nobody messed with that status quo because it benefits nobody.
Well, now there is someone to benefit: Wolfe announced his terms, and that was that nobody from here on out can redistribute his code contributions unless the Mojang server code becomes open source. The status quo was broken over not a moral or ethical argument, but over a childish manifesto. Any legitimate arguments that he could have had are just out the window, and one that opens the door to copycats who agree with him who also contributed to Spigot or Bukkit. Once one person tries to pull the rug out on the operation that has always, from day one, operated illegally but under good faith from all parties, by can't more people try the same?
Unless, of course, the claim is crushed by lawyers doing lawyery things, and chills the mood on throwing up claims. It'll be interesting to see what happens from here.
1
1
You got it right. Wolvereness filed a DMCA copyright claim (with no indications of there being any talks with Mojang) over believed incompatibilities with Mojang's ownership of Bukkit and how he had originally submitted that code in the GPL license. In all honesty, filing a copyright claim immediately a project that was going to close down is brought back on life support sounds like he's throwing nails where instead private discussion should have been had instead. Considering Jeb claims that this was sudden and without all his knowledge, I'd toss this into the same spite pile that EvilSeph's recent unfounded allegations against Mojang's EULA policies went.
0
1
0
But then again, this topic is based off of the premise that 'If something bad happens that I have no direct role in, will more bad things happen that I also won't have any role in?' which is a bit silly. It's an odd mixture of doomsaying mixed with being upset at what other people may do in regards to that doomsaying. "If everything goes wrong, and the very worst is assumed in absolute, what will happen?!" Well, an unideal situation, that's what.
1
That's a highly accusatory way of looking at the situation. Mojang had direct ownership of the project, but because of that, they also not only then provided blanket legal protection over it - so that whatever the hell EvilSeph was claiming would most certainly not be the case - but they also allowed the project to go on undisturbed for years. The fact that nobody even knew about the ownership should go to show that Mojang didn't sully up a community endeavor. I know of plenty of companies that would have tried to reach out and overmanage something like that.
Bukkit was from the community, for the community, and EvilSeph and his partner developers were more than happy to work on it as if it were their baby. It's just that now EvilSeph got bored of it, attempted to hit the ejector seat by blaming Mojang for a nonsense situation that he had no reason not to know about, and now Grum and Dinnerbone have to step in to officially unofficially support the project just because of it. Not that it's too much of a problem; them having the insight of code changes as they occur in real time, and having the full unobfuscated source code as a base should do nothing but help the project in the long run.
2
I'm sure even Notch can appreciate a good joke.
4
Someone made a thread angry at Notch when he gave pigs snouts, saying that the 3D snouts were ruining a part of the game's charm and selling out. Ain't no change goes unhated around here.
0
It's an easy mistake to make, but also one that can be very easily prepared for. If several players are using an account, or if mods are being used on one or more profiles, then I have no sympathy for those without the foresight to back up their save files regularly. When it comes to PC gaming, and especially when it comes to messing with mods and updates on PC games, backing up save files is a necessity, and if that's a hard learned lesson, so be it.
I still stand by my original premise, however: Going back in time with updates on any game has never been a sound idea, and always presents some challenges, and ones developers are unlikely to fix because, at the end of the day, it isn't really their problem. Players choose to roll back the updates on existing save files from more recent versions of the game, and players need to be self-aware of their actions any time game data is changed like that.