On another note, I'm thinking of a new feature for the downloads system which is "file locking".
One of the issues with RTB's moderation system is that if someone submits a broken update for a file it will be instantly distributed to all the users after it's been approved. Mod Reviewers don't actually ensure the add-on works before approving them - downloading each file and trying it in-game would be way too time consuming for all the files getting submitted to us.
File locking would enable us to totally disable the add-on for all RTB users as well as prevent it from being downloaded until the author has fixed the file. Once it was fixed it could be used in-game and downloaded again.
Well I don't know about disabling the addon completely, it brings up horrible images of Amazon and Apple deleting stuff off of people's kindles and ipods. I don't mind being warned about a mod and even having it automatically turned off, but having a mod specifically prevent me from running another mod just doesn't sit well with me.
I think that locking down a file should disable downloading and then prompt a warning message in the game when you start up that says something like
"This add-on has been locked down for the following reason:
sets motd to admin password
RTB has automatically disabled it for your convenience. If you would like to run the mod at your own risk, please enable it in the mod manager."
If it was v2 that broke everything and v1 ran fine and you hadn't updated yet, the game should also just stop it from updating and let you keep running it.
If you save it for extreme cases where addons seriously break the game I think most people will follow it, especially if the reason it's being disabled sounds really scary. There's going to be people who try to get around it anyway by renaming the file or trying to comment the code out of RTB. Normal people might not ever use the option but they'll be happier that it's there and appreciate that you're giving them the choice.
Edited for clarity.
