GPL compliance

Jump to: navigation, search

Because the source code for the OHRRPGCE is available to you under the terms of the GNU GPL license (version 2 or later, whichever you wish to use), if you make your own version of the OHRRPGCE, you need to release it under the GPL too. How do you do this?

  1. Read the full text of the GPL License. I know that reading lawyer-talk is a pain, but it is important to understand the license, and compared to most legal documents, the GPL really isn't so very difficult. If you are having trouble understanding something, feel free to ask James about it.
  2. Include a copy of the text of the GPL license somewhere with your program, and add a note to any readme file or documentation that mentions that your program is released under the GPL
  3. In the same readme and/or documentation, include a link to where people can download the source code for your program.

Note that creating engine plugins (separate .dll/.so files) does not allow you to get around the GPL; they have to be licensed under the GPL too.

Distributing Copies of GAME.EXE[edit]

If you just want to include an unmodified copy of GAME.EXE (or CUSTOM.EXE) with your game, you should also include a copy of LICENSE-binary.txt which tells people where to get the source code.

You are not required to release your RPG file under the GPL. Your game is just a data file. You should still make sure that players know they can have the source code to GAME.EXE.