Why not release Bukkit as a patch to avoid DMCA conflict?

Discussion in 'Bukkit Discussion' started by pquiring, Oct 6, 2014.

Thread Status:
Not open for further replies.
  1. Offline

    pquiring

    Could Bukkit be released as a patch to the Minecraft server and therefore not violate DMCA?

    Basically take CraftBukkit.jar and the real MinecraftServer.jar and run some sort of binary 'diff' on it and then release the patch. Then end users get the patch run a binary type 'patch' command to create CraftBukkit.jar from their copy of MinecraftServer.jar.

    Of course diff and patch will not work since they are for text files, but you get the idea. Something could be created to generate a binary patch and then apply the patch.
     
  2. Offline

    mythbusterma

    pquiring

    Because the Bukkit project is dead.
     
  3. I guess you need people who really want to apply such technique, while...
    • 1.7.10 -> Spigot?
    • 1.8 -> Similar amount of work as with a full recode of all conflicting code?
    • People to continue with that approach need...
      • Not have have made a final decision to quit.
      • Not have something better in mind than Bukkit.
      • Not have their own thing going already.
      • Be somewhat keen on maintaining binary patching.
      • Access to the project.
    Unlikely to happen all at the same time for 1.8, if you ask me, but never know.
     
  4. Offline

    mythbusterma

    asofold

    It's more or less that the source code has been removed off of GitHub, and that nobody who worked on the project previously is still around, so yes, it's not going to happen. Unless, by some ungodly miracle, Dinnerbone actually writes 1.8 by himself *scoff scoff scoff*.
     
    AdamQpzm likes this.
  5. Thousands of people have the code, but binary patching isn't more simple than merging with actual code. The main problem should be the complexity of that task. Not sure if the DMCA would hit code stripped off the mc_server code though, but i am also not sure if the DMCA is actually striking, those things depend on if the involved parties will move or not.
     
    mythbusterma likes this.
  6. Offline

    mythbusterma

    asofold

    Fair enough, but my point is that the people with the code fall under one of these:
    1. Their code wasn't the most recent version before takedown, and binary patches would be impossible.
    2. They aren't motivated enough, or aren't involved with this project anymore
    3. They don't have the necessary technical skills to perform the binary patch

    Essentially what you said above.
     
  7. mythbusterma

    Yes, though the likelihood of having the latest CB beta jar isn't that small, though.
     
  8. Offline

    toothplck1

    Not to mention that CB's based in a partially deobfuscated minecraft server, with static mappings, to patch a vanilla minecraftserver.jar you would basically have to entirely rewrite CB every update, as the obfuscation is hella tight in there. Patch files in that manner would be near impossible to maintain, and near impossible to even get done before a new mc update comes out. Spigot only can do what they do because they are patching their slightly older version.
     
  9. Offline

    NeelixBFT

    I guess I find myself hard up to understand this whole ridiculous situation. If I got the chain of events right, first Bukkit staff goes into an uproar about EULA agreements from Mojang changing, then one senior staff member from Bukkit says something about shutting the project down, then Mojang comes out and says "oh did you guys forget, we own Bukkit its not yours to shut down" If thats the case that Bukkit is owned by Mojang, how in the HELL does a company get into a copyright dispute with itself? I mean, maybe I don't really understand the situation clearly enough, but it sounds kinda ridiculous.
     
  10. NeelixBFT No, not really. The staff didn't go in uproar about the EULA changes (of which there have not been any, by the way). The project lead made an announcement that the Bukkit project would cease development (as is the responsibility of a project lead, regardless of who actually made the decision), which was followed up by the announcement from Mojang. This was then followed by a DMCA takedown notice by Wolvereness, who contributed to the Bukkit project.
     
  11. Offline

    NeelixBFT

    Well, that sort of clears it up. But explain this to me if you feel inclined, as I'd like to understand the full picture in plain simple english.

    If Bukkit has been owned by Mojang for 2 years, and in a roundabout way Bukkit developers are under the employ of Mojang (if I'm correct so far), then I would presume this Wolvereness fellow was also under the employ of Mojang, which at least every company I've ever worked for, anything you produce in your capacity of an employee, anything as simple as an idea to improve the efficency of the staff in the cafeteria, or something as complicated as developing a java script, that produced material is intellectual property of the company you produced it for.. Which to me, makes me wonder what legal ground Wolvereness has to issue a DMCA takedown notice in the first place? Just because he collaborated to produce something doesn't make his portion of the contribution his property, right?
     
  12. Offline

    toothplck1

    I for one, and I assume the rest of us as well, never received a paycheck from mojang, nor did I ever recieve any sort of employee contract. From what I have gathered. They bought in secret. The name and the assets(website) of bukkit. They did not hire every contributor, nor did they buy every contributors code. Also. Responding on a phone is difficult. so forgive misplaced punctuation and random letters or typos. The editing capabilities on a touchscreen are like impossible.i
     
    JaguarJo likes this.
  13. Offline

    NeelixBFT

    I see. Now I understand, I can see why Bukkit staff are so P.O.'ed. Thank you.
     
Thread Status:
Not open for further replies.

Share This Page