DrJustice has made a preset system, but it doesn't hand polyphonic patches or subpatches.
IMHO managing patches AND presets shouldn't take the form of an objet in a patch the axoloti at a ROOT level should manage that. Let's imagine being able to load a preset from another patch directly without having to load the patch first and then the preset, or even using program change program/subprogram messages, that would make it really great , fast, effective and usable.
Otherwise it's going to remain tedious to use it if you're not a developper.
I'm a developper and I know a bit about C & C++ but I don't want to spend days, weeks to have a reliable preset system, I prefer resuming doing music and use another machine (or buy another one if necessary) to do the job. I can imagine consumer users frustration with it
It's great that people can write their own objects, but I think that this should be handled at the root level of the axoloti because it would help everyone to keep the axoloti organised and usable.
I have a 64Gb card and it could be filled with hundreds of patchs/presets but it's not
And I guessing that most of don't either, that's a pity this thing is so close to being a Nord Modular G3!
(I'm gonna have a look at your NRPNs object that could solve one of my problem)