VaM 1.x What to do with depended plugins in different versions?

[YHNF]

I have many scenes that require the same plugin but in different versions, Should I just keep the lastest version plugin only?
Will this create problems for those scenes that depends on earlier version?

Eg, I have like around twenty different versions of accidbubble.timeline, they are all tide to different scenes that I have. And same applies to many other plugins.
The folder looks like a mess and I wonder if I can lighten it up a bit.

 

[Geraldo]

This is related to how the original creator packaged his resource. The moment a creator makes a .var, they can adjust the reference to a dependency to be "Exact" or "Newest". Probably they need an specific version of the referenced .var for their resource to work, and other versions might break it. To clean up your AddonPackages folder, you can use this, which scans unreferenced .vars. That way you can safely remove resources that are not being used by other resources, just remember to create a whitelist to not move unwanted content (like specific looks).

 

[pingox]

This is related to how the original creator packaged his resource. The moment a creator makes a .var, they can adjust the reference to a dependency to be "Exact" or "Newest". Probably they need an specific version of the referenced .var for their resource to work, and other versions might break it. To clean up your AddonPackages folder, you can use this, which scans unreferenced .vars. That way you can safely remove resources that are not being used by other resources, just remember to create a whitelist to not move unwanted content (like specific looks).

Do you think the one you mentioned is more complete than this one?
(I was about to try this ‘Delete Obsolete Packages’)

 

[Geraldo]

I don't know, never used this one.
But what I like about VARManager is that it doesn't automatically delete anything, it just moves to a new folder such that VAM doesn't load the files (which helps with performance and load times). Then from that new folder, you can choose what to delete or not.
You can give a try in both and see what you like.

 

[pingox]

I don't know, never used this one.
But what I like about VARManager is that it doesn't automatically delete anything, it just moves to a new folder such that VAM doesn't load the files (which helps with performance and load times). Then from that new folder, you can choose what to delete or not.
You can give a try in both and see what you like.

I'll do that. The one you mentioned seems pretty powerful. Thank you.

 

[SlimerJSpud]

The default mode in Vam is for plugins to always use exact, and most other resources to use latest. It's not something a creator normally changes. There's a tradeoff here. If you delete (or move to a holding area) all the old versions, then every scene that used those old versions will have missing dependencies. This reduces the value of the Scan for missing dependencies screen in game. If you just click download all, the old versions will be reinstalled. You would have to use Package manager to mark all of those scenes to ignore missing dependencies. Then you can keep only the latest version, and not get tripped up by the missing dependencies screen. Obviously, this would be a huge task for something like Timeline, which is used *everywhere*. I only do this (mark scenes to ignore) for plugins that have had serious bugs fixed, and which can do damage if old versions are still around. Life is one of those. I force every scene to use Life.14 because of this.