I’ve experimented with custom-persist a little, and I think it should completely replace the current template persistence for named disposables like this:
- Add an option for custom-persist to have files reset on boot, like current template architecture already does.
- Make an option for named disposables straight from templates.
There. If you want a named disposable with customization, use custom-persist. If you want an empty disposable, then just base it on a template. If you want the dispXXXX disposables, then you have the usual way.
This is meant to be a suggestion, just phrased this way because I’m trying to template out a system, and I wish it were simpler instead of having to manage ten different dvm-templates for ten different nameed disposables simply because they have different templates. Feels like wasted space, even moreso for the ones that need customization. Take this with a grain of salt.