In The Division 2, many are currently farming low-level mods. But why should you collect low-level gear? This is the reason.
What are gear mods? These are items that can be applied to armor pieces. They have various values such as additional weapon damage or simply armor.
Mods are a great way to optimize builds and enhance values to the maximum.
Which mods are we talking about? Some players are now focusing their search for gear mods on blue and purple mods from the low-level range. But why? It relates to their values.
Blue and purple mods can be quite useful
This is why it’s worth farming low-level mods right now: Even in the level range of 15+, some players are currently farming blue and purple mods.
Many have even created a second character for this purpose. Because the mods can offer values like specific weapon damage of 5% or more.
This even surpasses the mods in the high-level range, which usually only have 1-4%.
With multiple low-level mods, you can significantly increase the weapon damage for the desired weapon, provided you have the right mod slots for it.
This has also been reported by several players in the Subreddit of The Division 2, where this screenshot was posted:
How can I transfer the mods to my high-level character? Just store them in your inventory, you can then retrieve and equip them with the other character.
Will Massive change this? The developer is now aware of the situation and is listening to fan feedback on it. They announced this in the State of the Game on April 10.
It may be fixed in the next update. However, when that will come is unknown.
This video shows how you can achieve up to +40% weapon damage with the mods:
What do players say about this? In the Reddit post, the reactions are rather negative. Many find it annoying that you need a low-level character to get the mods with the highest damage bonuses.
Actually, these numbers should only be possible at the maximum level of 30. However, most are optimistic that this will change soon, as Massive has already responded.
This problem should also be fixed with the next update:
