Hi,
The custom package system seems to be a neat system to handle external assets/tools for a project. It distincts the specific assets created for a project from the generic assets. It also manages the packages versioning and dependencies.
I am wondering if it is possible to publish a custom package to the Asset Store and have it placed into the Packages folder when the user imports it. That would be handy for the package users to avoid having their Assets folder cluttered with external assets/tools.
I did assumed that was the purpose of the Packages folder and the Package Manager. But it seems that’s not the case since not all packages imported from the Asset Store are placed inside the Packages folder. So I’m a bit confused.
My question is: What makes a package imported from the Asset Store to be placed either in the Assets folder or the Packages folder?
Well the point to that package manager was so they we can import, as users what we need/want, not all that extra bloat, which is common, with most other game engines, in house and other wise. Not sure your experience, but if you ever used an in house engine alot of the times, we have the basics of what is needed in a game engine, and everything else is external as a package sort of speak, which we either use externally or we import , or use a wrapper. This is what Unity was trying to do in this regard. When we release a game, we have huge files with all sorts of crap, that is not needed, so I think they did a better job. ( it still needs work that is for sure) but its better than the old days in that regard as alot of us would spend hours getting rid of crap, that was just not ever needed for the project at hand.
a package, think if it like a Unity project, or think of it like a zip file.
https://docs.unity3d.com/Manual/AssetPackages.html This is an asset package. Which is different from you importing to the asset folder. if you used Unity for awhile , when we are exporting our projects, this is typically what we would do . it keeps all the meta data as well.
https://docs.unity3d.com/Manual/ImportingAssets.html
@Recon3 thanks for the info. I also like the package manager. It seems to help keep things organized and help us strip unnecessary stuff out.
One question though: I want to upload a code based asset to the asset store and I’d love it if it went in users’ Packages folder rather than Asset folder. Any idea how to make that happen? I wonder if it’s as simple just submitting to the asset store a folder structure that follows the prescribed Custom Package folder structure (especially if you have a package manifest in there) then it’ll automatically be a package for users.