Unity is not checking the contents of some asset store submissions

News & General Discussion
1

It is a tad annoying to have asset store items that include every single Unity standard asset in the package. One of them is a 600 MB download, with only 2 MB of that being the actual asset, the other is demo files and standard assets, and other items which aren’t being used at all/

This asset has numerous “Resources” folders which contains the v1.0.3 post processing stack items.

Here are the asset store guidelines:

3.1.d To help users navigate your package and avoid unnecessary clutter, all duplicate, unused or redundant files must be removed from your project before submitting.
3.1.e To avoid inconsistencies during importing, Do not include “Standard Assets” folder in your submission. If you have a demo scene that utilizes any “Standard Assets”, include documentation as to how you setup your scene and allow for the user to import the “Standard Assets” themselves.

9 Likes
2

I think it has something to do with submission… like they rarely accept assets that are small so people put random crap in there … basically the bigger asset the les willing they are to check it properly and just accept it based on screenshots. How ever whole shop is just weird some very trolling assets gets thru quality control and some good not and there are some obviously illegal assets like models of some public persones that surely have given no promission to this. Basicaly looks like shop is run by a 10y kid and not very smart one.

3

No clue where you got any of that from. Initial release of Build Automator was one editor script, few kb large, and that got accepted just fine

3 Likes
4

Report them.

4 Likes
5

Although Unity could solve this if they actually cared. They obviously rate this as a minor issue or it’d been solved. It’s absolutely a trivial thing for them to set a bot off to scan all the asset store packages they have and flag them. Absolutely trivial.

6 Likes
6

My experience is this is a bigger problem with older assets, and they are more lenient on those when they get version upgrades than they are with their brand new submissions. I’m not sure what the correct solution is for these older assets though. Boot them all from the store? Refuse incremental improvement submissions unless they refactor the entire package to the current guidelines? Or just grandfather in the older assets, even updates to them, and only enforce this on new assets?

7

Give them a clear transition period. Any asset not updated to meet current guidelines as of some date in the mid-term future gets removed. Nothing gets removed based on that until then. The vendors can fix it now, they can fix it next time they do an update, or they can chip away at it over the transition period.

3 Likes