News

The Division 2 Title Update 3.1 fixes a lot of known issues such as the armor exploit

Exploits are never easy to deal with, especially in a game of this caliber. It’s complexity surely speaks for itself, as the developers behind Massive Entertainment and Ubisoft were needed a lot of time to salvage whatever was lost in the original title. Therefore, the approach to updates is a lot more robust and fair to agree that it has been just on point. As such, this Title Update 3.1 fixes a lot of known issues.

We’ll be looking at some of them below, but it is more important to take notice about the so far released content too. Not everything shines in every video game, and since the disappointment in the original series, this may be a nice way to redemption.

Previously noted as preliminary patch notes, all of the patch notes assigned for Title Update 3.1 were exposed. But, we will be comparing their integrity to the official ones released from today, and check if everything is missing.

After this update, the bug count should be brought to a minimum, and the gameplay experience enhanced by quite a lot. Below you may find the official Title Update 3 patch notes.

  • Increased tutorial font size on the Mega Map.
  • Increased visibility on Collectibles and Caches in the Open World.
  • Fixed an issue where the “Loot” tutorial at the beginning of the game wouldn’t appear.
  • Fixed an issue where the Field Proficiency toast would not include the gained rewards.
  • Fixed an issue where players could remain stuck in the Theater settlement after recruiting Inaya al-Khaliq.
  • Fixed an issue that could cause players to get stuck on the roof of the Grand Washington Hotel mission.
  • Fixed an issue where Hunter Mask and Ivory Keys would not drop, even if the player correctly solved the riddle and killed the Hunter(s).
  • This fix should allow players to re-do the Hunters and collect the Masks and Keys they are currently missing.
  • Fixed an issue where the rate of fire on semi-automatic weapons would be lower than intended.
  • Fixed an issue where face masks would appear smaller than intended.
  • Fixed an issue where opening a Dark Hours Apparel Cache could cause a continuous loop.
  • Fixed an error that removed the Loot All as Junk option. Sorry about that!
  • Fixed an issue where enemy NPCs would rush past players to get into cover.
  • Fixed an issue where enemy NPCs would flank players too often.
  • Fixed an issue where enemy NPCs would not react to any combat until reaching cover or having their movement interrupted.
  • Fixed an exploit where armor would scale to unintended values when normalized.

According to recent sources, all of the players who were abusing the known exploit haven’t been banned yet. However, they were warned about future actions. This reminds us of The Division, which initial ban wave kept users out of the game for just 14 days instead of being banned permanently.

Will Ubisoft watch through their palm once again and let everyone who abused the content to retaliate himself? Nevertheless, the community is a bit frustrated, as there are thousands of players in the game who have never thought of doing the exploit, while others still do that on a daily basis. Well, be cautious, as you may be the next target on the ban wave.

The small amount of players who have used the armor exploit will receive a warning on their account. Any further violation of the terms of use will lead to a permanent ban on their account.

Tags

Angel Kicevski

Angel started playing video games a long time ago. He started playing competitively since the Counter-Strike 1.3 era. Apart from that, the desire to own a website has always been there. Now, when the mission is slowly accomplishing, he's striving for success and nothing else. Besides that, he quit his full-time job to work on futuregamereleases.com. Being a father of two beautiful babies puts babysitting, gaming, and making poetry out of it a definite challenge. P.S. I play games the way they are meant to be played.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button
Close
Close