Code-Stage / Package2Folder

Allows to import Unity packages into specified folder to avoid your project's root bloating.
Mozilla Public License 2.0
62 stars 15 forks source link

Hope to support import asset from in Window/Package Manager/Import #6

Open mrkyee opened 1 year ago

mrkyee commented 1 year ago

I'm sorry for forgetting to reply for so long. Currently, it seems that only a local .unitypackage file can be supported by dragging it into the Import Asset window. However, I usually import resources from Window/Package Manager/Import. In this case, I cannot specify the import path. Is there any plan to support this situation?

DmitriyYukhanov commented 1 year ago

Hi,

Thanks for getting back with a reply.

Do you mean My Assets tab in the Package Manager?

I believe all usual (real) packages are installed into the PackagesCache folder (or sit in the Packages folder) and changing their import path seems to have no sense.

mrkyee commented 1 year ago

Yes.But i need to find PackagesCache folder .I want to do everything in unity rather than searching for them in folders

DmitriyYukhanov commented 1 year ago

I am not sure if I fully understand, sorry.

/Library/PackageCache folder is not intended to be altered and all real packages in the project which do install in there are no intended to be placed under the /Assets folder.

Most Asset Store packages sitting in My Assets tab of the Package Manager are made as vanilla .unitypackage and install into the /Assets folder.

However, as it's now allowed to publish assets as embedded packages to the Asset Store, some packages from the My Assets tab are actually real packages with special inner structure, and they will install into the project's /Packages folder (they become embedded packages when installed).

From what I can see, Package2Folder could be helpful only in case when you need to change the installation path for the "vanilla" assets which extract to /Assets folder.

Does it sound like something you're asking about @mrkyee ?

mrkyee commented 1 year ago

I'm not sure how to explain my question, but here's an example. I recently purchased a resource from the Unity Asset Store, and it will be displayed in the Package Manager under "My Assets". If I want to import it into my project, obviously I need to take the following steps:

  1. Download it locally. image

  2. Click "Import".

image

  1. At this point, a window will appear showing the resources that need to be imported. However, it's often at this step that I run into problems, because the publisher may not have put the package in the standard plugin directory, and that's where my frustration lies.

So my request is to support this situation, because often when I import resources, it's through this way, rather than going to the cache directory to find the corresponding .unitypackage file and drag it into the Assets directory.

DmitriyYukhanov commented 1 year ago

Got it now, thanks for explaining it in all details.

Yeah, that would be nice to have indeed, but currently I don't have any ideas on how to inject into the importing process to route import into a different folder.

This needs some investigation to find out if it's possible. Unfortunately, I'm too tightly packed now to give any ETAs for this, so please just follow this issue for any updates.

mrkyee commented 1 year ago

You're too kind. Looking forward to your next update.