OCTGN

If you try to install a set with a higher version number than the one that’s currently installed, it will give you the “set is already installed” error message, and you have to delete the set first.

It would be a lot more logical to have the newer set file replace the older one in the database instead of giving that error message. I can see some issues with overwriting the set file with an “unofficial” update, so perhaps some sort of verification signature could also be implemented into set files to prevent this?