Big thanks, Case! I’m glad you like her, and I really appreciate the careful dependency check.
You’re absolutely right about both points. I’ll remove the Wolverine333 package dependency and clean it out of my installation so it does not get pulled back in during future packaging. The Brian.Noa_Custom reference in the README is also leftover wording from an earlier build and is not required by the released presets, so I’ll remove that as well.
Thanks again for catching these. I’m still learning the finer points of clean VaM packaging, so feedback like this is genuinely helpful.
You're welcome! Always nice if people appreciate my nitpicking. I've discovered some other stuff:
1) Your meta.json lists a lot of plugins that your appearance presets don't use - looks almost like initially, you had a scene in that .var that you deleted manually? (Normally, appearance presets don't reference plugins).
vamBear.Adaptive_Texture_Details.1
Skynet.OrificeDynamics.32
Skynet.BetterBends.15
everlaster.Naturalis.73
I think it'd be better if you made dedicated appearance-preset vars from the start.
2) There's a really weird thing in all the appearance presets - some of the morph's values are missing their quotation marks, for whatever reason. It's always the same three values in all the presets.
"morphs": [
....
{
"uid": "Spacedog.Import_Reloaded_Lite.2:/Custom/Atom/Person/Morphs/female/Eyes_Reloaded-Lite/Eyebrows arc.vmi",
"name": "Eyebrows arc",
"value": -0.018
},
{
"uid": "Spacedog.Import_Reloaded_Lite.2:/Custom/Atom/Person/Morphs/female/Eyes_Reloaded-Lite/Eyebrows outer up.vmi",
"name": "Eyebrows outer up",
"value": -0.008
},
{
"uid": "Bodybuilder Details",
"name": "Bodybuilder Details",
"value": "0.3"
},
{
"uid": "Fitness Details",
"name": "Fitness Details",
"value": "0.69"
},
{
"uid": "Areola Size",
"name": "Areola Size",
"value": -0.44
},
I've never seen this before, and I corrected it before I ran the .var, so I can't tell you whether it causes problems, but I think you
REALLY want to fix those ASAP - most .json parsers I've used will distinguish between strings ("0.3") and floats (0.3), and many programming languages are "strongly typed", and can't process dictionaries with mixed-type entries. TL;DR - This might work if VaM's json-parseer were written in Python, but it's not. It probably won't cause a crash or anything, more likely the morph values are simply discarded.
Also, if you go into hand-editing .json files (.vap and most other presets in VaM are just "json in camouflage"), you might want to get a good texteditor with syntax-highlighting and a suitable language file or style preset for json syntax: My editor marked those missing quotes in a different color-scheme, so I noticed immediately. You could use notepad++, which is good, and has JSON as a setting under "languages". For big files VSCode is better, and there are a lot of extensions for .json. It's also a bit more complicated to set up.
3) Lastly, you use different creatorname and packagename in your meta.json than in the naming of the actual package - like the package listed with creator:
SuppleShrew and name:
Noa, while the meta.json lists:
"creatorName": "Brian",
"packageName": "Noa_Custom",
It won't cause anything to break, but I wouldn't do that - you're going to confuse the hell out of your users, and yourself.
