Rainbow Six Siege Dev Tracker

Originally posted by UbiNoty

Hello.

We know that this is not the first time this request has been made, and we've shared before as well that a colorblind option is something we want to look into for the future. While we don't have any information to share with you all right now on this front, we're not unaware of the struggles you're facing and we most certainly want to make rainbow as comfortable and enjoyable for everyone as possible. I do also respect your persistence in championing your cause - so just want to reassure you and let you know that we hear you.

Originally posted by Der_Krasse_Jim

u/UbiNoty even commented somewhere else after first post but didnt respond here, very cool

Originally posted by Paz_Zombie

I always type "less than three"

Originally posted by totomantis

Well, the patch was released yesterday and IQ is still banned...

Originally posted by LazyLemon01

Nah they won’t ban us for that right? Like they know that means love

Originally posted by UbiNoty

Sorry about that, she was just getting her personal effects and getting signed out. She should be released and available right about now for both xb1 and ps4.

(restarting might help if she's still banned for you).

Originally posted by bulgarianseaman

I got the crap scared out of me the other day when I was playing. I haven't had any infractions before and I typed "Wow that Monty raped us" after the Monty on the other team solo killed 4/5 of our team if i remember correctly.

Is this a strike system? Do these messages get evaluated for "naughtiness"?

I'm quite invested in Siege so I'd really like to know how much trouble I'm in!!!

Originally posted by TooMuchRainbowSix

Consider client side metering of the amount of message that can be sent and limit the size of each message . Meaning, you can type only so much so fast before the client stops it. One message per two seconds etc.

Easy to implement . Could easily do it on server side as well by letting client think they are spamming but you just queue the messages and only pop off queue every second. If one person adds more than x, then you ignore them until it drops below x. This should all be done before hitting the server side filtering to avoid resource overload.

So, server gets a simple fifo queue segmented by player, set max message by limiting queue sizes, discard message over queue length, only pop every x seconds per queue , to meter message dumping. Run filters when popping messages to reduce server load. Easy.