How do I know if a game I made is copyrighted? I am using the unreal engine that supports c++ language. Now I don't know anything about copyright and I don't know how to know anything about it. I live in Egypt. I worked on a game for 8 months. The problem is that I used the Ben10 character and I do not know if this is legal or not. I am afraid that something bad will happen to me
If I lock you in a room without access to anything and tell you &quot;Write a novel&quot; and you write a novel with characters, you have copyright in the work. But it's not absolute: If you use your own characters, you own all the copyright in the work, but not in the idea, as ideas are not copyrightable, see Feist v Rural. If you use someone else's characters extensively (as in more than a short hommage/cameo), you very likely make a derivate. You own a copyright in your part, as in the expression of the story or pictures you created, but you do not gain property interest in the existing characters' expression. Since the copyright to the characters lies with the owner of their IP, you need their OK to release (and also to even make) your work - as with the owner of a copyright is the sole right to decide on distribution and creation of derivates under 17 USC § 106 (2). Also remember that making an unlicensed derivate work risks having nothing you can sue for in case the original copyright owner lifts your ideas and scenes-a-faire parts and adapts them for their own derivate, see Anderson v Stallone The strange case of fanfiction chains... Now, there is a strange situation when a work is based on a work which is based on a work... Then, publishers and editors start with red ink and the result is, that what people know as Twilight now has nothing to do with the fanfiction it started as (It wasn't Vampires in the original draft), and 50 Shades of Grey ended up striking any and all supernatural from it, despite it having been a Twilight fanfiction originally. By making own characters and own expression of the world, there could be no copyright infringement. US law vs Egypt law? Both Egypt and the US have signed the Berne convention, meaning that copyright is very very similar in the broad strokes that the right to allow or disallow derivates is with the copyright holder. Also, since Ben10's copyright owners are to the best of my knowledge in the US (Cartoon Network Studios &amp; Men of Action Studios), they will sue in a US federal court.
You should probably look up the Open Gaming Liscense (OGL) and what you can or cannot do with respect to it. Generally, classic fantasy monsters (Dragons, Manticores, Sasquatch, Vampires). Are fair use. OGL also allows for creatures that are similar to D&amp;D exclusive monsters to exist so long as the name is changed sufficently. Most &quot;monsters&quot; are in what's called Public Domain and are free to use and modify. Additionally &quot;powers&quot; of a monster (or superhero) aren't generally copyrighted but the totatllity of their use in a work can be (does your superhero fly? Is super-strong? Is invulerable? Can be fine. Is he named Clark Kent? That's a problem). Fair Use also allows for some parody but again, it's a defense to copyright infringment and not a liscenses to take someone elses work wholesale. It also doesn't stop them from suing you, as you have to claim fair use as your defense if and when each suit arises. I'd recomend looking at National Comics Publications, Inc. v. Fawcett Publications, Inc. for an example of an intellectual property dispute that is close to yours. Note that Fawcett won at trial but lost on appeal and rather than take the matter before SCOTUS decided to settle out of court.
Whoever "derived" the illegal derivative work most likely has copyright in his derivations, unless they are not worth copyright protections. Say I take the Harry Potter books and add a few chapters and try to sell it - that's copyright infringement of course, but I have the copyright on these additional chapters. However, I don't have the right to allow you to copy the derived work. And even if you have the right to copy the original work, you don't have the right to copy the derived work because it is a different work. I could extract my changes, and allow you to take them and do with them what you like. You could then create an illegally derived work yourself. I couldn't sue you, but the original copyright holder could. To the comments: One, a work and a derivative of the work are not the same, so even if you have the right to make a copy of a work, that doesn’t give you any right whatsoever to copy a derivative work - they are not the same work. Two, the copyright holder has the exclusive right to control copying and the creation of derivative works. If the copyright holder doesn’t want derivatives to exist, then creating them, copying them etc. is always copyright infringement.
I'm assuming that you are not seeking to change the license, and so it will remain GPLv3. As long as you've built on the original software, that license still applies. You also need to keep the previous copyright notices, including the names of the original people. Assuming that, everything you're doing is legal, which is what's on topic here. There is some etiquette around forks (which is what you're doing), which would be on topic at the Open Source Stack Exchange. I'm puzzled by your desire to have a different license text. You can't change the license from GPLv3, so that has to stay the same. (If the original has GPLv3 "or, at your option, any later version", you can drop the any other version text if you like.)
If you do not have permission to make and distribute reproductions of the work, then it is illegal to make and distribute reproductions of the work. US copyright law Indian copyright law
To answer the question in your title: Yes, software licenses are copyrighted. They are written works that involve (significant, expert) creative effort to create. The best solution would be for Grammarly to hire a lawyer and say "we want a new EULA. We think this one covers a number of points our current one doesn't". Most legal documents will be copyright for the same reason (there may be a few that are so stereotypical that there is essentially no creative effort in putting them together).
Using it without permission is copyright infringement and illegal. Legally, you can try offering money to the company for the copyright or for a suitable license. For example offer them $1000 for a copy of the code licensed under the GPL license. If they accept, you are fine.
The code is copyrighted. You are not given any permission to use or copy any part of it, nor to create a derivative work based on it. There is no way for you to "make the copyright null". The code was copyrighted in 2005, and the copyright will not expire until 70 years after the death of the author, under US law. The period would vary in some other countries, but in no country that I know of will it expire in the next few years. That the author is dead, or the publisher out of business, does not change this legally. Someone, probably the author's heir, or perhaps whoever bought the remains of the publisher's business, will own the copyright. However, the ideas and programming techniques shown and discussed in the book are not protected, and you may use them freely to write programs, commercial or non-commercial. You need not even acknowledge the book as a source of ideas, although to do so would be nice. Of course, since the author is dead and the publisher not active, if you were to infringe the copyright by copying code from thsi book, there is a reasonable chance that no one would notice, but if someone did notice, the current owner of the copyright could sue you for infringement, and could perhaps win sizable damages. It would be safer to write your own original code using only the general ideas from the book. In future, do not ever assume that you can just take someone else's code (or other creative work, such as a book) and reuse it without permission, unless it is in the public domain, for example because it was published before 1923.