yeah, this is the approach / variation Ive used since the beginning, and posted in on the first discussion of tag etc.
I also use a slight variation of this for development of modules, where I have a local build of vcv.
as ‘debug mode’ in vcv, disables access to the online module library.
as for VCV making changes, a change request was created for vcv 2 years agp (?) for just adding a tag, and they decided not to do this (and its extremely simple to do). but as discussed at the time, theres really no motivation for them to do it , and they wont want to have references to external projects … so not going to happen.
I did raise a request, for a generic change to VCV basically to support multiple module lists, that could be useful in a variety of scenarios (including for the MM), but this appears to have fallen on deaf ears.
though in fairness, frankly, I dont see, a much (github) development on vcv these days, I think its seen as mature - which is fair enough.
given the lack of dev on the vcv side, and so felt it was unlikely this change would happen.
a month or so ago, I took a look at the vcv source code to see if I could implement something similar (within a new module) , and initially impressions were pretty favourable.
the idea was basically, Id the list used by module finder, and basically use this as a seed for finding the vcv modules.
so each MM release, you’d basically just ‘import’ the new MM module list, and off you go.
busy on other projects at the moment, but I will revert to this at some point, as Im pretty sure it’d work well 