<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>[DISCUSSION] New Games Licensing Guide</title>
		<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide</link>
		<description>Posts in the discussion thread &quot;[DISCUSSION] New Games Licensing Guide&quot; - Vidja gaymes? I hardly know &#039;em</description>
				<copyright></copyright>
		<lastBuildDate>Sun, 08 Nov 2026 02:20:28 +0000</lastBuildDate>
		
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6719764</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6719764</link>
				<description></description>
				<pubDate>Sat, 26 Oct 2024 23:14:59 +0000</pubDate>
				<wikidot:authorName>ProcyonLotor</wikidot:authorName>				<wikidot:authorUserId>778357</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm posting here solely because my input was specifically requested by a current Licensing Vice-Captain/fellow Captain Emeritus<sup class="footnoteref"><a id="footnoteref-617117-1" href="javascript:;" class="footnoteref" >1</a></sup>. Retirement's great and I love it.</p> <p>We grappled with essentially identical questions during my tenure, and never came to a conclusion that satisfied me. This led to a disposition and enforcement that was inconsistent at best, actively contradictory at worst. We did the best we could, because, as seen above, it's not a question with a clear answer.</p> <p>To immediately contradict myself (we'll get to that), I'm inclined to believe that Kufat's right. Always have been. Queerious's research is interesting (if, I must say, perhaps not as compelling on the question that is being addressed as they believe) and is certainly worthy of further investigation.</p> <p>However, and here I will say the quiet part out loud, at least during my tenure our actions were guided as much by pragmatic concerns as by the License. We were then, and you remain now, a team with limited manpower and resources. A team at the end of the day largely beholden to how much the community is willing to actually <em>listen</em>. Sure you can always send a DMCA, but I sent enough of those in my time to have a pretty good idea of the actual success rate. It's not a magic bullet.</p> <p>All of which is to say, compromises must be made. You can talk a big game about enforcing the License strictly but if you don't make compromises where necessary you soon lose any practical ability to enforce the License <em>at all</em>.</p> <p>My preferred solution at the time, although it's not one I am quite comfortable supporting now<sup class="footnoteref"><a id="footnoteref-617117-2" href="javascript:;" class="footnoteref" >2</a></sup> was a slightly stricter version of what was proposed here. Creative content licensed CC-BY-SA 3.0, the technical content licensed under a vaguely free software license<sup class="footnoteref"><a id="footnoteref-617117-3" href="javascript:;" class="footnoteref" >3</a></sup>. But that was always a <em>compromise</em>. In formal, precise, perfect application, I again support Kufat's thinking.</p> <p>My actual recommendation here is going to be a frustrating bait and switch. This is a complicated issue that the Licensing Team needs to come to a collective agreement on, even if it's a begrudging compromise. The place to do that is longer term discussion<sup class="footnoteref"><a id="footnoteref-617117-4" href="javascript:;" class="footnoteref" >4</a></sup>, not framed as a minor guide rewrite.</p> <p>The team needs to come up with a party-line position on this topic, and only then should you be looking at guide edits.</p> <div class="footnotes-footer"> <div class="title">Footnotes</div> <div class="footnote-footer" id="footnote-617117-1"><a href="javascript:;" >1</a>. I am aware the timer's run out. My input was sought within the past hour, as of posting.</div> <div class="footnote-footer" id="footnote-617117-2"><a href="javascript:;" >2</a>. To be clear; I'm pretty rusty now, this stuff has not been top of mind for years. I am uncomfortable supporting anything, at this present moment. I don't think I even still have voting powers?</div> <div class="footnote-footer" id="footnote-617117-3"><a href="javascript:;" >3</a>. I no longer remember which I approved.</div> <div class="footnote-footer" id="footnote-617117-4"><a href="javascript:;" >4</a>. I no longer know how these policy discussions are formulated, seem to have changed since my day.</div> </div> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6716688</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6716688</link>
				<description></description>
				<pubDate>Wed, 23 Oct 2024 17:36:11 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Yes, I think it would extend to all interactive media derived, hosted on or off the site.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6716687</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6716687</link>
				<description></description>
				<pubDate>Wed, 23 Oct 2024 17:35:41 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I know it's past the time, but I will respond here anyways, before we make a new discussion thread. Part of the requirements for an asset to be CC-BY-SA compliant for a game is that it must be packaged separately, as those assets need to be available, unencrypted and separate from the packaged executable</p> <p>So to be compliant, yes, it does need to be packaged 'separately', so I would argue that the interpretation of it being a collective work is valid?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6714756</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6714756</link>
				<description></description>
				<pubDate>Tue, 22 Oct 2024 19:51:24 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Sorry to get this in right under the wire; I kept forgetting.</p> <p>OK, let's assume for the sake of argument that, as you argue, the following are true:</p> <ul> <li>All game code is mechanics that are unable to be copyrighted</li> <li>The code is not a derivative work of the SCP Wiki</li> <li>Code is a completely separate work in terms of copyright and is merely distributed alongside assets</li> </ul> <p>(I'm making the rest of this post under the assumption that these things are true.)</p> <p>If we do, we're back at the situation in <em>Drauglis v Kappa Map Group</em>, where we have different, unrelated works under separate copyright (the cover art and the actual maps in the atlas, in that case) being distributed together in a single package (a book in that case, an archive file of some sort in the case of most modern games.) Per the court in that case, the <em>amalgamation of separate works</em>, under separate copyright, must be either a collective work or derivative work under CC BY-SA 2.0. (I do not see anything that would cause this to differ for 3.0.)</p> <blockquote> <p>the entirety of a game should not be mandated to be released under a compatible of CC-BY-SA 3.0 license, rather, it should be analyzed and licensed in parts.</p> </blockquote> <p>This would only be true if the code and assets were packaged separately. When you package them together, you have the same situation as the CC BY-SA cover on the atlas of all-rights-reserved maps, <em>except</em> that the SCP material is modified and therefore does not meet the conditions to be distributed as a collective work. The combined product is a derivative work under CC by virtue of the fact that it cannot be a collective work and it cannot be a third option other than a collective work or derivative work.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6709628</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6709628</link>
				<description></description>
				<pubDate>Sun, 20 Oct 2024 09:51:57 +0000</pubDate>
				<wikidot:authorName>psychicprogrammer</wikidot:authorName>				<wikidot:authorUserId>5299606</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Question, does this apply to games/other interactive media hosted directly on the SCP site itself?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6705895</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6705895</link>
				<description></description>
				<pubDate>Sat, 19 Oct 2024 22:09:01 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I am ambivalent, it could either be an independent page, or just included as a tab on the main licensing guide.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6705804</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6705804</link>
				<description></description>
				<pubDate>Sat, 19 Oct 2024 16:35:11 +0000</pubDate>
				<wikidot:authorName>EstrellaYoshte</wikidot:authorName>				<wikidot:authorUserId>3781861</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Is this a completely new page? Addition to the extant one?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6698215</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6698215</link>
				<description></description>
				<pubDate>Wed, 16 Oct 2024 18:10:20 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I can see that - edited to remove.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6698084</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6698084</link>
				<description></description>
				<pubDate>Wed, 16 Oct 2024 13:14:31 +0000</pubDate>
				<wikidot:authorName>Ethagon</wikidot:authorName>				<wikidot:authorUserId>5844683</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I think the suggestion of putting the game under a similar license as Creative Commons is overall a good idea, but</p> <blockquote> <p>While this is not required, please consider it.</p> </blockquote> <p>this sentence specifically feels a bit too pushy for me, especially with the suggestion being already given multiple times at that point.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6697743</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6697743</link>
				<description></description>
				<pubDate>Tue, 15 Oct 2024 21:40:18 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I can understand the argument you make, however, after taking some time to look into relevant sources, discussions and case law, especially around licensing and copyright, I have found a number of sources that state a video game is made up of multiple constituent parts that are each protected under different laws, legislature, and treated as independent elements.<sup class="footnoteref"><a id="footnoteref-252880-1" href="javascript:;" class="footnoteref" >1</a></sup></p> <ul> <li><a href="https://www.researchgate.net/publication/356086684_THE_COPYRIGHT_PROTECTION_OF_VIDEO_GAMES_FROM_RESKINNING_IN_CHINA-A_COMPARATIVE_STUDY_ON_UK_US_AND_CHINA_APPROACHES">https://www.researchgate.net/publication/356086684_THE_COPYRIGHT_PROTECTION_OF_VIDEO_GAMES_FROM_RESKINNING_IN_CHINA-A_COMPARATIVE_STUDY_ON_UK_US_AND_CHINA_APPROACHES</a> &#8212; This discusses how games are made of multiple constituent parts, and how each aspect is covered under different laws. It also discusses the Idea/Expression dichotomy, covering that a concept or mechanic cannot be covered under copyright.</li> <li><a href="https://www.researchgate.net/publication/376654607_Status_of_Video_Game_under_the_USA_and_Indian_Copyright">https://www.researchgate.net/publication/376654607_Status_of_Video_Game_under_the_USA_and_Indian_Copyright</a> &#8212; Discusses general approaches, and also includes, from page 3:</li> </ul> <blockquote> <p>The current policy as a whole consists mostly of a few legal arrangements, scattered throughout mechanical and protected invention laws as well as competition laws. Additionally, these agreements propose ways to insure individual video game elements and the system on which they are played, but not the video game as a whole as a copyrighted work.</p> </blockquote> <ul> <li><a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4138875">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4138875</a> &#8212; also provides a similar breakdown to the above.</li> </ul> <p>The wider issue is that different countries from around the world address how copyright applies to video games in completely different ways; the intent with the interpretation included in the guide is to provide as much copyright protection and attribution as we can to the wiki's content, while providing flexibility for the various interpretations.</p> <p>Given that - I would argue that the entirety of a game should <em>not</em> be mandated to be released under a compatible of CC-BY-SA 3.0 license, rather, it should be analyzed and licensed in parts.</p> <div class="footnotes-footer"> <div class="title">Footnotes</div> <div class="footnote-footer" id="footnote-252880-1"><a href="javascript:;" >1</a>. If I have misinterpreted anything in this, disclaimer that I am not a lawyer lmao.</div> </div> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6697732</guid>
				<title>Re: [DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6697732</link>
				<description></description>
				<pubDate>Tue, 15 Oct 2024 20:48:43 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>As previously discussed, I don't think this interpretation of CC BY-SA is correct. It's my understanding that the entire game (i.e. A/V assets, dialogue, machine code, etc.) is considered one Work for purposes of the CC license.</p> <p>There isn't much case law on this, but <em>Drauglis v Kappa Map Group</em> (which dealt with CC BY-SA 2.0) was very clear about the fact that anything incorporating CC BY-SA work could only be a single work or a compilation (which was the equivalent of what's deemed a &quot;collection&quot; under 3.0.) The exact language is &quot;the License provides no other categories into which a published work might fall.&quot; Since video games don't meet the criteria of compilations/collections, they have to be treated as single works. Likewise, the USA generally treats video games as single works for purposes of copyright (see e.g. <a href="https://www.copyright.gov/comp3/docs/compendium-12-22-14.pdf">https://www.copyright.gov/comp3/docs/compendium-12-22-14.pdf</a> ) rather than compilations.</p> <p>I believe we should make it clear that any game which incorporates SCP content must be released under CC BY-SA 3.0 or a compatible license <em>in its entirety</em>. If that's incompatible with the license used for the game's engine, that would be the developer's problem to resolve.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://o5.scpwiki.com/forum/t-16968037#post-6697723</guid>
				<title>[DISCUSSION] New Games Licensing Guide</title>
				<link>https://o5.scpwiki.com/forum/t-16968037/discussion-new-games-licensing-guide#post-6697723</link>
				<description></description>
				<pubDate>Tue, 15 Oct 2024 20:29:51 +0000</pubDate>
				<wikidot:authorName>Queerious</wikidot:authorName>				<wikidot:authorUserId>7453143</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>o4 Mirror: <a href="https://scp-wiki.wikidot.com/forum/t-16968038/discussion-new-games-licensing-guide">https://scp-wiki.wikidot.com/forum/t-16968038/discussion-new-games-licensing-guide</a></p> <h1><span>Issue:</span></h1> <p>The current <a href="https://scp-wiki.wikidot.com/licensing-guide">licensing guide</a> has a small section within the &quot;For Specific Creator Types&quot; tab, that covers a very surface level of how our site's licensing interacts with video game development. The issue with the current language is that it is not very specific, and partially contradicts itself.<sup class="footnoteref"><a id="footnoteref-458976-1" href="javascript:;" class="footnoteref" >1</a></sup> Given the increasing number of games being developed based on the SCP Wiki, the creation of a dedicated guide is necessary.</p> <hr /> <div class="collapsible-block"> <div class="collapsible-block-folded"><a class="collapsible-block-link" href="javascript:;">Show&nbsp;Current&nbsp;Text</a></div> <div class="collapsible-block-unfolded" style="display:none"> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">Hide</a></div> <div class="collapsible-block-content"> <div class="blockquote"> <p><strong>Game Developers</strong>: You are free to create and share videogames based on SCP, but you must comply with all aspects of the license as it relates to software. That means releasing the work under CC-by-SA-3.0, including the release statement prominently on any store page the game is distributed on (as well as developer websites and the like), releasing the game without DRM if the game costs money (steam and the like have developer options for this), not imposing additional legal restrictions through EULAs or equivalent user forms, and not attempting to impede any alternate distribution sources so long as those sources in turn follow the terms of the license.</p> <blockquote> <p>Sample release statement: &quot;Content relating to the SCP Foundation, including the SCP Foundation logo, is licensed under Creative Commons Sharealike 3.0 and all concepts originate from <a href="https://scpwiki.com/">https://scpwiki.com/</a> and its authors. [Insert Game Name here], being derived from this content, is hereby also released under Creative Commons Sharealike 3.0.&quot;</p> </blockquote> <p>Note: You can also choose to license your game under GPLv3, which is compatible with our license. It is a more specialized software license that includes provisions for patent rights, but requires you to release the full source code of your game publicly- in a manner that is immediately playable and modifiable. If you do so, please still credit the SCP Foundation and its authors via attribution. <a href="https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software">See here for more information on why the Creative Commons organization recommends GPLv3 for software</a>.</p> <blockquote> <p>Sample GPL release statement:<br /> &quot;(one line to give the program's name and a brief idea of what it does.)<br /> Copyright (C) (year) (name of author)<br /> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br /> This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br /> You should have received a copy of the GNU General Public License along with this program. If not, see &lt;<a href="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</a>&gt;.&quot;</p> </blockquote> </div> </div> </div> </div> <hr /> <h1><span>Solution: A New Games Licensing Guide</span></h1> <p>To address this issue, I have created a new guide to break down exactly how software licensing interacts with the SCP Wiki, and answers a number of frequent questions that are typically asked by users. The intent of this guide is to provide more focused guidance, especially in relation to how a game developer can ensure that their game is compliant, while still giving them the freedom to distribute their game as desired.</p> <p>The full text of the page has been included below, in a collapsible, and may be reviewed and discussed in full. For a short summary, this is a TL;DR snippet from the page:</p> <blockquote> <p><strong>TL;DR:</strong> Any asset you create for the game needs to be licensed under CC-BY-SA, or a compatible license. Any source code, engine code, executable or otherwise are not considered relevant in terms of the CC-BY-SA license, and may be licensed under whatever you would like.</p> </blockquote> <hr /> <div class="collapsible-block"> <div class="collapsible-block-folded"><a class="collapsible-block-link" href="javascript:;">Show&nbsp;Guide&nbsp;Content</a></div> <div class="collapsible-block-unfolded" style="display:none"> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">Hide&nbsp;Guide</a></div> <div class="collapsible-block-content"> <div class="blockquote"> <p><span style="white-space: pre-wrap;">[[toc]]</span></p> <h1><span><span style="text-decoration: underline;">Licensing for SCP Games</span></span></h1> <p>When we're talking about creating a game based on the world or content of SCPs, we often get a lot of questions about how you need to license your game. Do you need to release it under a specific license. does it have to be free, does my game need to also be CC-BY-SA? Can I make an SCP game in Unity/Unreal?</p> <p>Unfortunately, the Creative Commons license was not designed for software, and is not directly compatible with games; instead, the focus is on attribution, and ensuring compliance for derivative words or art.</p> <p><span style="white-space: pre-wrap;">[[collapsible&#32;show=&quot;Show&#32;TL;DR?&quot;&#32;hide=&quot;Hide&#32;TL;DR&quot;]]</span></p> <blockquote> <p><strong>TL;DR:</strong> Any asset you create for the game needs to be licensed under CC-BY-SA, or a compatible license. Any source code, engine code, executable or otherwise are not considered relevant in terms of the CC-BY-SA license, and may be licensed under whatever you would like.</p> </blockquote> <p><span style="white-space: pre-wrap;">[[/collapsible]]</span></p> <p>To simplify how we talk about this, its easier to conceive of a game as three distinct parts: the <strong>engine and executable</strong>, the <strong>source code</strong>, and the <strong>assets</strong>.</p> <hr /> <h1><span><span style="text-decoration: underline;">Definitions</span></span></h1> <p>In the context of this guide, we are using each term in a specific way &#8212; to avoid confusion, we have defined these terms here:</p> <hr /> <h2><span>Engine and Executable</span></h2> <p>The <strong>engine</strong> and the <strong>executable</strong> are two distinct aspects that we bundle together, because licensing considers them effectively the same.</p> <hr /> <h3><span>Engine</span></h3> <p>The <strong>engine</strong> is defined as the base game development software engine that is used in the creation of your game. The engine refers to all of the proprietary code created by the company that created the engine, and is not considered relevant for the Creative Commons license.</p> <p>Examples of engines include, but are not limited to:</p> <ul> <li>Unreal Engine 4</li> <li>Unity</li> <li>Godot</li> <li>RPG Maker</li> <li>Twine</li> <li>Scratch</li> </ul> <hr /> <h3><span>Executable</span></h3> <p>The <strong>executable</strong> refers to the .exe file created when exporting your game from the game engine. The executable, similarly to the engine, is based on the proprietary code of the packager/engine creator, and is not considered relevant for the Creative Commons license.</p> <hr /> <h2><span>Source Code</span></h2> <p>The <strong>source code</strong> of a game refers to all code, data assets, data-driven tables, mechanics-focused comma separated value files, or other forms of scripting gameplay (such as Blueprints, or other node based-editors). This only applies to code that was created by the developers, not including the engine or executable code, and is not considered relevant for the Creative Commons license.</p> <hr /> <h2><span>Assets</span></h2> <p>The <strong>assets</strong> within a game refer to all non-code based files that are included with the game. The most relevant assets in terms of licensing are art files and narrative files, that are not natively packaged with the <strong>engine or executable</strong> &#8212; these assets are considered relevant when talking about the SCP Wiki's Creative Commons license.</p> <p>Assets include, but are not limited to:</p> <ul> <li>Textures (.jpeg, .tga, .png, etc.)</li> <li>Models (.obj, .fbx, etc.)</li> <li>Videos (.mp4, .mkv, .avi, etc.)</li> <li>Music and Sound Effects (.ogg, .mp3, .wav, etc.)</li> <li>Narrative &amp; Scripts (.txt, .csv (<em>Narratives</em>), .rtf, etc.)</li> </ul> <p>Basically, if it is not code, but you created it for your game, consider it an asset &#8212; these items are the most relevant when talking about licensing SCP for your game.</p> <hr /> <h1><span><span style="text-decoration: underline;">Guide &amp; Common Questions</span></span></h1> <h2><span><strong>Engine and Executable</strong></span></h2> <p>To start with a common question:</p> <blockquote> <p>Is there a restriction to what Game Engines I can use if I want to make a game about SCP?</p> </blockquote> <p>Short answer, <strong>no</strong>.</p> <p>There is no limit to what game engines you use, as any code that is used in the engine is licensed by yourself, as the developer of the game. Notably, the majority of the major paid game engines (Unity, Unreal, GameMaker) carve out an exception stating that you may publish your software under a different license than the engine, and that it does not change the license of the engine code itself. From this, we approach this entire issue in this manner; we separate the parts, and have the handled under different licenses.</p> <hr /> <h2><span><strong>Source Code</strong></span></h2> <p>The next part of a game, and the next question is about the game itself:</p> <blockquote> <p>If I release a game about SCPs, does it have to be under CC or a similar license?</p> </blockquote> <p>No, you do not <em>need</em> to release your software (or <strong>source code</strong>) under a similar license, <em>however</em>, we would ask that you consider releasing it under one such as GPL, to maintain the ethos of the site.</p> <p>You can release the source code under any license, unless otherwise specified by the game engine you use; the source code would not be considered derivative of the SCP wiki, or works therein, as the wiki is not a software project; it is a static asset, not interactable. That means you do not <em>have</em> to choose a 'compatible or similar license'.</p> <p>However, consider releasing your game under something like GNU GPL, MIT License or GPLv3 &#8212; these software licenses have a similar approach to freedom of information that informs the reasoning and ethos behind our use of the Creative Commons license.</p> <hr /> <h2><span><strong>Assets</strong></span></h2> <p>This is the section that actually matters in terms of the Creative Commons license, and has the most 'complexity' to it. As defined in detail earlier, <strong>assets</strong> are defined as non-source code files created for the game, including but not limited to textures, models, narrative scripts, music and more.</p> <blockquote> <p>How do I attribute the works? Do I have to?</p> </blockquote> <p>When you are making a game that is directly using, or adapting an SCP work into a derivative adaptation, you must follow standard attribution for Creative Commons works. That means that <strong>you must include the name, author, and a link to the source</strong> for any works or derived from the SCP wiki that are used in your game &#8212; see the rest of the licensing guide for more details on that.</p> <blockquote> <p>What about derivatives? Like a 3D model based on an art piece on the wiki?</p> </blockquote> <p>If you create a derivative work, that is, <strong>any asset</strong> that is derivative of a work on the wiki, that asset must be released under a similar or compatible license. This means that, if I created a model of SCP-173 in my game, that model and texture would need to be released under a compatible license. This also means that said assets must be unencrypted, and available in the source of the game, once distributed/packaged in the executable &#8212; this is to ensure compliance with our works, as based on the CC-BY-SA license present throughout the site.</p> <p>The also includes derivative stories; if your story is an adaptation of a specific work on the wiki, the narrative of your game must be released under CC-BY-SA, or a compatible license.</p> <p>However, if your game is simply based on the concept of SCPs, but you have created your own unique narrative and anomalies, you would need to follow attribution towards the SCP Wiki, but would not be required to release those legally distinct assets under a similar license, comparable to standard licensing standards.</p> <hr /> <h2><span>The Big Question</span></h2> <p>If you've made it this far into the guide, you're probably still wondering the big question:</p> <blockquote> <p>Can I make money off of my SCP game?</p> </blockquote> <p>The answer is <strong>yes, as long as you follow the ShareAlike license for assets, and have proper attribution</strong>.</p> <p>I do want to take a second and point something out &#8212; earlier I discussed releasing your game under the GNU GPL or similar license, and wanted to circle back on that topic. If you are releasing a game under a license such as that, you are <strong>not</strong> prohibited from distributing that game for money. What it means is that as an end user who owns the game, <em>I</em> would be able to redistribute it, as the license is concerned with freedom of information. You can still charge for access, you just cannot require that you are the only avenue. So if you release your game under GNU GPL, or a similar license, you can both maintain the spirit behind the SCP wiki's use of Creative Commons, while still being able to earn money for your labour!</p> <hr /> <h1><span><span style="text-decoration: underline;">Summary</span></span></h1> <p>In summary, when using the SCP wiki as the basis for a video game, you need to ensure that your assets are compliant with the CC-BY-SA license. This, however, does not extend to the software itself, not does it prevent you from using major game engines or profiting off of your game.</p> </div> </div> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">Hide&nbsp;Guide</a></div> </div> </div> <hr /> <p>This guide would be posted as a standalone guide, following discussion and a vote.</p> <h1><span>What's Next?</span></h1> <p>This guide has been discussed by members of licensing internally, but we wanted to open discussion to the wider staff to ensure that there are no blind spots or issues that could crop up. Discussion on this guide will continue for a week, and if there are no major changes required, we will progress to a vote, following which, this will be posted as a new staff guide on the Wiki.<br /> <iframe src="https://scpwiki.github.io/timer/timer.html?lang=en&amp;time=2024-10-22T20%3A25%3A50.752Z" align="" frameborder="" height="" scrolling="" width="" class="" style="width: 750px; height: 200px; border: 0; text-align: center;"></iframe></p> <div class="footnotes-footer"> <div class="title">Footnotes</div> <div class="footnote-footer" id="footnote-458976-1"><a href="javascript:;" >1</a>. In terms of saying that the entire game must be released under CC-by-SA-3.0, which is considered generally incompatible with software projects, and does not account for the engine code being released under a different license.</div> </div> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>