Archives by Day

About Rainier

PC gamer, WorthPlaying EIC, globe-trotting couch potato, patriot, '80s headbanger, movie watcher, music lover, foodie and man in black -- squirrel!


Rainbow Six 3: RavenShield - Update Patch Available NOW

by Rainier on June 17, 2003 @ 9:28 a.m. PDT

As expected Ubisoft has now released the new patch for their FPS/Stealth action game Rainbow Six 3: Raven Shield. This upgrade brings youer retail game to v1.3 and contains engine optimisations to prevent framerate drop during firefights. A new ban system allows hosts to ban cd-key instead of player IP. The patch comes in various flavors for UK as well as US versions ... Read more for details and download links ...

Get the Rainbow Six 3 v1.3 Patch Off Worthplaying (UK/US versions)

Get the German Raven Shield v1.3 patch off UbiSoft Germany

Get the French Raven Shield v1.3 patch off UbiSoft France


Patch 1.3 contains engine optimisations to prevent framerate drop during firefights. A new ban system allows hosts to ban cd-key instead of player IP.


  • Optimisation to prevent framerate drop during firefights. We now only spawn one of non-visible impacts out of 16. This reduces the number of decals and the
    number of particles/Wall effects. Also first person weapons are no longer affected by projectors.
  • Fixed map download, there's now a visual effect related to downloading the map. Map files are saves to a temporary folder and allow you to play immediately after downloading.
  • Server restrictions work now correctly for high capacity mags, demolition kit, electronic kit, lockpick kit, and gas mask.
  • To prevent people telling enemy position by changing their name, the name and setname functions only allow one change every 60 seconds.
  • Implemented a new ban system linked to CDKEY. When a host bans a player, the id number of the banned player appears the player banlist.ini. This player may no longer join the server anymore. To unban a player the host needs to delete the appropriate player number. To find out your id use the command myid in the console. This id number is also be listed in the ravenshield.ini file. Refer to the Other part of the document for more details about the system. banlist.ini is created when host player uses the ban command for the first time. The file is located on the servers machine in the system folder and can be edited
  • fixed a sound bug that makes the editor crash when you convert stereo sound to mono.
  • ASE is now officially supported by RVS.


Here is in details the way the new ban system works

New command:


A player banned from a server may appeal to a server administrator to become unbanned. To do so, the player will need to tell the administrator his id, which can be displayed by using the MyID command in the console. Alternatively the player may look up their id in ravenshiled.ini by searching for m_szGlobalID.

New admin commands:

To unban a player the server needs to manually edit the banlist.ini and remove the banned players id. You can also unban someone in the console by using the following commands: UnBan, BanList, NextBanList, and UnBanPos

  • UnBan #####
    • If you have the id of the player you want to unban, simply issue the unban command with the player's ID.
      Player ids consist of 32 characters, however you may only need to enter the id prefix assuming there is only one match.
      If there is more than one match you must enter the entire 32-character id.
  • BanList, Banlist #####
    • BanList displays the server's first 10 banned ids. If you add an id prefix it displays the first 10 matching banned ids.
      Each id in this list has a corresponding position, which is used with UnBanPos command.
  • NextBanList, NextBanList #####
    • NextBanList displays the next 10 matching ids using the same criteria as BanList.
      Using NextBanList without first using Unban or BanList causes an error.
  • UnBanPos #####
    • UnBanPos allows you to use the position index of a players id displayed using BanList or NextBanList.
      After using UnBanPos you must use BanList or NextBanList before trying this command again.
blog comments powered by Disqus