D&amp;D Manual Copyright I'm working on a program for D&amp;D enthusiasts that helps dungeon masters keep track of their characters and streamline battles. I want to transcribe the all the monster data in the Monster Manual so my program can automatically deal damage and so players could look up monster data within the program itself. Would that be violating copyright law if I did that? Edit 1: To clarify, I'm not planning on making any money off of this(Ad revenue or otherwise).
Let’s work it through Is the work copyright? Yes. Are you making a copy or a derivative work? Yes. Do you have permission? No. At this point, it is prima facie copyright violation. However, various copyright laws have defences for breach. You don’t say where you are but as the USA is the most permissive in this regard we’ll use the USA. If it’s not legal there, it’s not legal anywhere. If it is legal there, it’s still likely to be not legal everywhere else. is it fair use? Almost certainly not. Wizards of the Coast (the copyright owner) already do this. While this service is free for creatures from the Monster Manual, it does drive traffic to their web site where they sell stuff. They also licence (presumably for money) others to do the same. Your usage would negatively affect the copyright owners market. This counts against fair use. Because it’s already being done, your work has virtually nil transformative value. This counts against fair use. You are copying a substantial part of the work. This counts against fair use. You are not using it commercially but neither is it for educational use. This is unlikely to matter. On balance: not fair use. TL;DR This is copyright violation.
I would argue that no, there is no copyright for the restored work. Independent copyright is only possible for any original material added, as previously discussed on this site. In this case, the added work was a technical process rather than a creative process, and technical processes cannot be protected by copyright. Copyright licenses would therefore be ineffective. However, I believe one could still impose a license based on owning the copy as opposed to the copyright (contract might be a better term in this case). However, if a third party managed to obtain a copy through some other avenue, any such contract would not be binding on them and nothing could be enforced against them unlike with copyright laws. Another way a license might be imposed is through patent protections, as technical processes can be protected via patents. However, I'm not as familiar with patent law, and this doesn't appear to be the claim being made.
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.
No The artwork is all covered by copyright that, in Japan, lasts for 70 years after the death of the last artist. As employees of Squaresoft, the artists don’t own the copyright, Squaresoft (or it’s heirs or assignees do). So, the copyright currently vests with the successor company Square Enix. They are the only organisation with the right to make or licence derivatives. While they currently don’t want to, they might in 10 or 20 or 40 years and any work you made would damage the profitability of that hypothetical project. So it isn’t fair use. So you can’t do it.
Yes, such a site can be created without infringing copyright Facts about the game are facts.They are not protected by copyright. Criticism of, and comment about the game, is an activity protected by the US First Amendment. Making such comments is very likely to be fair use under US copyright law. In general the author of a work, such as a book or a game, or the maker of a product, has no right to grant or withhold permission to discuss or comment on the work. This is true not only under US law, but also in the law of most countries (perhaps of all countries). The name of the game might well be protected as a trademark. But that does not allow the trademark owner to prevent discussion of the game, clearly identified by the name of of the game. As long as nothing is being sold or rented, or advertised for sale or rental under that name, and there is no attempt to claim that the site is sponsored or approved by the trademark owner, and there is no likelihood of confusion, there is no trademark infringement. This is true under US law, and under the trademark laws of most other countries. A wiki is a specific technology. It can be used for community discussion, or for a company's internal documentation, or for any of many other purposes. Wikipedia has popularized this technology. Not all community discussion sites are wikis, however, nor are all wikis for community discussion. Just as not all novels are books printed on paper, and not all books are novels. In any case, setting up a wiki about a topic such as a game, a movie, or a novel does not require permission from the owner or creator of the game or of any trademarks associated with the game or work. The same would be true for a discussion forum about such a game or work that is not a wiki. If a wiki uses excessive quotes from game dialog, or uses the game's logo without permission, or reproduces other game assets, such as character art, maps, and the like without permission, that might be copyright infringement.
No, this is not true. Copyright can be enforced selectively. You are confusing copyright with trademark. Company can lose its trademark if they aren't protecting it. All the meanwhile they can choose to ignore some copyright infringement while enforcing their rights on others with no legal problems what-so-ever. In order to illustrate the difference: for example, if someone would make a clone of Super Mario and would call their clone as well "Super Mario" and maybe even would call themselves "Nintendo", even if they have programmed the whole game by themselves from scratch and the art and music would be all different, they wouldn't be infringing the copyright but challenging protected trademarks. In your case, the naming was identical, the art and everything was too similar to the original and therefore the clone was challenging the trademark that needs constant protecting.
There is no case law as yet However, the most likely situation is that there is no copyright in the original works because they are computer-generated. There is certainly copyright in the code that created the art but the output of that code, the art itself, would probably not be subject to copyright. Copyright only exists in art created by humans. The US Ninth Circuit has held that animals cannot create copyrighted works. Subsequently, the US Copyright office has rejected applications for registration (a prerequisite to a suit in the US) of computer-generated art because it “lacks the human authorship necessary to support a copyright claim.” While this position has not been tested in the courts, I don't think they are any more likely to grant copyright to a program than they were to a monkey. What's going on? The OP states that there is litigation: there isn't. What there is, is a DCMA takedown request from Larva Labs. If this is complied with that will be the end of the matter; if it isn't then there may be litigation. However, before Larva Labs could sue CryptoPunks in the US they would first need to get a writ of mandamus to force the USCO to register it. If they try and fail then there will be a legally binding court decision that Larva Labs don't own the copyright in any of their computer-generated art. Which kills their business model and, presumably, them. This would be a very high-risk move. They may choose to sue in a jurisdiction where registration is not a prerequisite, however, that court would still need to be satisfied that there was a copyright that could be breached. So that's just a different take on the same problem. I have ignored the issue of NFTs as these are legally problematic in their own right and irrelevant to the main question. However, the NFT and the artwork are not the same thing.
It does mean that you cannot reuse any parts of the source code, even small simple ones. You would have to rebuild the code from scratch. There is a significant chance that the code would be "substantially similar" to the code that you were hired to build, also that if anybody else were to write a bubble sort or 24-to-am/pm conversion routine, it would look the same, where even variable names (which should describe function) are the same or very similar. In case of an infringement lawsuit, you would have to defend yourself by showing that there are only a few ways to code a given function. Copyright protects only the "expression", not the abstract idea. A linked list is an idea, which can't be protected by copyright; same with recursion, pointers, stacks, object-oriented programming... Anything that involves copy and paste is infringement. If you re-read the copyrighted code and then try to reconstruct it, you probably crossed the infringement line. If you remember the problems and solutions and accidentally write somewhat similar code, that is probably on the safe side. From the perspective of the programmer not wanting to always reinvent the wheel, it would be most useful to make a distinction in the contract between "the essentials of the customer's program" versus "incidental utility work". The difficulty will arise in saying specifically what is essential vs. incidental. For instance, I know that if I were to hire you to develop a speech-recognition system, low-level audio-acquisition and encoding would not be essential to my purpose, whereas DSP parsing routines would be the center of my interest. The programmer would then want to retain recycling rights to all non-essential code.