Jump to content

Forge and Minecraft's EULA


mehrcraft

Recommended Posts

I am very confused by Minecraft's EULA as it relates to mods.  It states that you can't profit in any way from mods, but there are obvious signs that it is not quite so, as virtually every mod download goes through something like AdFly and so many modders ask for donations on Patreon.

So, it seems that the real question is "how do you profit from mods without violating the EULA?"

Also, since most modders seem to prefer Forge, the most successful mods that have not been abandoned after a few years are Forge mods, and Forge seems to operate through a standard interface to the Minecraft code instead of by modifying the code itself... it leads me to suspect that Forge was designed to allow profiting without violating the EULA.

Am I guessing correctly?  Are there basic principles or maybe a guide on how to do it safely?

I ask because I am an experienced Java developer, loved Minecraft since Beta, and I would like to create AND properly support mods, but without a steady income (obviously assuming the mods are successful) it is obvious that I would sooner or later get bored and abandon any mod I wrote... so I don't see much point in nodding unless this was viable.

Link to comment
Share on other sites

Paragraph before last of the section "Using our game".

Am I misreading it?  Are you saying that making a Forge mod and earning income through ads and patreon is NOT a violation of the EULA?  That is what I suspected and hoped for, and the reason for this post.

if yes, is there a source of advice on how to do it without getting in legal trouble?

Also, assuming that I were able to design a mod that got millions of downloads and promoted it correctly... would I be able to live on that income?

Edited by mehrcraft
Link to comment
Share on other sites

TLDR: We live in Mojang's good graces and legal grey areas. Forge is not `designed to allow profiting` It was designed too help people not violate the EULA's 'dont distribute our stuff' part. 
Basically, if you're asking this question then you're most likely going to violate their EULA. Just make mods for fun, and if you host it yourself feel free to put non-intrusive ads on your page.
Do not say "Pay be $10 and you can have access to my mod"

But again, nobody here is lawyers, nore would it have any effect if Mojang decided to go after you as Microsoft has more money then you do, and we all know the side with the most money wins thee lawsuit.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

That is exactly it LexManos, it is flat out impossible to produce good mods and support them for the long term if you are only doing them for fun.  If the only motivation is "for fun" sooner or later something else will attract your attention and you'll stop updating the mod as new versions of Minecraft come out and the mod ends up abandoned and no longer functional.  That is easily seen in 80-90% of mods made.

But there are some mods that have stood the test of time.  Most players wouldn't even consider playing without mods like Optifine, Xaero's or Journey maps, and some others from the mods with millions of downloads.  All of those are very obviously making an income from ads, Patreon donations and possibly other means.  Neither Mojang nor Microsoft have gone after them.  That is why I strongly suspect that there is a way to make an income without violating the EULA, although the EULA is very vague about how you would do it. 

Some of the obvious steps are:

- Don't charge for access to a mod.  The mod must be given for free.

- Don't make any of the features dependent or even remotely related on any kind of financial contribution.

- Don't distribute any of Minecraft's stuff.  That part this thread seems to be what Forge (not Fabric as far as I can tell) helps achieve. 

- Don't make any claims of any kind of relationship with Mojang and Microsoft.

 

So I think my question remains, and is valid and clearly possible as those many mods have done it:  "What additional steps must be taken to earn income without violating the EULA?" 

Link to comment
Share on other sites

Ya I think this is getting along the line of trying to skirt their license for the sake of trying to abuse users for profit.
I also reject your assertion that its impossible to produce good mods unless you're paid too do so. Yes, being paid helps you not have to worry about income and other jobs. But that is no guarantee that you won't get "distracted" by other things. Or run into burnout from the Minecraft upgrade grind. 
However the ONLY legal way to make a mod for profit without violating the EULA is to get explicit permissions from Mojang to form a business relationship with them to utilize their IP for profit.
Good luck doing that. I don't think this needs to be discussed any further because your intention seems clear.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • rp.crazyheal.xyz mods  
    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.