MCP License Violation

[caoimhebyrne]

Your project is in active violation of the MCP license. You are not allowed to distribute the Minecraft source in any way as stated in the license

The license:

License and terms of use.
=========================

No warranties. If MCP does not work for you, or causes any damage, it's your problem. Use it at own risk.

You are allowed to:
- Use MCP to decompile the Minecraft client and server jar files.
- Use the decompiled source code to create mods for Minecraft.
- Recompile modified versions of Minecraft.
- Reobfuscate the classes of your mod for Minecraft.

You are NOT allowed to:
- Use MCP to do anything that violated Mojangs terms of use for Minecraft.
- Release Minecraft versions or modifications that allow you to play without having bought Minecraft from Mojang.
- Release modified or unmodified versions of MCP anywhere.
- Use any of MCPs scripts, tools or data files without explicit written permission.
- Make money with anything based on MCP (excluding Minecraft mods created by using MCP).
- Use MCP to create clients that are used for griefing or exploiting server bugs.
- Release the decompiled source code of Minecraft in any way.

Tagging relevant people: @SeargeDP

[caoimhebyrne]

You are also in violation of the Optifine license, which doesn't specify a license. If a project does not specify a license, it is known as "All Rights Reserved". I advise you to remove this repository yourself to avoid legal issues :-)

[OxideWaveLength]

I'm aware of the current violations of the project and I am working on a solution for it

[caoimhebyrne]

These are quite serious, the project should not have been open sourced in the first place. As an alternative, you can use something like mixins. https://github.com/SpongePowered/Mixin

[OxideWaveLength]

The solution I'm working on involves diff files and does not redistribute any of minecrafts or optifines source code

[stpidgamers]

shove that fucking license up ur ass and get gud

[josephworks]

LMAO didn't expect that

[stpidgamers]

These are quite serious, the project should not have been open sourced in the first place. As an alternative, you can use something like mixins. https://github.com/SpongePowered/Mixin
fuck mixins
they bad

[caoimhebyrne]

These are quite serious, the project should not have been open sourced in the first place. As an alternative, you can use something like mixins. https://github.com/SpongePowered/Mixin
fuck mixins
they bad

I think using mixins is better than a potential DMCA on your project, don't you?
You can't say you don't like mixins when I can make a very good assumption that you actually haven't used mixins, and that you probably know nothing about respect :)

[josephworks]

Yeah, mixins kinda really suck. Mine as well do a patch based dev side system like paper.

I'd personally take a dmca rather than add mixins to my project.

[OxideWaveLength]

You're not really risking any DMCA with the patch system, it's been tested and used before. Optifine uses them for their installation, for example. And Spigot does too, as pointed out by @josephworks.

This repository is probably not going to stay, a new one will be created and old users redirected there, which seems like the best option, keeping the best of both worlds safely

[Wyvest]

You're not really risking any DMCA with the patch system, it's been tested and used before. Optifine uses them for their installation, for example. And Spigot does too, as pointed out by @josephworks.

This repository is probably not going to stay, a new one will be created and old users redirected there, which seems like the best option, keeping the best of both worlds safely

2 fun facts:

1. Optifine and Spigot is not OSS. Do you know why? Because making that OSS would be a violation of the MCP license!
2. Your solution seems good

also MIXIN ISNT BAD

[AverageComet250]

I like how the examples for ways this repo can stay oss are private.

Almost defeats the point if you know what I mean.

[OxideWaveLength]

I like how the examples for ways this repo can stay oss are private.

Almost defeats the point if you know what I mean.

It doesn't matter if Optifine is open source or not, they patch Mojang's Minecraft jar on your computer with diff files contained within their installer jar. And, correct me if I'm wrong, but redistributing a modified version of Minecraft as a jar is against Mojang's EULA, so they are effectively getting around it.

Spigot gets around it by patching Mojang's Minecraft server jar and Spigot is open source for the most part, including Bukkit and CraftBukkit (which they maintain).

Them getting around it by letting you patch their software on your computer means that I can get around Mojang and MCP's EULA by letting the user patch their MCP decompiled source code locally using diff files from github and then, finally, download normal source files for the bits of code that don't infringe any license or user agreement (the rest of the client, everything under the "me.wavelength" package).

I could be wrong about all of this so, please, correct me if I'm wrong

[Wyvest]

I like how the examples for ways this repo can stay oss are private.

Almost defeats the point if you know what I mean.

It doesn't matter if Optifine is open source or not, they patch Mojang's Minecraft jar on your computer with diff files contained within their installer jar. And, correct me if I'm wrong, but redistributing a modified version of Minecraft as a jar is against Mojang's EULA, so they are effectively getting around it.

Spigot gets around it by patching Mojang's Minecraft server jar and Spigot is open source for the most part, including Bukkit and CraftBukkit (which they maintain).

Them getting around it by letting you patch their software on your computer means that I can get around Mojang and MCP's EULA by letting the user patch their MCP decompiled source code locally using diff files from github and then, finally, download normal source files for the bits of code that don't infringe any license or user agreement (the rest of the client, everything under the "me.wavelength" package).

I could be wrong about all of this so, please, correct me if I'm wrong

You are misunderstanding what the original complaint was about. You are literally distributing mojang code, Optifine is literally just patch files only and therefore not against mojang eula.

[OxideWaveLength]

I like how the examples for ways this repo can stay oss are private.

Almost defeats the point if you know what I mean.

It doesn't matter if Optifine is open source or not, they patch Mojang's Minecraft jar on your computer with diff files contained within their installer jar. And, correct me if I'm wrong, but redistributing a modified version of Minecraft as a jar is against Mojang's EULA, so they are effectively getting around it.

Spigot gets around it by patching Mojang's Minecraft server jar and Spigot is open source for the most part, including Bukkit and CraftBukkit (which they maintain).

Them getting around it by letting you patch their software on your computer means that I can get around Mojang and MCP's EULA by letting the user patch their MCP decompiled source code locally using diff files from github and then, finally, download normal source files for the bits of code that don't infringe any license or user agreement (the rest of the client, everything under the "me.wavelength" package).

I could be wrong about all of this so, please, correct me if I'm wrong

You are misunderstanding what the original complaint was about. You are literally distributing mojang code, Optifine is literally just patch files only and therefore not against mojang eula.

I mean, have you read the whole conversation? I've said that I'm very aware of that, and that a solution involving diff files is coming soon.