Destiny 2’s Armor 3.0 Rework Continues To Be A Broken Mess As Players Find A New Stats-Related Bug

Image: Bungie

Destiny 2 players have found yet another bug related to the major Armor 3.0 stat rework that went live with the Edge of Fate expansion.

When Destiny 2’s Edge of Fate expansion launched last month, Bungie introduced some of the biggest systemic changes the game has seen in years. We got the new Portal system, which lets you jump between activities faster. Gear was overhauled with a new tiering system. And one of the most hyped changes came with Armor 3.0, a complete rework of how your stats work, allowing them to scale all the way up to 200.

Bungie even promised that “every point in a stat will provide a benefit”, removing the old tier system that only improved abilities every 10 points. The idea was to give players more flexibility when creating builds, without being forced into exact stat combinations just to hit certain cooldown tiers.

Destiny 2's Armor 3.0 Rework Continues To Be A Broken Mess As New Stats Bug Breaks Bungie’s 'Every Stat Point Provides A Benefit' Promise
Image: Bungie

Shortly after release, players found that grenade and melee ability cooldowns weren’t lining up with Bungie’s own numbers, with ability regen being much lower than expected. Then came the mobility bug, where Titans and Warlocks were moving at speeds equivalent to 0 Mobility, and Hunters were slower than intended as well.

Now, the Armor 3.0 mess has gotten worse. Players have found yet another stat-related bug.

New Destiny 2 Bug Proves Stat Scaling Is Still Tiered

This latest bug was spotted by Boiler in the Destiny Science Discord and posted on Reddit by engineeeeer7 (the same player who previously ran extensive tests on earlier Armor 3.0 issues). According to their testing, class ability regeneration isn’t truly scaling with each stat point. Instead, it still works in the old “breakpoints” style where your cooldown only improves every 10 points, not per point as Bungie claimed.

As the Reddit post explains: “For class regen, every stat point does not matter. Class regen is still using tiers and only changes at multiples of 10. You can see it yourself. Have your class ability at any value ending in 0-4 and equip a +5 mod. Your class cooldown in the UI and in actual play doesn’t change. You can be at say 59, but getting to 60 instead changes it dramatically.”

Each point still appears to count when it comes to things like flat stat bonuses and regeneration effects from certain perks or mods, so depending on your build, those extra points might still help. “Now, every point does still matter for flat gain and regen effects, so it still may matter for your particular build,” the post reads.

The data comes with a graph and table showing this in effect. Check them out below.

Destiny 2's Armor 3.0 Rework Continues To Be A Broken Mess As New Stats Bug Breaks Bungie’s 'Every Stat Point Provides A Benefit' Promise
Image: Boiler

In short, if your class ability stat is at 41 or 49, you’re getting the exact same cooldown speed. That’s not what was promised when Bungie said Armor 3.0 would make every point valuable. In the “Next Gen Armor” blog article, Bungie said:

“Stats effects will no longer be tiered every 10 points. Every point in a stat will provide a benefit. This change is intended to reduce the “lock-in” effect that happens when a fine-tuned combination of stat values makes it feel impossible to switch out any single Armor piece.

“Stat effects will be capped at 200, with the range from 101-200 providing an additional powerful effect building on the base effect. This change is intended to support deeper investment in a smaller number of stats, and “spikier” stat distributions on armor with fewer secondary ‘dump stats.'”

Destiny 2's Armor 3.0 Rework Continues To Be A Broken Mess As New Stats Bug Breaks Bungie’s 'Every Stat Point Provides A Benefit' Promise
Image: Boiler

As of now, Bungie hasn’t commented on this newly found bug, but given how quickly they addressed the earlier Armor 3.0 and mobility issues, players are hoping this gets fixed soon.

What do you think? Let us know in the comments below!

Share This Article