I've made a utility to help people initialize and fix up clothing plugins on their items:
A small utility for clothing creators to initialize Stopper's Clothing Plugin Manager on their clothing, and later fix all Clothing Plugin issues in a prepped package before release. I made this so that I wouldn't go crazy working on my...
hub.virtamate.com
Had to make it or I'd go crazy working on
my Piercings package (~200 items), and I'm here to report bugs I've encountered
1.
The MAIN one is that storables don't get re-applied when loading a scene or a preset. So if someone edits offset/scale/color of my piercings, save their appearance or a scene, and then load it later, they'll see all default values, which is prettyo brokeno
Actually, they do get applied when you load the clothing preset with customization for the 2nd time, which might be a clue to fixing it. I've tried taking a stab at it myself, but failed miserably (couldn't even localize ClothingPluginsManager without breaking everything and my VaM crashing to desktop), so you're my only hope, Stopper
.
2.
CPM doesn't try to resolve local paths. For example, I'm using my own version of your CUA Clothing (I'm gonna write about it in its thread later), so it's a local plugin. It also loads local assetbundle. If I'd package it like this, loading both plugin and assetbundle would not work, because storables contain local paths and CPM is not scoping them to the package.
I've worked around it by adding path de-localization to my utility app linked above. It walks all storables and checks if there are paths to `Custom/*` of `SELF:/Custom/*`, and namespaces them to the package being built, so in my case `qdaro.Piercings.latest:/Custom/*`.
Dunno if this should stay in my util, or be handled by CPM, but it's an issue.
3.
When activating a clothing item that has a plugin that hasn't been loaded before, the permission prompt disrupts the initialization process, and the plugin never loads, even after allowing it. You have to deactivate the item, press the "Clear Inactive Objects" button, re-activate the item, and then it works fine.
This is a problem when loading some scene that depends on clothing items with plugins in them. If the clothing items have been installed to satisfy the scene dependencies, and than user loads the scene, none of the items will load, and they'll never know why or what's wrong.
