Can I claim copyright if my code is used in a game without full payment? I wrote a game's code for this guy, he has paid half of the agreed amount when the code was delivered, but when the game was published, and I asked for the rest of my payment, he denied and blocked me. The agreement was verbal (discord chat), and I've kept a record of the whole conversation in its original format and a recorded video. The publisher of the game ignored my take-down request sent through email, so did itch.io, didn't reply at all. subscribestar has answered and seemed very understanding, but my code is still up on their platform and haven't been taken down yet. Do I have any legal recourse here?
Yes, you do. But you should not base your claim primarily on copyright, but just on the license contract you agreed to. It's typically much easier to prove that a party did not fulfill its part of a sales contract (here: Pay the agreed amount) than to prove violation of a copyright you own. Also, you then only need to sue one guy, and not care about every platform your game might be hosted on. This is particularly difficult here, since they have not done anything wrong. It's not their fault that the publisher didn't properly pay the programmer. They (very likely) got their copy of the game legally. For details, you should consult a lawyer. We can't give you detailed legal advice.
This appears to mean that the author, while retaining copyright, is allowing anyone to make copies without asking permission from the author. This would seem to be similar to a CC-BY license, or perhaps more exactly a CC-BY-ND license, as the author has apparently not granted the right to create modified versions or other derivative works. This does not require one who makes such copies to distribute them free of charge, unless there is another provision not mentioned in the question. Amazon, or anyone else, would be free to sell copies at any price they cared to ask. If the author wanted to limit the sales price, that would take another provision, and might not be enforceable.
This answer is limited to United States law. The situation in other countries is definitely different. Under United States law, the owner of a lawfully made copy of a copyrighted work has, as a right of the physical possession of that work, the right to the work's ordinary use. Licenses grant you additional rights such as the right to make derivative works, the right to make copies beyond what's needed for ordinary use, and so on. A pure license doesn't ask for anything in return, it just gives you new rights. Those rights may be conditional, but the conditions are just things you have to do to get new rights. They're not conditions imposed on any existing rights you had. A contract is an agreement between two parties. Both parties must agree to a contract for the contract to be enforceable. Contracts can take away rights you otherwise have. You don't need a license or contract to use a copyrighted work if you lawfully possess a copy of that work. Say you download a copy of a work covered by the GPL. You can refuse to accept the GPL license and you can still use that work. Why? Because no law prohibits you from doing so and there is no civil cause of action for using a lawful copy of a work under US law. But now say you want to give a copy of that work to your friend. This is illegal under US law because 17 USC 106 restrict that right to the copyright holder and there's no applicable exception since that's not part of the ordinary use. For a work covered by the GPL, the license offers to give you that right, a right you wouldn't otherwise have. It imposes conditions on you that are specifically in exchange for the grant of the new right. If you do accept the GPL, it functions as a contract. You got in exchange a right you didn't have before and if you don't comply with the GPL's terms, you don't have the copyright holder's permission to exercise those rights which is required under the law. By contrast, a click-through or EULA takes effect when you agree to it and such agreement is a condition for using the software. That's a pure contract and usually doesn't give you any rights you wouldn't have in the absence of such an agreement other than the use of the software.
The first thing that people need to do is to quit over thinking it. That being said, I'm going to see if I can tackle your problems one by one, before summarizing and providing my own opinion: Many users don't care if their code is copied. I'm like that. I left a couple comments on Shog9's post that read this: Good point: Licensing does not prevent careless or malicious use. I'm surprised about how many people are thinking that this license will let them steal their code, because it's already happening right now. I don't want to sound pessimistic, but when thousands of people break a license/law/contract, it's a bit of a lost cause. You're not significantly damaged in a direct way, so honestly, let it go. All I want is to make sure that no one can come up to me if something of mine screwed something on there side. Aside from that, I don't care about people who don't attribute me: chances are, they have no moral sanity, and I will appreciate the people who do, and help me out. As it is, I'm 16, I share what I know with a good heart, and in a well-spirited manner, and at the end of the day, knowing that I was able to help someone out makes my day. I don't mind if my code is copied. I know that people will copy my code whether I like it or not, but I also know that there will be people in the world who will say "thanks", and will try to attribute me where possible. I feel good about that. That being said, I don't care. But the person who uses my code does. The license that affects all Stack Exchange posts are licensed under the Creative Commons Attribution Share-Alike license, or CC BY-SA. Code contributions don't fit well with this. This excellent post on Open Source explains why it's discouraged for code. What these people want is a code-friendly license, so that they can stay in the clear when it comes to copyright issues. The next thing they want, is for someone to come after them over some licensing issue. You may think that people are good, but you never know the world around you. They can be evil. For other users, they don't mind their code being copied to another post, as long as there is a link to the post and a mention of the original author. Most people post with good intention. There's not that much of an issue from a legal perspective either: The license allows people to copy and paste into answers of their own, and since the license remains the same, there's no issue to get into. The license allows it, and contributors kind of have to acknowledge it. I don't think anyone cares what happens to code that is less than 3-4 lines at least. I can probably agree. Such code probably wouldn't be eligible for copyright anyway, since it's so trivial. Many jurisdictions have a "Threshold of Originality," which means that simple things can't be under copyright. Stack Exchange does not probably want people to own the code they submit. For example, Stack Exchange has (and probably wishes to retain) the right to keep even deleted posts in the visibility of the high rep users (even if the author is against it). Wait what? You may be right that it is in Stack Exchange's interest to host content. After all, they get hits, which helps them as a business. It is illegal for companies to host illegal content. If somebody sees objectionable, copyrighted content hosted on Stack Exchange that they would like removed, then they need to file a DMCA Takedown Request. This is also why moderators, like myself, cannot process legal requests. The reason why Stack Exchange doesn't act themselves, even if they see something that is copyrighted and objectionable, is because it's a form of liability. When YouTube began removing copyrighted content themselves, they received a wave of lawsuits (If you remove some, you need to remove all. Why didn't you remove mine? being the argument). The plaintiff's won those, and when YouTube did nothing, they weren't liable at all. If a user wants to have their content taken down, it's tricky. You need to look at the Terms of Service for Stack Exchange: (quoting Section 3) You agree that all Subscriber Content that You contribute to the Network is perpetually and irrevocably licensed to Stack Exchange When Stack Exchanges gets your content, you grant them an irrevocable license to your contribution. This is pretty standard across a lot of sites: it's just a way to secure data and stay in the clear of licensing issues. At the same time, it doesn't seem fair for SE to acquire complete ownership of the content. The user must still have the final say, if the content is to be used for purposes not already agreed upon in the licence. They don't. What users have done is that they have provided a license of their content to Stack Exchange. This is done, again, through their Terms of Service: You grant Stack Exchange the perpetual and irrevocable right and license to use, copy, cache, publish, display, distribute, modify, create derivative works and store such Subscriber Content and to allow others to do so in any medium now known or hereinafter developed (“Content License”) in order to provide the Services, even if such Subscriber Content has been contributed and subsequently removed by You. The user grants a license to their content to Stack Exchange, but they do not assign or relinquish copyright. The code still belongs to them. It's important not to conflate the user contribution policy, with copyright assignment. You are still free to add an additional license to your content (known as dual or multi-licensing), and have a copy for your own use. Stack Exchange will always host a copy licensed under the CC BY-SA license. Stack Exchange can expect a high level of decorum and respect for laws from its users. At the same time, it cannot expect redundant attributions anywhere and everywhere, because one of its main aims is to not waste the users' time. Not only Stack Exchange expects it, but many copyright laws in various jurisdictions require it too. There's a concept known in many jurisdictions known as moral rights. These are rights that are irrevocable, whether you like it or not. Generally, these include attributions, disclaimer of liability, and other rights as well. Even if your work is in the public domain, you still retain these moral rights. If memory serves me right, the right to be attributed is revokable under United States copyright law. Therefore, attribution becomes more a courtesy, when the right is revoked. Licenses such as CC BY, and CC BY-SA still require attribution as a part of their licensing terms. What defines attribution is generally up to the person who uses the content. If memory serves right again, one can not demand how to attribute. There should be a clear-cut way to determine what is code and what isn't. The code formatting indicators on SE may not be adequate because some users simply use backticks, or 4-space indented text for other not-so-codey text. Personally, I feel like making the entirety of a post under both the Creative Commons license and whatever proposed code license they use is the best option, and allow people to use moral judgement to determine the most appropriate license. The concern comes about people who lack such judgment. I bet these same people don't follow the existing license anyway - and are a lost cause. We made it through! There will always be debate on the license of choice. Some people want the GPL, a license that's apparently closer to the status quo of Creative Commons license (I disagree that it's a good match), while other's want permissive licenses, such as the MIT or the Apache licenses. I'd prefer the permissive type, since it allows use in closed-source applications, and grant more rights (i.e. less restrictions) to the people that use them. I'm not going to right much because my hands are tired, but I'm sure if you've got more questions about the open source licenses themselves, you can probably ask on Open Source Stack Exchange.
The DMCA prohibits circumvention of technological measures that effectively control access to a copyrighted work. So you can't legally "crack" the software, period -- even if you own a disc containing the software and have a valid license to use it, a license to use the work is not authorization to circumvent access controls. So if the disc is copy-protected, by my understanding of the DMCA, you're kinda screwed. (The company might be willing to provide you a replacement copy, even if only to maintain the illusion that the software is "licensed, not sold". But you can't make one yourself.) Likewise, if you have a copy of the disc but have lost the license key, you're screwed. Even if you could prove beyond any doubt that you are the licensee, there's not any law i'm aware of that would compel the copyright owner to provide you another license key. And courts have held that distribution of license keys without authorization is a violation of the DMCA. So whoever might provide you another key, if they're not the copyright holder, has broken the law. If you managed to copy the disc from a friend (without circumventing any kind of copy protection), and had your own license key, you might be in a better position. Many EULAs allow you to make a backup copy. Even if they didn't, copyright law does, so there's a possible case for fair use.
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.
Yes The relevant legal concepts are copyright, contract law and the Computer Fraud and Abuse Act. You are liable to be sued by the people affected for damages and/or be prosecuted by the government for the felony under either or both laws. Let's start here: "I bought a game". No, you didn't; you bought a licence to use the software in accordance with the terms of service (licence) that you freely agreed to. All modern ToS will not allow you to reverse engineer the software. If you breach those terms of service then you have broken a contract - that is what allows them to sue you. They will no doubt argue that the prevalence of cheat routines developed by people like you reduce the number of people willing to play the game - say 100,000 users x $10/month * 12 months = $12,000,000. They will also ask the court to impose punitive damages to discourage this sort of thing. Which brings us to the copyright violation. You are allowed to copy their software provided you comply with the ToS. But you didn't. Therefore you are in breach of the Copyright Act and subject to additional civil and criminal sanctions. Finally, your "cheats" access their servers in a way that the ToS doesn't authorize. This puts you in breach of the CFFA - breaking this carries serious jail time penalties. Not to mention that in the US, a criminal conviction will preclude you from many jobs, including, naturally, any with access to company computer systems. Putting aside the illegalities, cheats are unethical and ruin the game experience for hundreds of thousands of people who don't use cheats. You are a criminal - stop being one!
Getting permission from the game owner would be a sensible approach. If you get it, great. Then you could do it with the owner's blessing. It's possible to do your write up without the owner's permission, but then you have to be much more careful. For instance, the names of games cannot be copyrighted. No one can prevent you from writing "A Guide to Bridge," or "A Guide to Chess," etc. On the other hand, some games are trademarked, in which case you will need to attach a TM (trademark) symbol when referring to them. In this case, see a lawyer. You are also allowed to discuss the game itself "in your own words," but you must be careful not to "plagiarize" anything from the rules, or the official game description. That is, while you can refer to specific aspects of a game, such as building houses and hotels, the leash on copying is fairly short, as little as five words. This does not refer to five words in a common sequence referring to a single thought like "The United States of America," but it could refer to five words in an original or unusual sequence such as "I think therefore I am," by Rene Descartes, or "X houses and Y hotels," where the numbers X and Y define the number of houses and hotels in a certain board game trademarked (I believe) by Parker Brothers.