This is not cool.
I notice for the first time that BWP is not just distributing fixes, but also content modifications disguised as fixes. In particular, the most recent fixpack tweaks the way SCSII warriors use their special abilities. This is in no sense a fix; it's modification of my content presented to the player as if it was a fix.
This is seriously not cool. I have no objections to other people's mods changing content that I've written. I have no objection to people using my code or content in their own mods. I have a serious objection to people modifying my own mod, without the player even knowing this has happened.
In the light of this I am no longer happy with BWP distributing "fixes" to SCS or SCSII. I'll make an exception for genuinely critical fixes (like the distribution of scsii.ini in the most recent fixpack) and for the previously-agreed compatibility change to "skip candlekeep", and I'll make a blanket exception when I'm away from the modding scene (as happens for up to 6 months at a time). Other than that, though, please remove all SCS(II) modifications from the BWP fixpack.
EDIT:
Having wandered around more in the "Fixes for the BWP fixpack" it's reasonably clear to me that the fixpack more or less indiscriminately bundles and includes any hotfix distributed on any site for any mod. Since that means (for instance) that it's not even going to be able to distinguish between critical and non-critical fixes, here's a modified policy:
Please do not distribute any fixes for SCS(II) which are dated earlier than the most recent version (currently the beginning of December 2011)
(There is a specific exception for scs/addtoarea.baf.patch, which is a compatibility modification. You can leave that one in.)
Edited by DavidWallace, 06 January 2012 - 11:20 AM.