Rainbow Six Siege update: PS4 and Xbox One cheaters banned permanently in new fix

UBISOFT have announced that players caught cheating in Rainbow Six Siege will now be banned permanently.

 

A number of major changes have been made to Rainbow Six Siege

 

First-time cheaters were previously given just a three-day ban, but Ubisoft have decided to clamp down following complaints from Siege players.

A number of other tweaks have been implemented on the Xbox One, PlayStation 4 and PC including a fix which stops Defenders from leaving their zone during the preparation phase.

Those who stray will now be automatically killed, with Ubisoft also confirming that the server tick rate for console users has been updated from 30 times per second to 60.

As reported by News News Blog Gaming, Patch 1.2 went live on consoles yesterday, a full week after it came out for the PC.

Another update, 1.3, will be available for consoles on January 20, with major patch 2.0 available from February 2.

Here is a full breakdown of the changes on Rainbow Six Siege:

 

Players who cheat will now be banned for good

 

General Tweaks and Improvements (Live for PC and consoles, as of Jan. 13th)

Hit Registration Improvements:

- Updated the server tick rate for console users

Anti-Cheating Improvements:

- Cheating countermeasures have been improved further

- Banning policy update: all cheaters detected by the system will be banned permanently

Exploit Fix: Defenders Exiting The Preparation Phase:

- Added a configuration that allows us to turn ON an insta-kill configuration for Defenders that go outside their zone during the preparation phase

 

A major new update will go live in early February

Top Community-Raised Bug Fixes (Live for PC on Jan 13th, live for consoles on Jan. 20th)

Level Design Fixes:

- Fixed a bug that allowed players to exit their zone during the preparation phase (red wall)

Online Fixes:

- Partial fix of Error [2-0x00000041]

- Potential full fix of the loading screen freeze (smoke background)

- Potential full fix of the failed data synchronisation issue