Reword additional permissions to make it more unambiguous

The original permissions were written somewhat hastily, so this just cleans things up
This commit is contained in:
FalsePattern committed 2024-05-30 18:11:52 +02:00
1 parent 0451795576
commit 9012ddc522
29 files changed
+200 -636

No files matched your search

+4 -30
View File
@@ -15,38 +15,12 @@ ChunkAPI is designed with players in mind, and as such, it uses slightly aggress
party developers cannot break your worlds in an irrecoverable way by changing huge parts of the API.
For this reason, the mod itself is fully licensed under the GNU Affero General Public License, version 3.0 or later,
with the following additional permissions to allow it to be easily used by modpacks and other mods:
with several additional permissions according to Section 7 of the AGPL.
<details>
<summary>License excerpt</summary>
You can find these permissions in the full [LICENSE](LICENSE) file. (TL;DR: Yes, you can use official releases of
ChunkAPI in a modpack without getting trapped by AGPL's requirements).
```
According to section 7 of the GNU AGPL, this software comes with the following additional permissions:
You may link this mod against proprietary code developed by Mojang Studios (Minecraft and its dependencies), as well
as distribute binary builds of it as part of a "Minecraft modpack" without the AGPL restrictions spreading to any other
files in said modpack.
You may also develop any mods that depend on classes the API packages (`com.falsepattern.chunk.api.*`) and distribute that
mod under terms of your own choice. Note that this permissions does not apply to anything outside the internal package,
as those are internal implementations of ChunkAPI and are not meant to be used in any external mod, thus the full force
of the AGPL applies in such cases.
These additional permissions get removed if you modify, extend, rename, remove, or in any other way alter
any part of the public API code, save data binary formats, or the network protocol in such a way that makes
it not perfectly compatible with the official versions of ChunkAPI.
If you wish to make modifications to the previously mentioned features, please create a pull request on the official
release of ChunkAPI with full reasoning and specifications behind the requested change, and once it's merged and
published in an official release, your modified version may once again inherit this additional permission.
To avoid abuse caused by upstream API changes, these permissions are valid as long as your modified version of ChunkAPI
is perfectly compatible with any public release of the official ChunkAPI.
```
</details>
Note that while the mentioned limitations might seem unnecessary, it is essential for protecting your saves from getting
Note that while these limitations might seem unnecessary, it is essential for protecting your saves from getting
"trapped" in a random fork of ChunkAPI without any way to recover to vanilla or the official release of ChunkAPI
without world corruption, in case no suitable backups are available.