Thursday, 16 August, 2018

Tom Clancy's: The Division's Falcon Lost Exploit Will Lead To Bans: Ubisoft

Kristopher Love | 22 April, 2016, 05:35

The Division isn't one of those games; you need a UPlay account and access to Ubisoft's servers before you can look at your character's gear, much less play through a mission with friends and family.

Ubisoft and Massive may have patched out the exploit in "The Division's" first Incursion, Falcon Lost, but another has already taken its place. However, a glitch has been found where players can repeatedly run the mission many times - therefore farm some high-level reward items - by buying and using a riot shield and plunging headlong into an "almost invisible" wall.

In Tom Clancy's The Division, there's a war on the streets.

"Obviously it is against our Code of Conduct", community manager Natchai wrote on the game's official forum. While a lifetime ban may seem severe, some Division players are adamant that the punishment should be more heavy-handed.

Foremost among these changes was the addition of end game content. Ubisoft delivered this in the form of what it calls Incursions. The incursion was created to provide this loot just once a week, requiring players to come back again and again over time to gain the full set of randomly doled out gear. Ubisoft, they say, shouldn't punish those dedicated (but temporarily outclassed) players.

YouTube channel Simplified has explained the exploit in a video embedded below.

Once that's complete, all the player has to do is use the skill, pause, go to the inventory, and then quickly start switching between the primary and spare weapons for about a minute. Most notably, the publisher is trying to find out if players would like to see The Division branch out to include new cities other than just NY with possible upcoming expansions.

"But now I'm reading that you consider your faulty code to be on USA, as players?". It's not as if these fans manipulated the game with their own malicious code, after all. The game could've easily used, and probably should've had, an extensive beta test that lasted months, and not a flimsy open beta over a weekend.