We're glad you've decided to submit your work to the Union Assets Store! This document describes current best practices and guidelines for providing the required content and the images used when promoting products on the Union Assets store.
We look for craftsmanship in assets that would otherwise require a developer an investment of time or money to create. We look for well-made textures, clean geometry and UV mapping, code quality and overall good design. Do not submit a very simple asset, such as a single crate, unless there is something extremely special about it. If you have simple assets, consider making a multi-pack instead. Your submissions should be a reflection of your talent and skill.
Things should work as much as possible out of the box. If there are unavoidable setup steps to be performed by the user, please specify them in the product manuals. Code packages should contain manuals and will not be approved without it.
Submit complementary texts and preview images that justify the quality and usefulness of your assets. You can also entice your viewers by linking to website material, YouTube or Vimeo videos to create an interest among your audience. A short demonstration video usually makes a good first impression and shows what your asset is all about. This is especially helpful for demonstrating particles and characters.
You may not upload content that you did not create or are legally licensed to resell. This includes assets ripped from other games or mods, assets downloaded from Turbosquid or Google Warehouse or any other repository, You may not upload or sell assets freely available from locations like CGTextures or Mayang, for example.
NEVER UPLOAD ANYTHING YOU DID NOT CREATE OR ARE NOT LEGALLY ALLOWED TO RESELL. YOU ARE LEGALLY LIABLE AND CAN BE SUED BY UNION ASSETS LLC, BY THE OWNER OF THE CONTENT, AND BY ANYONE WHO PURCHASES AND USES THE ASSET.
Your submission cannot contain trademarks, logos or branding which you do not own. For example, you cannot have a Ferrari emblem on a sports car. Therefore you may want to check your asset on the US Patent and Trademark Office website. We will not accept submissions that we deem (at our discretion) to be defamatory, libelous, pornographic, obscene or evocative of racial hatred of any kind.
If you are an Online Service, such as a monetization service, ad-network, back-end hosting service, analytics system or other service where a variable amount of money changes hands after the user downloads your SDK or plugin, you may not upload your SDK or plugin to the store unless you are an approved Online Services Strategic Partner (OSSP). Contact us to learn more.
Choose a descriptive name for your asset. Instead of just 'Spaceship' or 'Airplane' consider something like'Deep Space Cargo Spaceship' or 'Classic Italian Biplane'. Use spaces instead of underscores in your package names, and please spell check them if you are unsure of their spelling. Do not name your asset with arbitrary numbers like Zombie 1.. however it’s OK if you name multiple-asset packages with Volume, for example, Zombie Collection, Volume 1. You absolutely cannot include brand names like Ferrari. Be aware that most guns and weapons have trademarked brand names as well, and we will not accept a model called Uzi, for example.
Code packages should contain manuals and will not be approved without it. You can also create manual section for any type of content, especially if you feel that you need to share some information with your customer before he or she will start using your package.
Use *.unitypackage file if you selling content related for Unity, and *.zip for the another type of content. If you want to use another package format, feel free to contact us with the explanation why do you think this file format will be most convenient for the your customers. You should do this befor submiting package for review, otherviwes you will get decline due to file format.
The Graphic assets should sontain source files, like mb, .ma, .max, .c4d, .blend, .3ds, .psd, .ai, etc. Since it allows customers to customize premade graphics.
Graceful handling of errors: Your asset must provide useful warnings to the user if he or she does something wrong. Under no circumstances should your extension throw null reference exceptions, unclear error messages or warnings. Remember that your code will be included in other people's project and too many warnings from 3rd party contributors may clutter up important errors or warnings in their own code. Error messages must be in the form of a message / dialog or inline warning and explain how to fix the problem. Also you should format your code as describe in coding starnders, depends of language you using. You my want to look at:
For complete projects we request a YouTube™ video presentation.
In order to ensure that your audio's volume distribution is even, we recommend you to normalize your content before submitting. When you're finally submitting your audio asset, you must link to preview audio on a webserver, or a service like SoundCloud™.
Often developers ask how they can be featured on the front page. We showcase items that are great products which feature attractive looking key images. If you have a great asset but the art is not visually appealing, we would be reluctant to showcase it. Please take care that it looks pro!
For the sake of consistency, all Union Assets Store offerings are covered by a license we have created. Please have a look at the End User License Agreement to be sure you are comfortable with it. If you are offering your content for free, you have the further option of selecting one of three free-licenses, which override the basics of our commercial license. Please do not include your own license terms in your offering.
The submition guide can be found here.
Please feel free to contact us, if you need further assistance. We look forward to seeing your submission!