One month after the public XR 1.0 release and more than two months after the initial pre-release, the testing period for Savage XR 1.0 is over. We would like to thank our testers and players so much for their patience and support!
As time progresses, the moment to sever the ties with the past closes in. At this point, under 5%
of all the Savage clients being used are not XR 1.0. Although there are unfortunate exceptions like honest players believing their computers are too old to run anything other than outdated versions, there are those whose choice is not so benign. Many if not most that still use them do so because of the client cheats and hacks only working on those. The countermeasures we could implement in the servers, we did, but there's nothing we can do to prevent those unfair advantages on age-old installs with no auto-updater and crafty cheaters.
Besides the new anti-cheat protection in XR, there are new features which are incompatible with old versions: the new auth server, the new clan commands like inviting, voting and playing mods 'on the fly', the new XR maps with all their props. In fact, the xr_ maps triggered a new kind of exploit: the XR 1.0 props and textures are invisible on older clients even though they CAN play them. The players using them can actually see through
them like there was nothing there. It's time we cast them out.
Further development is also hindered by having to maintain retro-compatibility. You have to be a Savage dev to know how many times we felt suicide urges because of the amount of work needed to add the smallest of things without breaking backwards compatibility. As yesterday's patches showed, the updates to the Testing installs, both client and server, which many of you still use, can cause quite some issues.
So, in order to remove the cheaters once and for all and to clear the way for the development of XR 1.1, everyone should switch to public release Savage XR 1.0 Production
version, which will only get major updates, and not untested and frequent dev patches. Please read the following instructions carefully:
To find out exactly which version you have, run Savage, pull down console with the tilde key ("~"), type cl_SEPVersion
and press Enter. The number you get shows your version:1005: YOU ARE OK
. You have the public release Savage XR 1.0 Production, you need not do anything, except make sure you always start the game with savage.exe and not silverback.exe.1006:
You were an XR 1.0 tester, and still use a Savage XR 1.0 Testing install, used by developers to test new changes through frequent updates that may happen to break it. You can either reinstall the game from the download page
or edit 2 files to keep using your current install. To do the latter, find your Savage XR installation folder and edit the "a-u.cfg" file located inside. Just change the value of the "isTesting 1" keyword to "isTesting 0" and your install will become Production. Start Savage, let it update and play. 820-1004:
If cl_SEPVersion resulted in anything lower than 1005 or 1006 (like 1003, 1000, 999, 820 etc.) means you have an outdated and unsupported version
. You need to reinstall the game by downloading your appropriate client from the download page
As soon the final preparations are in place, a patch will be uploaded for all servers, clients and OS's installs. That will most likely be tomorrow evening. Among other dev changes, it will break compatibility with outdated clients so please make sure you take care of it by then. Thank you.