While perhaps not identical, I have noticed that Decalmaker seems to save it's decal preset "automatically", if the decalmaker plugin was present and active on the atom while an appearance preset was created, and is then able to automatically associate this specific decalmaker preset with said appearance preset whenever the appearance get's loaded again.
(For example, if you open a new scene, add a new person atom, first load the appearance preset (which had decalmaker active while it was created) onto this atom, and then afterwards add the decalmaker plugin.)
Decal maker will then provide the following popup message:
While I am uncertain if this decalmaker info is written directly into the appearance preset file, or if decalmaker uses it own seperate presets that it simply "checks" upon adding the decalmaker plugin to an atom.
It made me wonder however, if perhaps this is a similar route your Hidepubes plugin could take, in order to bypass the save/load issue you mentioned earlier
@PrettyFrank where it perhaps tries to save and merge load a hair preset in a similar fashion? (A preset which only includes the tagged pubic hairs)
