GPL, MIT, CC BY-SA: game licences explained

·

A valley in Luanti 5.12, playing the VoxeLibre game.

Licences are the least exciting part of open source games and the part that causes the most arguments. Most of the confusion comes from one thing: a game is made of code and assets, and the two are usually licensed differently. Here’s a plain-language tour. It isn’t legal advice; when it matters, ask a lawyer or the project.

Code: copyleft or permissive

Copyleft licences, mainly the GPL family, let anyone use, study, change and share the code, on one condition: if you distribute a modified version, you must share its source under the same licence. That’s why so many games are GPL: it keeps forks open. The LGPL is a weaker form, usually for libraries, that lets closed programs link to them.

Permissive licences such as MIT, BSD, zlib and Apache 2.0 ask little more than keeping the copyright notice. Anyone, including commercial studios, can build on the code without sharing their changes. Engines often choose these to be adopted widely; Godot is MIT-licensed.

Neither is “more open”. They make different bets about what keeps a project healthy.

Assets: usually Creative Commons

Art, music, sound and text are rarely licensed like code. Most open games use Creative Commons licences:

  • CC0 places the work as close to the public domain as the law allows.
  • CC BY asks for credit.
  • CC BY-SA asks for credit, and that adaptations are shared under the same licence. It’s the asset-world equivalent of copyleft.

Avoid the NC (non-commercial) and ND (no derivatives) variants if you want a project to count as free: they stop a distribution from packaging the game, or a fan from remixing it.

Do they mix?

Mostly, if you’re careful. CC BY-SA 4.0 is one-way compatible with GPLv3: adaptations of BY-SA material can be released under GPLv3. Creative Commons itself recommends against using CC licences for software, so use a software licence for code and CC for everything else, and say so clearly in your repository.

What to do as a maker

  1. Pick a licence on day one and put a LICENSE file in the repository.
  2. Keep a credits file listing every asset, its author and its licence.
  3. Don’t use assets whose licence you can’t find. “I found it online” is not a licence.
  4. If you accept contributions, say what licence they’ll be under.

What to do as a player

Nothing, mostly. Every licence here lets you play the game, share it with friends, and look at how it works. The conditions only kick in when you redistribute or modify it, and even then they’re about sharing, not paying.

Tomás Herrera Avatar

One response to “GPL, MIT, CC BY-SA: game licences explained”

  1. indie_owl Avatar
    indie_owl

    Clearest explanation of the code versus assets split I’ve read. Sending it to my jam team.

Leave a Reply

Your email address will not be published. Required fields are marked *

More from the site