Complying with Licenses

The license is the legal requirement for you (or your company) to use and distribute the software (and derivative projects, including games made with it). Your game or project can have a different license, but it still needs to comply with the original one.

In the case of the MIT license, the only requirement is to include the license text somewhere in your game or derivative project.

This text reads as follows:

Note

The license does not specify how it has to be included, so anything is valid as long as it can be displayed under some condition. These are the most common approaches (only need to implement one of them, not all).

Include the above license text somewhere in the credits screen. It can be at the bottom after showing the rest of the credits. Most large studios use this approach with open source licenses.

Licenses screen

Some games have a special menu (often in the settings) to display licenses.

Just printing the licensing text using a function may be enough on platforms where a global output log is readable (as an example, mobile devices).

Accompanying file

If the game is distributed on desktop operating systems, a file containing the license can be added to the software that is installed to the user PC.

If the game includes printed manuals, license text can be included there.

Godot itself contains software written by third parties. Most of it does not require license inclusion, but some do. Make sure to do it if you are using them. Here is a list of which ones require it:

FreeType

Godot uses to render fonts. Its license requires attribution, so the following text must be included together with the Godot license:

MBedTLS

If the project is done with Godot 3.1 or above and it utilizes SSL (usually through HTTP requests), the MBedTLS Apache license needs to be complied by including the following text: