Rainbow Six Siege Dev Tracker

This is a very nice question, and a keen observation. It's no secret that our obsession since the beginning has been competition rather than making a realistic and immersive game. So the more the game evolved, the more we felt the need to explore gameplay areas that were no longer compatible with the "realism" and the original settings.

Also as game dev we wanted to make a game that talk about the stuff we love and what we love is esport :)

So that’s why we decided to move away from the classical terrorist hunt storytelling to the more "Competitive and Search for Perfection" story telling that also exist in special forces fantasy. This provides a setting that is closest to us, and also that is way more sustainable on the long run than the classical good vs evil classical story arc.

Think our story as a Season of NFL or NHL.

-Leroy, Creative Director

You're actually making a valid point here. Adding new content on top of existing content can be tricky.

To give an example: when we first shipped, we realized it was tricky adding new gadgets, because parts of the code were shared, and every time we added a new one we risked breaking existing ones. This was not scaling well - the more gadgets we added, the trickier this was becoming.

So this is why we created a gadget v2 framework, to isolate gadgets and make sure that new ones don't risk breaking existing ones. Today, I'm happy to report that over 90% of our gadgets have been migrated to the new framework, and of course all new ones are as well. ~ Paul, Technology Director

She has a very good secondary weapon and to be honest, for now, we are not looking to give her another primary. For us, if we do that, nobody will use her sniper anymore and that's a shame.

So we need to look at the sniper itself how to buff it. We still believe on a bolt action sniper rifle in Siege. We are aware that this is a very polarizing weapon, and that some are convinced otherwise, but this is still an option that we want available in the game.

We have no plan to share yet.

-Aurelie, Game Director

We've already touched on toxicity and reporting in other answers, but you've got some great thoughts on the Test Server! This is actually something we're in the process of working on and have some solid improvements coming quite soon - especially to matchmaking. Let's just say we're looking into all the things you mentioned here. Stay tuned, because we'll have more to share soon ;) ~ Mo, Business Strategy and Live Performance Director

Great question, and that representation is incredibly important to us as a team. This year, in fact, the team has taken great strides to really level up how we are authentically representing our Operators, for example with the partnership of Nakoda consultants for the creation of Thunderbird. This is an approach we'll be taking moving forward as well, to ensure the future LGBT operators we bring to the game feel like honest, real people. Please stay tuned, very shortly you may meet someone interesting joining the crew...

-Eric, Senior Community Developer

We have indeed added Gamelift to the roster. The idea behind is 3-fold and pushes to improve the overall server quality of service:

1. Improve our resiliency, offering a service backup in case of outage of our other providers
2. Mid-term we plan on putting Gamelift in the siege server pool more frequently in order to improve connectivity (some users might ping Gamelift better than our other providers, hence directing them to the best option available)
3. Having more providers enables us to improve the global coverage by allowing you to benefit from new regions that might be unique to some providers while not being available to others

~ Ben, Technical Director for Live Operations

It's true we haven’t added new guns for some time, because we have already a huge pool of weapons - we have 100+ weapons (23 Assault Rifles, 20 SMG, 18 shotguns for instance).

Because of Siege’s lethality system (a headshot guarantees the kill), rate of fire is the king parameter for all weapons. This makes all low rate of fire weapons sub-par, and reduces drastically the pool of weapons that are really played, only 30 of them are played most of the time. This reduces the diversity of the game experience.

The Loadout should guide the player in the playstyle and abilities of the operator.

- New weapon is created for new gameplay. Example with the CSRX 300 on Kali.

- New weapons can be created for lore / universe reasons. Zero with the SC3000k is a good example

Each year we bring a new weapon. Recently we have released the Gonne-6 to help for the 20 sec meta and a new one will be available soon.

We concentrated also some efforts on sigh...

It sometimes depends on your area of expertise but from personal experience I would recommend not being afraid of getting in the door through Game Testing or very Junior levels. The amount of knowledge you will gain by being close in proximity to experienced team members will pay dividends in your career growth. You can also try looking for Industry Meetups such as IGDA to get close to those with industry experience. There are many developers that attend these and are willing to have conversations with those looking to join the industry. It is all about getting out there and meeting others in the industry and putting into practice what you have learned from those conversations. Making games is a team sport and learning to play your position on the team is an asset to any team looking to deliver on products, content, and features.

-Christopher, Assoc. Game Director

Manual bans are not our long term strategy as it would not be scalable, but that doesn't mean that we don't do manual bans - they're still very valuable to the team. We are looking at more automated detections so they can be as fast as possible and able to scale as needed. This is why we're investing in data-based detections and sanctions while continuing to reinforce BattlEye detections. This also means improving the client complexity to increase the cheat support costs for cheat makers. It does not mean that we're not issuing manual sanctions - we are. We're simply looking at the future, where we see more value in ramping up our data models detections rather than relying primarily on manual operations. ~ Ben, Technical Director for Live Operations

Hey! This is a bug the team is aware of. Thanks for the post!

Hey kid_moe96 -- do you happen to have your ticket number?

Hello everyone!

We’ll be starting to do community surveys. These are aimed to be short for you to fill out (1-5 minutes), but should give us a snapshot of how you are all doing following bigger updates on Siege.

Thanks in advance for any insights you might share!

Survey link: https://www.surveymonkey.com/r/7VQNR5V

Hi u/D4NW0LF — the way in which certain players' accounts were compromised were not due to a hack on our 2FA system.

It was certain people taking advantage of the human-nature of our customer support team who has since had their processes more tightly guarded and updated as a result. Thus, this was corrected on a case-by-case basis when discovered with the respective proper account owners.

flair:ubiresponse

Hey SuperMaxxii,

Just as a follow up to this, we did have a further look into this case and can definitely verify that the ban should be issued.

To avoid disclosing your personal info and your account's history, customer support will once again reply to your ticket with a bit of additional info.

Check the store now :D

It's out now btw.

flair: ubi-response

This is just a part-way update on issues covered in the Top Issues blog. We have a much more extensive status report on a greater number of community topics coming in the near future.

It is still coming in this season.