I still have lot of unanswered questions about how I'd like to publish my game.
Uncategorized
19
Posts
5
Posters
5
Views
-
The last idea I have would be to keep the code open source and copyleft (GPL), but place the assets under a CC-BY-SA-NC license. The important part here is "Non Commercial", which would forbid to sell the game as-is.
It would still be allowed to fork, replace assets (which might be quite easy since I plan to use CC0 assets myself), and sell the result, but that would require work, restricting it to people motivated to actually work on a meaningful fork.
Would that be a good compromise?
@youen NC is a bit delicate as license. For example, someone streaming the game on Twitch (and getting paid for it) would be technically violating it.
-
For context, as a programmer and only developer of the game so far, I expect most of the "value" (if any) to be in the code, not in assets. Yet assets are still necessary to run the game.
Though I'm interested to know how people are handling open source games in general... I haven't studied that subject myself.
@youen I don't think most open source games reach the level notoriety to have this problem.
If you, or a company you create, holds the sole copyright of the game, you are free to do what you want with it. That includes publishing it on Steam using their SDK that violates the GPL. You would effectively be giving Valve a different license to redistribute the game with Steamworks included. This is even if you also release the game under GPL. If you use other GPL code in your game, you cannot do that. Others wouldn't be able to publish your game on Steam either (unless you grant them a different license).
Another point to make is that if you use CC0 (public domain) assets, you can't re-license them under another creative commons license because you don't have copyright control. You would need to create, or commission, assets under your copyright.
-
@youen I don't think most open source games reach the level notoriety to have this problem.
If you, or a company you create, holds the sole copyright of the game, you are free to do what you want with it. That includes publishing it on Steam using their SDK that violates the GPL. You would effectively be giving Valve a different license to redistribute the game with Steamworks included. This is even if you also release the game under GPL. If you use other GPL code in your game, you cannot do that. Others wouldn't be able to publish your game on Steam either (unless you grant them a different license).
Another point to make is that if you use CC0 (public domain) assets, you can't re-license them under another creative commons license because you don't have copyright control. You would need to create, or commission, assets under your copyright.
@bryanredeagle
"if you use CC0 (public domain) assets, you can't re-license them under another creative commons license [...]"Do you mean if I integrate CC0 assets (as-is or modified by me) in something else, I can't apply any other license on the resulting work? I don't mean to remove the rights of others to use the original CC0 assets of course.
As an example, if I create a mesh and apply a CC0 texture on it, what can I do or not with the resulting work?
-
@bryanredeagle
"if you use CC0 (public domain) assets, you can't re-license them under another creative commons license [...]"Do you mean if I integrate CC0 assets (as-is or modified by me) in something else, I can't apply any other license on the resulting work? I don't mean to remove the rights of others to use the original CC0 assets of course.
As an example, if I create a mesh and apply a CC0 texture on it, what can I do or not with the resulting work?
@youen CC0 means public domain. No one has the rights to control it or give it a new license. If you create a mesh that uses a CC0 texture, then the mesh is under your copyright, but the texture is not. You would not be able to stop someone from using that texture in your game or anyone else's game. You would need to change it enough to make it a new work (of which there are no hard guidelines of how much to change).
-
@bryanredeagle
"if you use CC0 (public domain) assets, you can't re-license them under another creative commons license [...]"Do you mean if I integrate CC0 assets (as-is or modified by me) in something else, I can't apply any other license on the resulting work? I don't mean to remove the rights of others to use the original CC0 assets of course.
As an example, if I create a mesh and apply a CC0 texture on it, what can I do or not with the resulting work?
@youen I peeked at your profile. It gets even more complicated because the things I'm saying apply to the US. France is probably very similar, but there will be differences. Like, what is considered in the public domain. Because some things expire into public domain (each country has different rules), and others are put there on purpose (like SQLite).
-
@youen CC0 means public domain. No one has the rights to control it or give it a new license. If you create a mesh that uses a CC0 texture, then the mesh is under your copyright, but the texture is not. You would not be able to stop someone from using that texture in your game or anyone else's game. You would need to change it enough to make it a new work (of which there are no hard guidelines of how much to change).
@bryanredeagle I feel that we agree on the principle (CC0 assets are public domain, and I don't want or could restrict others to use them).
I want to put my work on another license (like CC-BY-SA) but also use CC0 assets in that work. Is that even possible on a practical stand point?
Things are quickly going to be mixed up and intertwined. I may patchwork texture bits in the same image, aggregate assets in single pack files for performance, etc. How to specify what falls under which license?
-
@bryanredeagle I feel that we agree on the principle (CC0 assets are public domain, and I don't want or could restrict others to use them).
I want to put my work on another license (like CC-BY-SA) but also use CC0 assets in that work. Is that even possible on a practical stand point?
Things are quickly going to be mixed up and intertwined. I may patchwork texture bits in the same image, aggregate assets in single pack files for performance, etc. How to specify what falls under which license?
@bryanredeagle according to these charts, I would believe that it's allowed to remix CC0 and CC-BY-SA-NC works. And then to license the result under CC-BY-SA-NC (which they call "adapter's license"). Unless I don't understand what this all means?
Actually, I think only the second chart matters in this specific case (I'm remixing CC0 and my own work, and wish to publish the result under CC-BY-SA-NC)
-
@youen NC is a bit delicate as license. For example, someone streaming the game on Twitch (and getting paid for it) would be technically violating it.
@oblomov indeed, I didn't think about this case, but it would be quite limiting, and not my intent at all.
Why do legal stuff always end up being inextricable 😅
-
I still have lot of unanswered questions about how I'd like to publish my game.
Make it #OpenSource is something I've already decided.
But I'm concerned someone could take the game to sell it on Steam. This is something I might do myself at some point (yet another unanswered question), but I clearly don't want someone who didn't work on it to get money from players (who could get the game for free instead but woudn't know or would be tricked into thinking they support devs)
@youen if the game becomes popular, you will get scammers doing stuff like that, and it is a valid concern
-
@oblomov indeed, I didn't think about this case, but it would be quite limiting, and not my intent at all.
Why do legal stuff always end up being inextricable 😅
@youen I discovered this particular aspect while discussing licensing of assets with Luanti developers. It would have never occurred to me.
-
@youen if the game becomes popular, you will get scammers doing stuff like that, and it is a valid concern
@aeva not very reassuring 😉 but I suppose you're right. And of course none of this matters if the game *doesn't* become popular (in which case, and if I could know beforehand, I wouldn't be scratching my head 😅)
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Yaku ma vogliamo parlare anche di ilpost.it/2026/03/11/moschea-m… ?
(a scelta, della parte divertente popcorn, o di quanto sia agghiacciante che qualcuno possa dire che gli aderenti ad un partito che è al governo si fanno chiamare camerati, senza che nessuno faccia una piega)
-
PRIDE Daily (@pridedailypod.bsky.social)
https://bsky.app/profile/pridedailypod.bsky.social/post/3mgutqh3a2k24
> Judges say, under European Union law, trans people are permitted to change their status - and that this supersedes the rules in any EU country, such as Bulgaria, that prevent legal gender recognition. >>> PRIDE Daily: Pod app · smart speaker · YouTube · pod.link/1712324163 2/2
-
PRIDE Daily (@pridedailypod.bsky.social)
https://bsky.app/profile/pridedailypod.bsky.social/post/3mgutqdtips24
> The official documents of transgender people must now recognise their gender identity across the European Union. It follows a ruling from the EU’s Court of Justice in the case of a transgender woman from Bulgaria, where courts refused to update her details. 1/2
-
Sandrino Russo (@sandrinorusso.bsky.social)
https://bsky.app/profile/sandrinorusso.bsky.social/post/3mguu3lvpns22
> Space Age 1970 Set da pranzo di Rudi Bonzanini per Tecnosalotto
-
@OrionBelt Mercoledì 26 novembre 2025...abbiamo aggiornamenti?
i soldi buttati nel referendum potevano essere meglio spesi per la gente
-
@mhoye So, a very good question about Devuan; How is it with dealing with proprietary chips, like wifi?
-
@anfangel.bsky.social
https://bsky.app/profile/anfangel.bsky.social/post/3mgu3es2l6k2e
-
@mhoye oh for crying out loud! Look, I run Ubuntu, don't alter it much, and usually don't care about systemD. However, this icks me the hell out!
