How to get an Asset Package successfully published or how to know why its declined

Hi folks,

i have created a small asset and tried it to publish. The first time i got an answer that it was declined cause of "internal conventions". i tried to find out in the forum what "internal convensions" could mean.
Second time it was declined with "Unity Technologies reserves the right at its sole discretion to reject a submission for any reason". I don´t know what to do now? i also wrote mails to get a hint what is missing/wrong or so but they did never answered me. Now i hope to get some answer from the community or even hints what pitfalls can i take into account.

What is the package about?

• It’s a small package to manage Camera(s) and object in huge scenes and to get around float jittering and view far distances.

What is in the package?

• Source code (less than 10 files)
• 1 Demo scene
• 1 scene that corresponds to the PDF file/getting started
• PDF File with a small getting started (English with screenshots) and a documentation of all class and major functions
• some textures for the demo scene

I hope you can help me

 

polish it, add more feature.
maybe if you download standard asset there is some script in camera section that do same thing.

 

i already checked the standard assets and also similar assets, but there is nothing like is i had found.
i will try to add some new features. Its hard because for my purposes this package works fine.

 

Hard to tell from that vague description.
Is the code lovely and polished? Docs all shiny? Does it offer something truly unique/superior to the store.
If I had to guess, which would seem to be the case, "Lacks overall content or Value-Adding-ness"

Which, as you suggest, is subjective but meh,
I am still struggling to understand what your thing actually does to be honest.

If the store people thought you were going to make a million they would have released it... Perhaps think about how you could make it invaluable to all projects - all developers - and then resub


good fortune

 

I agree with @twobob -- you don't necessarily need to add extra features. Just make the core feature polished, professional, and very useful. Several people contributed to a list of ideas on How to Make Better Code Assets. It's a useful list to help make your product more publishable. Best of luck!

 

hi,

thank you for this link, it was very interesting! with all the tips i will do a "polish" and than lets see if this will work

I find it a pity that the asset team a not a few keywords leaves for which reasons it was rejected.

thanks you all