"Unity" prefix in custom package asmdef name

Question

Over here there are some examples of how to name asmdef files, e.g. "Unity.[YourPackageName].asmdef", etc.

Question: Is this "Unity" prefix actually allowed/encouraged? Or are we supposed to use a custom prefix, to avoid making it look like the package was developed by Unity? The linked documentation is a bit unclear about this imo...

Answer 1

I sent an email to trademarks-team@unity3d.com and got this reply:

Thank you for your email to our Trademarks inbox.

We have reviewed your concern - thank you very much for highlighting the inconsistency in our Documentation. Our documentation team has reviewed the relevant areas of the manual and has done the following:
  - updated the [Package Layout][1] page to make it clear that the first element of a package name should be 
  - added a note to the [naming a package][2] page to let users know that the examples are based on Unity packages and they shouldn't use the 'unity' prefix in their package name.
These changes will be effective from 28 September after the site's next build.

I hope that helps clarify that unity should not be used as a prefix in custom package names.

[1]: https://docs.unity3d.com/Manual/cus-layout.html

[2]: https://docs.unity3d.com/Manual/cus-naming.html

Answer 2

Answer by Renardjojo · Sep 19, 2021 at 01:12 PM

According to this video: It seam to be more a convention than an obligation. But is encourage you to use the unity convention

Add comment · Show 2 · Share

Hurri04 · Sep 19, 2021 at 03:17 PM 0

Share

Interesting, in the video he says (at 4:42): "Name your asmdef according to the convention which is companyname.featurename.editor".

And on this page shown just before (at 4:32) they also wrote "Runtime/MyCompany.MyFeature.Runtime.asmdef". So is the "Unity" prefix from the page I linked in the OP just an oversight?

I also looked at the Asset Store Submission Guidelines where under "1.2 Legal" it says: "1.2.f Submissions and publisher accounts do not reference unauthorized trademarked names or branded content in images, names, description text, or content/file names. Your product does not contain any brands or names that hold active trademarks. Titles do not start with a brand name or infer an affiliation with a brand. For example, "Tools for Unity" is acceptable but "Unity Tools" is not."

So I wonder, does this carry over to the asmdef name?

Also, what do you use as a "companyname" if you're not a company but a hobbyist? Simply your real name, since that's in the "package.json" file as "author" already anyway? But then what happens if someone forks the package on GitHub to make some changes of their own?

Hurri04 Hurri04 · Sep 19, 2021 at 04:03 PM 0

Share

Some more pages which imply that "Unity" as a prefix might not be allowed:

Unity Package Guiding Principles & Guidelines

Guidelines for using Unity Trademarks

"Unity" prefix in custom package asmdef name

2 Replies

Your answer

Follow this Question

Related Questions