Originally Posted by
Andraax
So, you want to push the responsibility of not updating CoreRPG (a supported ruleset) until GURPS (an unsupported ruleset) gets updated onto SmiteWorks? That's not going to happen. If you use something unsupported, it's on *you* to make sure they work together. SmiteWorks makes sure that all *supported* rulesets gets updates so they work simultaneously - that's all they should be required to do. SmiteWorks already announces, and makes available, the updates well before they push them, so developers have plenty of time to test / update before the push happens. If developers do not take advantage of that, it's not SmiteWorks fault...
If you are using an unsupported ruleset that relies on CoreRPG, your choices are to maintain older versions of CoreRPG that work with the ruleset yourself, or not update until GURPS works with the latest CoreRPG.
Of course, if GURPS *becomes* a supported ruleset, this argument goes away for GURPS.