wolf_update_133.exe —
This patch includes many improvements/updates since the release of the previous 1.32 patch. Once you upgrade to this patch, you WILL NOT be able to play on servers with the 1.32 patch installed.
Also, this patch DOES NOT change the protocol version from the previous map. Please see the readme file for more specific information.
INSTALLATION & SET UP ISSUES 1. The update won't install: ============================ You must have a full retail version of Return to Castle Wolfenstein installed properly on your system before you will be able to install the update. -------------------------------------------------------------------------------- 2. Issues with uninstalling then reinstalling RtCW: =================================================== After applying the 1.33 patch you will not be able to use the automatic uninstaller to completely remove the game from your system. In order to successfully remove the game you will need to run the included uninstaller and manually delete the game folder from your hard drive. After you’ve run the uninstaller located in the Return to Castle Wolfenstein group on your Start Menu, follow these steps to delete the folder. These instructions assume the game is installed in the default directory. 1) Open My Computer. 2) Go to the C: Files folder on your hard drive. 3) Locate the Return to Castle Wolfenstein folder. 4) Highlight it and click File, then Delete. -------------------------------------------------------------------------------- 3. Issues with installing the patch to the wrong folder: ======================================================== When installing the 1.33 update, it is possible for you to browse and install to an incorrect folder. It is important that you only install the patch to where you have previously installed Return to Castle Wolfenstein. If this is not done, you will need to uninstall Return to Castle Wolfenstein before you will be able to install the patch again. -------------------------------------------------------------------------------- WHAT WE'VE FIXED 1.>Fixes added in 1.33 ============================ Medic Revival Sticking: Some players found that medics were sticking to people they revived. This issue was introduced in the 1.32 update as a bi-product of the new moving objects. -------------------------------------------------------------------------------- 2.>New features added in 1.33 ============================ Improved PunkBuster WebTool: Improved PunkBuster WebTool support, added additional features for the PunkBuster WebTool for server admins. Improved WebTool support Additional support added for people using the PunkBuster Web tool. See below for more information on the WebTool. Added g_axismaxlives and g_alliedmaxlives These settings were requested by server administrators looking to adjust the gameplay balance on their servers. These settings supercede g_maxlives when set. Servers can now set maxlives independently for each team. Important note for server administrators: before these settings will work, you must launch the game with a setting for maxlives. Added g_fastres 1 (Defaults to 0) This was another requested change. With g_fastres set to 1, players will instantly get up and is instantly mobile after being revived by a medic. However, the player is only invulnerable for a second vs. 3 seconds the standard way .. Added g_enforcemaxlives 1 (defaults to 1) When a player enters a game with maxlives set, their IP gets added to a list. Any IP on the list is banned from connecting until the next round starts. This is to prevent people from disconnecting and reconnecting to get by the maxlives limitation. Important note: this setting is on by default when "maxlives" is on. Since it is tracking by IP address, people who are sharing an IP (as in from a computer lab or dorm) won't be able to join the same servers.
There are no comments yet. Be the first!