Solved A question about the details of the "required deps" (Vam 1.x)

[PVP]

Here's what i notices lately from hub browsing..
There's many creators out there and also a mere mortal like me who sometimes, create some .var and put it on hub, then it's showing that it requires a dep that you didn't know "how come" and "why does it popped up as a dep".

Let's say when you create a look B and posted it on the site, now it's showing that it requires look A as one of it's dependency.
The question is, how can we know about which exactly the part of the resources it actually requires from look B.
Do we have a plugin or other method to specifically address the exact resource it uses? also addressing the target position it will be used on. e.g. ddaamm.hair_01.2 from look A target : look B, person01, section - hair.

Yeah.. something like detailed dep list or detailed dep error report. I hope I put on the right context.

 

[atani]

As a plugin:

VAR Inspector - Plugins + Scripts -

VAR INSPECTOR CC-BY-NC-ND What is it: Var Inspector is a desktop application written in Python which will scan the save files and presets in your var and tell you where the dependencies are located How does it work: Var Inspector creates a...

hub.virtamate.com

As a guide:

How to package like a pro: a guide on proper VAR building - Guides -

Intro There is a recurring issue with VAR packaging. No one's to blame, really, as there is no guide on how to make a "good" VAR package. I'll try to remedy to that. In short, this guide is for you: If you’re about to post a resource starting...

hub.virtamate.com

Manually for a specific dependency:

• Open the JSON - scene or preset you may have - and search for the dependency's name

 

[PVP]

Bookmarked. Thanks a bunch!
I will link them the next time I see someone saying "idk why this pops up here?".