Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Feedback Please allow publish package with dependency on asset of anyone

Discussion in 'Assets and Asset Store' started by Thaina, Mar 4, 2023.

  1. Thaina

    Thaina

    Joined:
    Jul 13, 2012
    Posts:
    904
    I would like to propose that every asset should be allowed to declare dependency on any asset, not limited by asset we had published ourselves

    Maybe limited by asset that we owned from the store. But imagine we could buy art asset, then publish template or helper script or additional decorate texture that useful for those asset. If we can declare dependency on asset of another publisher, the people who already bought original asset can buy our new asset with small price. While the one who don't will also need to buy original asset from original publisher
     
  2. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    2,436
    This is possible today. Check for the various assets like „xyz for Playmaker“ where the asset will only work if Playmaker is installed in the project.

    As to scripts for art assets, you would not gain anything from adding an art asset dependency - your asset‘s scripts won‘t magically appear on those art assets. You would still have to do what you can do today: use an editor script to manipulate other assets.
     
  3. Thaina

    Thaina

    Joined:
    Jul 13, 2012
    Posts:
    904
    The point is, this is not a good experience. It should be officially supported as assetstore publishing feature

    It should be explicit stated at the `Buy now` button that this package will also make you buy the depended package. Also calculate the sum of all package required on the price UI. Without that people may have been misunderstand that the only price they need to pay is just on the package

    As you can see, Car Setup For PlayMaker is 24$ but Playmaker itself is 65$. People might bought 24$ and stumbled that it don't work unless they need to pay 65$

    You can create prefab over art asset, and that was the point of making dependency. We can sell asset that only contains prefab and script but using model, texture, material, etc from other package and so people would just using prefab to make thing work faster

    Not only that, being updated package we can make prefab variant and any other variant supported by unity
     
  4. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    2,436
    You would still be buying two separate assets. Buying both at once would not make the experience any better.

    In fact, who gets the support request when you purchase these two assets at a point in time where one is not compatible with the other due to an update of either one?

    You can only strike a deal with another publisher so that you can hook into their sales. Like, there is an editor and then there might be an editor with art bundle asset where the art publisher gets part of the sales from the editor publisher.

    I would like something similar, for example when making a race game template i do not wish to create my own car controller, but currently the only option is to do just that AND provide support for other (popular) car controllers. Alas, I cannot see this happening both technologically and from the publisher revenue sharing perspective without making custom deals, like two devs bundling their art and code assets together in a game template published by either one or even a company they form to do so.
     
  5. Thaina

    Thaina

    Joined:
    Jul 13, 2012
    Posts:
    904
    What you are saying is like you never ever buy upgrade package

    It was the existing UI that already supported in unity assetstore. It show the full price that would like it made buyer buy 2 packages at the same time, both current and the original package. But if customer already bought the original package it will show another cheaper price like it was cut the original package out

    What I trying to propose is just, we should allow to make upgrade package over any package, not only from self publish package. And if possible it should allow making multiple dependency, so that publisher can make a bundle upgrade from multiple asset

    if the original package was updated will cause conflict then we can set the system to have download compatible version, like UPM system, for example, Unity.Mathematics have new version, but Burst still compatible only with older version

    And customer can update the original package at their own risk. Or wait for the upgraded package followup publishing newer version

    What I am saying currently is, from my experience there are many zombie asset (not a literally Zombie asset) that was being discontinued or the owner just don't have time to maintain it. It was a great asset but it not compatible with new version of unity anymore, especially URP

    Convert to URP is not hard but tedious. If there is an upgraded asset that convert the old asset into URP that asset would still be alive. So it very tempting to republish that package as URP. But I want it that the asset will share the income back to original owner. And if anyone already buy that package it would be upgraded in cheap price so I, the one who upgrade it, still got some income

    This is something that should be done automatically without the need to asking the owner. The possibility also vast. There could be artist who want to make texture just for model of another package or create additional shader and material for some package. Which would make assetstore economic more lively