You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The license file in the repo is an MIT. However, Unity has it listed as the standard Unity EULA. I added this library via Git URL in the package manager, but now I'm unsure as to whether or not I could potentially violate Unity's license agreement.
Please note that Unity's licensing stuff is massively confusing to me. All of the free assets I use are also within the same EULA. If I'm just being an idiot, I accept it and apologize for raising this ticket.
The text was updated successfully, but these errors were encountered:
Though Unity disallows an asset to contain a sub-license but: MIT is compatible with Unity's EULA (same as CC0, which is compatible with it too). Thus it's OK to include an MIT licensed asset inside your own asset.
(Again, this is from my understanding, not a legal advice)
The license file in the repo is an MIT. However, Unity has it listed as the standard Unity EULA. I added this library via Git URL in the package manager, but now I'm unsure as to whether or not I could potentially violate Unity's license agreement.
Asset store link: https://assetstore.unity.com/packages/tools/utilities/naughtyattributes-129996#description
Please note that Unity's licensing stuff is massively confusing to me. All of the free assets I use are also within the same EULA. If I'm just being an idiot, I accept it and apologize for raising this ticket.
The text was updated successfully, but these errors were encountered: