Conflict in file: NOTICE #5
Description
Clarification Needed: GPL License vs. Mod Notice Conflict
There is a concern regarding a direct conflict between the repository’s GNU GPL license and the accompanying mod notice from Daemon Forge Developments / cnofafva (Carim DayZ Project).
Observed Conflict
-
GPL License:
- Allows anyone to copy, modify, and redistribute the code, including modified versions, as long as GPL terms are followed.
- Public redistribution of derivative works is explicitly permitted.
-
Mod Notice Conditions:
- Repackaging or building from the source is heavily discouraged.
- Redistribution of modified versions for public use is prohibited - stating that any modifications can only be used for personal servers/players. this in and of itself is a conflict to the terms of the GNU GPL
- Full credit must be provided, and the notice file must be included without modification.
Concrete Example of Conflict
Suppose a developer wants to:
-
Modify the map menus to fit their custom map.
-
Package the modified mod together with their map as a single map mod.
-
Release this map mod on Steam Workshop so other players can use it on their servers.
-
GPL permits this: redistribution of modified work is allowed as long as GPL terms are followed.
-
Notice prohibits this: public distribution is explicitly forbidden.
This creates an unresolvable legal ambiguity: the GPL grants the right to redistribute, but the notice forbids it.
Request for Clarification
Can the maintainers clarify which governs? Specifically:
- Are derivative works allowed to be distributed publicly (e.g., in a map mod), or is this prohibited under the notice?
- How should contributors comply with both the GPL and the notice simultaneously?
This clarification is critical for developers who want to build onto or improve upon the mod while remaining legally compliant. I personally have no issues with providing clear credits where credits are due in this area but again the primary license becomes convoluted by the additional Notice.