Launch Base Beta Test

[Marshall]

Index out of bounds

I'll look into this.


NPatch
I could replace the "RockPatch" labels with "Required Patch" and use a combination of version and name to distinguish patches. I think this would have too many problems though:
1. Mod authors would have to type in the patch name exactly as it appears.
2. If the author changes the patch name (VK) then it would no longer be valid.
3. I'd have to ignore certain mod file rules to make sure things like new mix files were allowed. I don't want to do this because who knows what files someone may decide to include in future, and these could potentially compromise safe usage.
4. Any patch can affect the way the game works - it could change filenames or create new files, all of which I would have to keep writing new code to handle them. At least I can rely on pd to keep me apprised of those kind of changes, and to discuss them with the community beforehand.
5. Authors would have to send me a security.lock file and wait for me to send them a security.key file. At the moment this is not required for RockPatch, so pd does not require involvement from me in order to release updates.

On the whole, I think only supporting RockPatch2 (maybe RockPatch1 too if the setup is the same) is the best way to go.


On another note, I'm thinking of adding a new flag for RP plugins so that pd can specify whether a new version is backwards-compatible or not. That way, a mod can say "I need version 2.3", and RP can say "this is version 2.5 but it is backwards-compatible to 2.0" so okay, or "this is version 2.5 and it is only backwards-compatible to 2.4" so it's not okay.