I just want to make sure I understand the Runtime licenses for Spine. I have a few questions about how the license applies.

I have a Spine license, which means that I'm able to use the Spine Runtimes to create a game in, say, Unity. Once that game is compiled (not, say, an open-source game), does it still require a note in its license that the Spine Runtimes cannot be transferred? That seems like it would be strange, but I want to be sure. Also, if it is the case that I need to include the license, how does that affect freeware games made using Spine for animation?

If I make a freeware game, I would want players to copy and redistribute the game at their own discretion. I don't want to require them to download the game off, say, my own website if their friend already has it on a USB drive. But if that counts as redistributing a Runtime, would I be able to allow that? That's moot if the compiled, finished game doesn't count as a derivative of the Runtime, but the language seems unclear, so I want to be sure.

Also, if I'm cooperating with someone else in making a game, but only I am handling animations (and only I am using Spine), do they also need a Spine license because the project as a whole contains the Runtime code?

Just want to be clear before I use the Spine Runtimes. Thanks. 🙂

Related Discussions
...

Legal stuff is never fun. I am not a lawyer and this post is not legal advice. Here we go!

1) Any software that contains the Spine Runtimes is considered a derivative work.

2) Any redistribution of the Spine Runtimes requires the Spine Runtimes Software License to be included.

Without those two, someone could redistribute the runtimes as their own library and effectively strip away the license.

3) Users of a freeware game (or other derivative) are limited to "personal or internal use". This should be acceptable for users of the game.

4) Licensing Spine grants rights to use the editor, and also rights to distribute derivatives. I don't see a problem with an intermediary distributing derivatives on your behalf (and ceasing to do so in the unlikely case your license becomes invalid).

5) There are two considerations: using the Spine editor and using/distributing the Spine Runtimes. When cooperating with others, they don't need a Spine license if they don't need to run the Spine editor. The person/entity which owns and distributes derivatives needs a Spine license to cover using/distributing the Spine Runtimes.

"Locks keep Honest People Honest" or my favorite variation: "Locks keep honest people out".

It's security theater.