Yeah I have that too, I've reported it to Ash.
Nothing crazy:
- 1 working/playing VAM (everything is in there)
- 1 clean VAM (only required vars to test new content, cleaned over time)
- HZMDemos which includes all the demo scenes for my content
- Acid's dev tools + forward log always loaded
From there after I pack a .var
- Full test of the asset/plugin in my working VAM. One test clean (manually use of content or plugin). One test with existing scenes or demos if there are some. Test of most critical features ( preset systems, save system, multi-dependencies interactions etc )
- Full test of the asset/plugin in my clean VAM. Same process.
I also tend to test a "download" process in the clean VAM without installing manually. I suspect the error reported above I had (the fixedupdate error) was due to you forgetting to mention a required dependency, which is fixed in the new one and tells you it's required.
I'd ensure that a content used in the plugin is always considered a hard dependency (not soft/sub-dep) to avoid that sort of stuff. Even with the background I have with VAM, I did not realize I was missing a sub-dependency. So imagine a noob : )
Btw, critical errors "you're missing this, it's mandatory to have it"... use
SuperController.singleton.Alert if the user is in edit mode. It is critical, the plugin will not work... so it's not really a problem to popup a big window instead of a short log that disappears before you could even read the full message.