License(s)? in exported ZIP and GitHub mod repositories, where are they?

Started by kreatorKen on Fri, 11/06/2020 - 08:35

Topic category: Help with MCreator software

Last seen on 11:14, 11. Jan 2021
Joined Aug 2020
User points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • Tracker tickets:
  • MCreator plugins:
  • Comments:
License(s)? in exported ZIP and GitHub mod repositories, where are they?
Fri, 11/06/2020 - 08:35

Hi. I know that this might be an old hat somewhere, but it is difficult to find it.

When I uploaded my mCreator code v2020.4 to my GitHub repository, no empty or template license was dumped there. I am not concerned about commercialization, but only the correct way of doing this. I am also worried, that if I add a readme and a license to the GitHub repository that this will interfere with importing the project to an mCreator workspace. (Optional is to upload the exported workspace, but there again, we have the same problem, no license). This seems incorrect; only in the the 'mods.toml' and 'modnamehere.mcreator' files do we have the Authors, which both the User and mCreator (which is fair, as it does the heavy lifting).

"author": "kreatorKen, MCreator",

"websiteURL": "https://mcreator.net",

But, the URL here is always mcreator, which I think is overwritten by mCreator if I change it. If I have a GitHub repository, it should be that no? and not mCreator? I could accept both maybe, but it seems a bit of a stretch that all the URLs will only be that. For example, I will add to my own webpage a walk-through since you explicitly state you dont want any external links from your webage to others: this will be about my mod, not mCreator! Here too, I should be able to link that way, without any danger of claiming that I am infringing on your stuff either, since that should also go under a FairPlay/FanArt type of policy.

I know that I can find the 2020.4 EULA in the mCreator "About" and also get to the 3rd-party licenses, but the mod code is outside of that, I suppose, since it is what I made with it. Like a l e go model, if I made it myself, it is my work and not theirs, but I have to state that. It is basically just the Java code, the 3D models and the textures that actually do belong to me, since I made them. Again, I want people to use and expand my stuff, but it would be cool that they keep my name to it. Same thing also, that there should be something that stipulates that all the mCreator, Minecraft and minecraftforge user licenses are also conformed to.... Yes? Or is that unnecessary, since mod code is just a bunch of code? Somehow I really doubt this.

Actually, I just want to release my own code as GPL3.0 for example (so that my name stays with my code, but is opensource), without infringing on anything for mCreator (irrespective of it being opensource or not). I want the URL to be my sites (both a mcreator.net as well as my webpages, which again, must be fair as I made the mod stuff, not the compiling software). This is actually there in §8 of the mCreator EULA. But, could you please state how to safely implement it?

For those that think they can use mCreator and ignore it, keep in mind the mCreator has its own objects, libraries, etc. that are needed for moving the source code to the jar file. That is, you need to keep that in mind and respect all the hard work there, otherwise you should learn java yourself. That is one thing that Klemen is protecting, for good reason. (Please correct me if I am wrong).

One final thing was that uploading it to GitHub also kept my Windows username !! as a new GitHub contributor. Is that normal? I didnt want that on there. Is that from your side or from the GitHub side? That name should not appear anywhere and I couldnt find it in the different mCreator settings.

 

Best wishes.

 

Last seen on 18:27, 26. Jan 2021
Joined Apr 2010
User points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • Tracker tickets:
  • MCreator plugins:
  • Comments:
2020.4 EULA is distributed…
Fri, 11/06/2020 - 09:25

2020.4 EULA is distributed with the said version as legally properly implemented, licenses are version-specific.

that if I add a readme and a license to the GitHub repository that this will interfere with importing the project to an mCreator workspace.

It won't feel free to add custom files to your repository.

One final thing was that uploading it to GitHub also kept my Windows username

I think this is fixed in 2020.5, you can also set your username manually via cmd as you would normally do for a GitHub repository.

Last seen on 11:14, 11. Jan 2021
Joined Aug 2020
User points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • Tracker tickets:
  • MCreator plugins:
  • Comments:
Thanks Klemen, I hope I…
Fri, 11/06/2020 - 10:40

Thanks Klemen,

I hope I didnt imply that the legality of 2020.4 is wrong. It is fully okay. Just it is confusing where to add the "my stuff" license-tag that wont interfere with your and the 3rd-party ones.  After all, all the models and textures are my creations, as should be, as far as the EULA goes.

To that, I am confused: "It wont feel free.." is a bit ambiguous. Could you please elaborate?

  • Did you mean to write "I wouldn't feel free ...": meaning that it might ruin the repository on import? so it is best not to do that? 'Do it at your own risk' kind of thing? i.e. be careful!
    • and maybe if I do, add a note that those files have to be deleted before importing?
  • "The software (it) wont be free...": because I am adding restrictions (which actually I wont be, but I could image others might want to).
  • something else?

Sorry to bother you with this, I know it is a hassle.

Cheers.

 

 

Last seen on 18:27, 26. Jan 2021
Joined Apr 2010
User points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • Tracker tickets:
  • MCreator plugins:
  • Comments:
Sorry, this is a typo :D It…
Sat, 11/07/2020 - 08:56

Sorry, this is a typo :D

It won't feel free to add custom files to your repository.

I meant to say is that it won't interfere with existing files and MCreator if you add custom files there ;)