The best way to protect your "code IP" is by open sourcing it - nobody can steal it and claim it as their own, because your public repositories clearly state the dates and the names of the authors. And honestly, anybody who tries to "protect" their mod IP with legality are just deluding themselves.
Forbidding your users from customizing their experience is just a really lousy thing to do.
Yes it can drastically alter the balance and feel of the mod, but it's not like they can accidentally do it and blame you for making a crap mod. This permission must be irrevocable, and you must also let us permit other people to use, copy, modify and adapt your content". As per Mojang's EULA, there's no such thing as an IP in a Minecraft mod - you only own the *code* that you made (I guess that's IP too, yeah) but the actual content is just as much Mojang's as yours, and it's only yours by name (not liberty) - "If you make any content available on or through our Game, you must give us permission to use, copy, modify and adapt that content. The mod itself have already violated Minecraft's IP, so any compounded claims of breach are void - any court will tell you that. Why aren't users free to change their own personal modded experience how they like? As long as they don't expect support/help with it - but that's implied anyway, unofficial modification = no support - everyone knows that.Īnd errr, changing recipe's with MineTweaker does not violate any mod IP. But the thing is that nobody is forcing anybody to mod their game. Mod authors telling their mod players not to mod their mod, because it ruins the balance.? That's be like Mojang telling their players they're not allowed to mod Minecraft, because it will ruin the balance of the game.
0 kommentar(er)
