Sorry to be a downer, but ... this is still too unreliable for me to use as a standard plugin. Maybe it's due to the huge-ass scenes I prefer (Slamt, TGC etc), maybe it's bcs my machine is not quite fast enough & stuff gets lost during async loads bcs some anim starts playing while the triggers aren't finished populating - or maybe it's my presets? - or whatever ... but the end-result is that I've found there's a pretty decent chance that the Ninja will have "ninja'ed" ANY plugins on all person atoms after scene löad.
So I've reverted back to using the Browser-Assist plugin mergeloads & deleting any double-loaded plugins - a little more tedious, but a lot more reliable, IMO.
Sorry for the lack of detail - and normally, I'm more than happy to assist with bughunting (especially for a superb idea like this) but in this case, "testing" means sitting through loads of tedious scene-loads, waiting to see whether I've twiddled my thumbs for nothing.
Could you maybe add some kind of diagnostic? I'd be A LOT more inclined to take the risk of a broken scene-load if I knew it wasn't completely for *nothing* ...
I actually think I know what this is, I just haven't had time to check to see if my theory is correct.
Check the plugin's UI once - does it show the same value for the plugin preset as it does the appearance?
I *think* the setting value was getting crossed somewhere, and it was trying to merge the appearance with the plugin. I also *think* I've got a fix implemented for this, but just need to test before updating.
If I'm right, you should be able to disable the plugin, load a scene, select a plugin preset, then enable/reload the plugin to make it do the merge. With this process, I'd expect it to work fine on a scene that failed previously. LMK.