As more authors release macros, we need a way to mark a macro disabled. There is no point deleting a macro when a mod will juts reload it. A disabled macro will still show in /gs but in a seperate list. It wont auto create the

As the macro are updating always and with a lot of different authors and type of macro i think it will be easier to manage with this things

1 - version incremental value
if any macro can have an incremental number each time is modified and loaded into the addon, you can solve it in this way :
all should start as version=000001 and each time a macro is edited the [version] value should be incremented by one and you can then upload into the addons folder in the correct order and make the GS-E load only the latest version of each macro ( same macro name but different version)
that can keep the active macros limited to the latest valid one and marke them, but not deleting, the older ones.
to do the job of incrementing version i thing a simple script to add+1 to [version] value shoud be enought to be runned only by you as the mmacros are validated and uploaded into your addon.

2 - data check on macro files
you can tell the addon to check the creation or modification date details for the concerned lua files with the macri written inside and make it load only the lastest [1/2/3] ones for each class/spec.
to do that the haddon should be able to check luas files details and take only the latest one ( and maybe mark as OLD a macro not updated since 6 months)

3 - auto update feature.
compile the addon to let him on auto empty the whole macros sets on each update you made and redownload the latest macro sets validated from you/authors.
this will give you the downside to check every macro and also if someone have modified a macro you will delete it and maybe change the macro setup to all the others that didn't know that each time you update the macr sets the macro work in a different way ( then maybe have to recheck talents and way to playing)

A lot of this is covered in 1.3. There is both a source, version value and an authorversion. Source is the name of the mod it came from while authorversion is version of that mod. Version is a unique internal value but will be different on each client.