[outdated] Do not change flag of Disable outdated addons when APIVersion raise

[Rhyono]

The author being able to choose would be nice. Normally, CS catches fire on a new API update, so I'd like to disable it (until I upload the new one), but this patch for example, it would've still worked.

Would we assume if the setting is left off that it should be disabled or enabled? The addons that likely suffer from this the most are discontinued where the author won't be changing the flag.

[sirinsidiator]

Originally Posted by Rhyono The author being able to choose would be nice. Normally, CS catches fire on a new API update, so I'd like to disable it (until I upload the new one), but this patch for example, it would've still worked. Would we assume if the setting is left off that it should be disabled or enabled? The addons that likely suffer from this the most are discontinued where the author won't be changing the flag.

Hm. That would be a separate feature altogether and a reverse of the APIVersion directive. A "MaxAPIVersion" so to speak which forces the addon to disable once an update comes around. Sounds nice and useful when you know that the next patch will break the addon.