How to put a disclaimer about IP in an open source fangame? I am creating a fangame. Specifically a game where you can open weapon cases from Counter-Strike: Global Offensive for free and collect or trade skins that you obtain. The entire game source is my own work, except there are two files containing names and parameters of items from CSGO. I want to distribute my game's source including these files. I am ready to retract these parts should Valve contact me regarding intellectual property, however I'd like to put some kind of disclaimer in case somebody else used my source code and then got hit by Valve or anything. To state that I don't have a right to the IP contained and that the use of these files is at the risk of the user, not me; so they couldn't point at me, claiming the game was fully open sourced by me under MIT (which I plan to use). What would the best approach in this be?
IF part of your code and data is non-open-source, you can't release this software under the MIT license. However, from what I know, CS:GO uses real-life weapons, and their names aren't protected by copyright. Weapon stats aren't copyrightable either. With skin names, you should be safe as well, since there isn't enough (or any) lore around them to establish them as literary works. However, if you are using any in-game descriptions or images, they are copyrighted content and can't be legally copied without permission from Valve. Which might be easy to obtain by writing them.
Copyright never protects ideas or processes, it only protects expression: words, images, and sounds, some of which may describe ideas. But when a work is nothing more than a translation of an idea into words, with no independent originality -- when almost anyone would use more or less the same way to describe the idea, then the work will not be protected by copyright at all, as it is not considered an "original work". Computer code that implements an algorithm often falls under this rule. It is my belief that the code shown in the linked SE thread would fall under this rule, and would not be protected by copyright at all. If this is correct, then anyone may share such a program with no copyright concern.
The fact that a developer is showing off work that he/she has done for other another company doesn't imply that that developer owns any copyright to the work. In Canada, see the Copyright Act, § 13 (3): Where the author of a work was in the employment of some other person under a contract of service or apprenticeship and the work was made in the course of his employment by that person, the person by whom the author was employed shall, in the absence of any agreement to the contrary, be the first owner of the copyright and § 13 (4): The owner of the copyright in any work may assign the right... In the US, see 17 U.S.C. § 201 (b): In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. and § 201 (d): The ownership of a copyright may be transferred... "What rights should and should not be attributed to the developer?" That is a business decision to be made on a case-by-case basis. Advice about the prudent balance of copyright between an employer/client and employee/contractor is legal advice. "Is it okay to use this projects as part of the developer's portfolio?" If the developer can link to public use of a product that he/she developed for a company, then the developer is not violating copyright by simply advertising that they worked on the product and linking to, without reproducing, the work. If the developer for whatever reason maintained copyright ownership in the code and other assets, it would not be copyright infringement to reproduce those as part of the portfolio. If the developer did not maintain copyright ownership in the code or assets, reproducing those may be copyright infringement, dependent on whether the copyright owner allowed the developer to reproduce those elements, or if the reproduction is fair use. There may be other laws or contracts implicated, though: non-disclosure agreements, trademark law, among others.
In general this is protected by the first amendment. It is not in general a problem describing how one can one can do something illegal. But there are special cases to be careful with. You might want to do some research into the limits on free speech. It would be hard to provide an answer that fully covers all your different cases and you would need to be more specific about what illegal activity you want to describe. In describing how to do something illegal, you might accidentally share information that you are not allowed to share. When you post things online, this can be considered as publishing or exporting. Therefore certain export restrictions might apply. Also, It is illegal to publish bomb making manuals, with the knowledge or intent that this information be used to commit a federal crime of violence. See https://www.law.cornell.edu/uscode/text/18/842. There are restrictions on publishing material relating to cryptography without having an export license. Granted, this isn't necessarily related to publishing things that are illegal, but just to give an idea about how publishing/exporting knowledge can causes problems. See https://en.wikipedia.org/wiki/Export_of_cryptography_from_the_United_States ITAR (International Traffic in Arms Regulations) sets restrictions on what you can publish about arms. What you publish can't be “directed to inciting or producing imminent lawless action.” See for example https://en.wikipedia.org/wiki/Brandenburg_v._Ohio. One might imagine that you could get into trouble if someone interprets what you do as inciting or producing a lawless action. It might sound obvious, but you want to make sure that you have the right to share the information that you have. The information that you are providing might be copyrighted in some way.
Of course you have to follow the license. You seem to have a license that doesn't allow distribution and want to know if giving copies to the Dutch or Chinese branch of your company is distribution. First, you should not make that decision. Your company's lawyers should do that. Second, such distribution is with some licenses perfectly legal if you distribute the software with source code. That's a business decision which you or your manager or his/her manager... can make. Such questions (whether giving a copy to your Dutch branch is distribution) often don't have an answer that is yes or no but maybe - if you went to court, would a judge say that it is distribution? The answer is quite clearly "maybe". So unless you can find a safe way, there is a risk. Again, your lawyers will assess the risk.
It's questionable, because if you design your own visual interpretation of the T-Shirt then it isn't necessarily the one from the book and thus your art has it's own copyright. However, if the current Copyright Holder and Possible Trademark owner is selling the shirt it could be an issue because yours is not official but being sold as one. If you're making it for non-sale and just cosplay, than you have a better arguement.
You need to check if the original game developers patented the mechanics/rules of the game. For your example, Monopoly was patented, but expired in the 50s and while it would not be a copyright violation to mimic the rules/mechanics, it would be a different intellectual property violation (patent infringement). Spry Fox vs LOLAPPS is also relevant as it extends copyright protection to the implementation of an idea, but ideas (like rules/mechanics) cannot, by themselves, be copyrighted. This means that there is an avenue for the original developer/company to sue even if the visual/audible aspects are different, but the overall gameplay is the same. Also see Tetris Holding LLC vs Xio Interactive Inc. as it relates to the visual aspect of the game.
This kind of quotation, for commentary, criticism, or reference, is generally allowed without obtaining permission. In the US, this falls under fair use (see 17 USC 107. In the UK and most commonwealth countries, it falls under fair dealing. In other countries there are various exceptions to copyright that will probably cover this. Even answers that do not directly quote the rule books often use information from those rulebooks to write an answer. Facts and ideas are never protected by copyright, so this is not going to be an issue. See 17 USC 102(b), which provides: (b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work. As a comment by user Trish reminds, game rules are facts and are not protected, although their exact wording may be.