You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not currently. I'll have to research more licenses to see what would be most fair for game developers who don't want to open source their forks. In the meantime:
I hereby grant all the permissions and exceptions laid out in an GPLv3 license. This notice will act as the license for the current commit (fd692670f683b3701850c493d90e9ce899db6617), but can and likely will change for future commits.
MIT or Apache 2, very open, the developer can do whatever they want
LGPL - keeps some of the GPL properties, but the code can be bundled with commercial games pretty easily. Except for iOS and other App Store platforms where the user can't change their copy of the game. (Re-linking requirement.)
Keep something strict like GPLv3 but sell a commercial license on the side to interested programmers. This is an example of "dual licensing".
The LGPL could work even for commercial N64 games if the game developer takes care to explain to users how to relink their game with another version of the N64-RPG library. In this day and age with open source dev tools, it's entirely possible.
No description provided.
The text was updated successfully, but these errors were encountered: