License: GNU GPL version 3

Other (objects, etc.) concept

Distributed under the GNU GPL Version 3 license. Which includes clauses allowing fundamentally different uses & restrictions not existent in GPL 1 & 2


The first video game about License: GNU GPL version 3 was released on September 30, 1997.

Fast RGV, Zelda s9larus and Gott Games has published most of these games

There are many differences in the GPL 3 from 1 & 2. Highly publicized was the included language to prevent 'tivoization'. So named, because Tivo used GPL licensed code in their Tivo set top boxes. But designed this hardware to specifically not function if the software was changed. Many people who know that GPL could be modified, improved, and used for any purpose were understandably putout that Tivo had found a way to enforce a, "Not this purpose". Nothing in GPL 1 or 2 prevented Tivo from doing this. Note: Tivo had legitimate reasons related to customer service. They wanted to ensure they did not have to support modifications they may have no idea how to support. But their method was just plain overkill and prevented Tivo and anyone else from benefiting from any changes in the Tivo software that anyone might have come up with.

Another key importance is the language undercutting DRM. GPL 3 grants the right of the user to break, bypass, or remove, and otherwise "never be trapped", by DRM in GPL 3 software. While developers remain free to develop DRM for and with their GPL 3 software, users (or other developers) have the right to get rid of it or bypass it in their improved versions (which can be as simple as getting rid of it or bypassing it). And this satisfies DMCA restrictions that not only forbid DRM circumcision, but forbid devices capable of DRM circumcision. GPL 3 is legally not one of these devices. One may wonder why it wasn't forbidden entirely. But, such a ban may not be legally enforceable. Such a ban is contrary to "any use". DRM-like algorithms have value for privacy software, and therefore should not be outright restricted. DRM-like algorithms can have gameplay value, such as preventing cheating. So UVL users can rest assure GPL 3 isn't forcing developers supportive of GPL 3 to make games in ways they do not want to.

Language that makes GPL 3 Apache Compatible also means no company can use GPL 3 code and make 'backroom deals' with it that favor their own customers. An example was, Microsoft granted broad rights to their customers to use Microsoft's software patents. But when they licensed code to Novel, they ensured that Novel users were specifically prohibited from using Microsoft's software patents, if using the exact same software or any other software from Novel that used Microsoft's software patents. If you grant a patent license with GPL 3 code, it always stays with the code and all derivative works even if the licensed is changed to a different GPL 3 compatible license. (Licenses that do not grant patent licenses as well, are not GPL 3 compatible)

The language of the GPL 3 confirms that it is a "License" and not a "Contract".

The work of the GPL 3 itself is copyrighted with rights of fully owned derivative works granted. However such derivative works require the name to be changed and cannot use the GPL preamble without written permission. As in, you can modify the GPL but your version has to me renamed and have a different preamble (or none).

The most shocking difference in GPL 3 from 1 & 2 is clauses listed in Section 7, "Additional Terms". This allows the software to inherit restrictions that GPL 1 & 2 do not allow. Trademarks and service marks are specifically mentioned as points-of-restriction. But the language is vague enough to allow most any general restriction. Early debate over this section raised the possibility of people mixing GPL version 3 code with restricted code, such as code under other 'incompatible' open source licenses, and even fully closed-source proprietary code. Once mixed, GPL 3 code inherits the restrictions of the non-GPL 3 code. Thus, GPL 3 can become restricted freedom of use for any purpose, restricted freedom of study, restricted freedom of making improvements, and restricted freedom of redistribution. In short, free to restrict ALL GPL freedoms. This remained a theory until it was put into practice by the DXX-Rebirth project team. DXX-Rebirth uses proprietary source code from Parallax Software. Parallax' license grants everything except commercial use. Only Parallax can relicense it. This code cannot be mixed with GPL 1 or GPL 2 code as the restriction of non-commercial use is specifically forbidden by the term "Any use" in these licenses. Derivatives of this code also cannot be mixed with GPL 1 or GPL 2 code (If derivative works are allowed by the copyright holder, Copyright law places derivative works under the restrictions of the original copyright notice/EULA unless other rights are specifically granted to authors of derivative works in the original copyright notice/EULA). But the DXX-Rebirth project team licensed their derivative code and their original code under the GPL 3 using the Section 7 exception. This means all of their GPL 3 code inherits the non-commercial use restriction for as long as its mixed with Parallax' original code and their derivative code. This "GPL 3 project" is restricted to non-commercial use. And any developer who uses DXX-Rebirth' code is in danger of placing his/her project under the same non-commercial use restriction.

The phrase "Unless specifically stated, the Program has not been tested for use in safety critical systems." is not part of the GPL 3. Sharks with lasers may or may not have been tested before they are revealed and start randomly shooting mooks; GPL 3 makes no statement on the matter. Authors of GPL 3 software are free to inform customers of testing status one way or another, but separately from the GPL text and not within the text of a conflicting license.

=========================== Section 7 of the GPL 3 ===========================

7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.