Why do you have to accept a licencing agreenment before installing Java but not C++? There is a license to use Java which you must accept before installing. Why isn't there one for C or C++? If there is, where can it be found? I'm guessing it has to do with how Oracle owns Java, but in a sense can't you say whoever makes the C++ owns it?
The reason for this is simple: You can’t install C or C++. C or C++ is just a programming language and C/C++ code compiles to machine code. Machine code can directly be executed by the processor (CPU) in your computer. Java, however, is normally compiled to byte-code only a Java Virtual Machine can execute. And this Java virtual machine is what you get from Oracle and Oracle wants you to accept a license agreement. You likely also have accepted some kind of license agreement when you began using or bought your computer. That’s the same you did for the Java Virtual Machine, but this time for your whole computer, which includes the processor that is responsible for executing the machine code. Java in this context also refers to the Java libraries that ship alongside the JVM. While C or C++ also have standard libraries they are part of your operating system and you have agreed to a license covering them when you installed your operating system (or began using it).
The GPL doesn’t require you to distribute the software to anyone. The only requirement to distribute something is that if you do distribute the software to someone as a binary, you must also distribute the source code to them at no additional charge. The focus of the GPL is ensuring freedom for people who have copies of the software, not ensuring that the software is available to the world at large. Because your final deliverable is source code, you’ve already complied with the requirement to distribute source alongside object code. You have to comply with the requirements in section 5: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”. c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. You have to license the software to the company that hired you under the GPL v3 (since parts of it were licensed to you under GPL v3), so you can’t stop them from distributing it to the world. But nothing requires you to distribute it to the world.
Using software generally does not entail any legal requirement to acknowledge the use of that software, and would only arise as a licensing condition. Google services, including Translate, are subject to certain terms of use especial the part about what they expect of you. They do not impose any requirement regarding acknowledgment, therefore they cannot later demand any royalties. If a translation program imposes any demands on your usage of the program, that has to be part of the original agreement whereby you were allowed to use the software at all.
The terms transfer IP rights only for the New IP, meaning that Customer would own the new stuff. Developer will still own their old stuff, but Customer will have the right to use the old stuff, depending on the license terms. If the license is as in your link, then it is forever (but this is a stub, so I assume that the license will be more specific and possibly restrictive). You retain all your rights to old stuff, customer will not pay royalties for the old stuff, and they can transfer or extend the license, or part of the license, to others.
A TOS is not intrinsically illegal, but an interpretation of a TOS may or may not be supported by a court, that remains to be seen. It probably does not constitute a &quot;deceptive practice&quot; under FTC standards. The TOS is your permission to use the software, and there can be no question that they have the right to impose conditions on customer use of the software. E.g. Amazon cannot freely use software that is only licensed for free educational use. They speak of &quot;ownership&quot; of IP so created and explicitly disclaim any claims about Current Law in Your Jurisdiction. At the crucial point in the agreement, they switch to talking about the license (BY-NC) that they grant when you are not a paid member. The exact details of this ownership are not part of the free tier TOS, but they do seem to add certain protections to &quot;owned&quot; content created under the Pro plan – they are under no legal obligation to make all content universally visible and usable.
Your understanding of the GPL is a bit off. GPLed code doesn't generally force you to GPL the output of the program, but that's just because the output of the program is normally not a derivative work of the program. For instance, if you write a novel in Emacs, your novel is an entirely original work. The fact that you used Emacs as a tool doesn't mean that your novel is somehow based on Emacs. This generator is different. It generates sprites by putting together art assets made by the program's creator. That means that the output contains a substantial amount of content made by the program creator, which means that it would likely be covered by the program creator's copyright. If the content was licensed to you under the GPL, you normally have to abide by GPL restrictions when you redistribute the content or incorporate it into your own program. Copyright holders can, if they want, grant additional permissions to their content and allow you to incorporate that content into nonfree software. For instance, the GCC compilers have an additional permission for their runtime libraries to let you use them in any GCC-compiled code; without that permission, GCC could only be used to compile GPL-compatible code. But unless the copyright holder has granted those permissions, when program output contains large amounts of their copyrighted content you're bound by the GPL when using it. In this case, the program specifically says that the art is dual-licensed under GPLv3 and CC-BY-SA-3.0. Since the generator's output is a combination of premade art assets (the buttons just let you tell the program which art assets to combine), the output is a derivative work of those assets. You can't use it unless your use is compatible with the GPL v3 or CC-BY-SA-3.0 (either works, since dual licensing lets you pick either license).
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!
Section 1 of the GPLv3 states: The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. So Makefiles are clearly included if they exists. The point of the GPL is to let the user be free to modify the code. A lot of projects are very hard to modify without the scripts used to fetch dependencies &amp; build the executable so not providing means to build the code would go against the license spirit.