Rainbow Six Seige issue with penalty or ban timer (banned permanently or unreasonable hours) is a visual bug, confirms Ubisoft

Rainbow Six Seige is a multiplayer FPS that was released in 2015, but still maintains a pretty decent community of players today.

However, lately, its players are facing some issues related to bans or penalties during matches.

According to reports, many Rainbow Six Seige players have been receiving ban notifications with an excessive or permanent timer without justification (1, 2, 3, 4, 5, 6, 7).

Reports indicate that the problem can occur randomly at any time. First, the game kick out affected players from the match, and they cannot reconnect to it.

Due to the above, the system automatically applies abandonment penalties to those players. But, the ban timer of these sanctions is not normal, standing out for being excessively high.

So, players are suffering penalties that originate from disconnections due to game server issues, and it is not their fault in most cases.

There’s also a bug where you can be kicked from the match randomly and cannot reconnect ends in a ranked and unranked Ban—- to be honest I kind of want compensation for this one happened to me more than once yesterday and friends.
Source

Admit idea why I get kicked out of game at the start of ban phase and cant join back ultimately being banned for hours from playing the game when it’s not even my fault for leaving in the first place?
Source

As you can see in the following reports, there are ban notices for almost 30 years, and even some that go up to 60 years.

The multiple complaints of the players finally reached the ears of the developers. The official Ubisoft Support account confirmed the bug, but revealed that it is only visual.

In other words, the ban notice is showing many more ban hours than it actually is.

On the other hand, the game’s official support account also confirmed the bug, and offered more light on the matter, explaining how to calculate the real remaining hours on the ban.

We are aware of players seeing extremely long sanction timers due to a UI display issue.

🛠 We are developing a fix and will have more info soon. Conversions from # of hours or days to minutes gives the accurate timing.

Ex. 120 hour/day sanction = 120 minutes = 2 hours.Source

Finally, the company is working on a fix for the issue, but there is no ETA for it yet. We will update this article when new related developments emerge, so stay tuned.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.