Hey I was curious if anybody else came across and looked into if Mod Developers can "Ban" a user from their mods without violating the Minecraft ToS, I know that there's a few mods out there with Developers that will ban a person for some reason may that be personal or not, Like there's one I know a person was banned because the Owner didn't like them and another where they banned them for using a Mod alongside another one ( LetsDo Winery & Management Wanted were the two combined mods, Management Wanted made and setup the mod to Ban people, Person was banned because of a joke, it was actually nothing but a joke they got banned for, person had joked about one of the Management Wanted Devs who can legally drink, drinking in-game ).
I couldn't find a single good source on if they can or cannot do this because the way they usually do seems to be World Related and forcefully corrupting or breaking something with the world, Like actual damage because the Developers decided to ban them from the mod, Wasn't known how it worked until a banned person who the Devs didn't like joined a world they wanted to test it on and it just overloaded the hell out of it and caused the game to crash and the world to corrupt. I'm talking about the Management Wanted Developers here.
I'm pretty sure this is against the EULA, especially intentionally coding a mod to grief somebody's world just because they used it "incorrectly" (excluding issues due to bugs in the mod or mod conflicts, of course) or worse, the mod checks some sort of blacklist online (easy solution though: block access to whatever site it is checking. Apparently though, some mods even had blacklisted player names / UUIDs hardcoded in them).
These threads are old but Mojang made it clear that this sort of activity was prohibited and if you don't want somebody to use your mod then don't make it public:
See what happens then when Mojang respond to the email I sent, even If I did something the Management Wanted team didn't like it still doesn't hold grounds that they can Ban me, if they don't like it then too bad. They made a mod, made it public and think they're just not going to have this stuff happen to them, hundreds of people can do this behind the scenes without them knowing, what are they gonna do then? Implement spyware? I'm not the first and sure as hell im not going to be the last
I think if you make the banned players list public and instead of crashing the game soft-lock them with a UI that tells them to uninstall the mod then it wouldn't break EULA/TOS?
Hey I was curious if anybody else came across and looked into if Mod Developers can "Ban" a user from their mods without violating the Minecraft ToS, I know that there's a few mods out there with Developers that will ban a person for some reason may that be personal or not, Like there's one I know a person was banned because the Owner didn't like them and another where they banned them for using a Mod alongside another one ( LetsDo Winery & Management Wanted were the two combined mods, Management Wanted made and setup the mod to Ban people, Person was banned because of a joke, it was actually nothing but a joke they got banned for, person had joked about one of the Management Wanted Devs who can legally drink, drinking in-game ).
I couldn't find a single good source on if they can or cannot do this because the way they usually do seems to be World Related and forcefully corrupting or breaking something with the world, Like actual damage because the Developers decided to ban them from the mod, Wasn't known how it worked until a banned person who the Devs didn't like joined a world they wanted to test it on and it just overloaded the hell out of it and caused the game to crash and the world to corrupt. I'm talking about the Management Wanted Developers here.
I'm pretty sure this is against the EULA, especially intentionally coding a mod to grief somebody's world just because they used it "incorrectly" (excluding issues due to bugs in the mod or mod conflicts, of course) or worse, the mod checks some sort of blacklist online (easy solution though: block access to whatever site it is checking. Apparently though, some mods even had blacklisted player names / UUIDs hardcoded in them).
These threads are old but Mojang made it clear that this sort of activity was prohibited and if you don't want somebody to use your mod then don't make it public:
https://www.minecraftforum.net/forums/mapping-and-modding-java-edition/minecraft-mods/mods-discussion/1408743-to-mod-creators-copyrights-and-malicious-code
https://www.reddit.com/r/feedthebeast/comments/1w2v2i/marc_irl_says_the_mojang_eula_forbids_modders_to/
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
-
View User Profile
-
View Posts
-
Send Message
ModeratorThere have been past occurrences that modders have implemented a "ban" feature by forcefully crashing the game (see mDiyo and GregTech fiasco).
Whether or not it is "legal", per se, is up for debate.
See what happens then when Mojang respond to the email I sent, even If I did something the Management Wanted team didn't like it still doesn't hold grounds that they can Ban me, if they don't like it then too bad. They made a mod, made it public and think they're just not going to have this stuff happen to them, hundreds of people can do this behind the scenes without them knowing, what are they gonna do then? Implement spyware? I'm not the first and sure as hell im not going to be the last
I think if you make the banned players list public and instead of crashing the game soft-lock them with a UI that tells them to uninstall the mod then it wouldn't break EULA/TOS?
~ Holly :3