sendpax.blogg.se

It's possible to allow the community to use Google Drive as they are currently doing, and have a daemon running that polls the Google Drive file for modifications. The Modding API GitHub repository will contain only the modifications to the file, not the original file. It is not illegal to publish the modifications, as long as the publication contains no content from the original file. The part of the modified Assembly-CSharp.dll that is not copyrighted by Team Cherry is the modifications that the modding community makes. The legal solution: publish only the modifications, not the entire binary

It's conceivable that Team Cherry will never enforce copyright claims against such a violation, but it's still a legally risky and frankly impolite way to treat the developers of the game that we love enough to mod. Publishing the modified Assembly-CSharp.dll to GitHub is illegal copyright infringement. However, the modified file still contains lots of content from the original Hollow Knight, which is copyrighted and proprietary. The most obvious way to put the Modding API on GitHub is to simply publish the modified Assembly-CSharp.dll to GitHub. The naive and illegal solution: publish the binary to GitHub

It would be ideal to have the Modding API on GitHub in some form as well. The modding community is already using GitHub for several other mods (examples below). This means that you can only be a Modding API developer/contributor if you are invited to the Hollow Knight discord server. Discussion about this problem: MyEyes/RandomizerMod#1Ĭurrently, Hollow Knight modders are editing the binary game file Assembly-CSharp.dll directly with dnSpy, and publishing the modified binary to Google Drive at a secret link that's shared in the #modding channel of the Hollow Knight discord server.Modding API: (Link not available due to copyright infringement.This is my plan for publishing the Hollow Knight Modding API to GitHub without infringing on copyright.