Reflect Damage should be taken out of game.

"

Ydoum wrote:

They should also remove curses from map mods. Or ailment avoidance. Or ele equilibrium.

Look, it's annoying, I get it. But that's what it's supposed to be. My build has no space to run curse removal flask, so I roll past dangerous curses.

Your build cannot deal with reflect - re-roll.

You seem to have forgotten that there used to be times when, even with no "reflect" mod on a map, there were magic and rare mobs with reflect affix on them.

"

whengreg wrote:

Then they removed those affixes. And that was the right decision. I'll also note that reflect is banned from appearing on Vaal side areas in maps. This was also the right decision.

If you ran a map with a dangerous curse, would you instantly die by attacking a normal enemy, or would it just make the map more dangerous?

If you ran an unidentified map with a dangerous curse, would you be able to notice before you started combat, or would the first clue come when you exploded? (And don't tell me not to run un-ided maps; there's a literal challenge for running these. This is a part of the game.)

I'm aware that "rolling past dangerous mods" is a good strategy to follow. Reflect is a unique map mod, because of the number of builds it affects, the impossibility of actually running the map anyway, and the instant death that it causes.

"

Ydoum wrote:

This guy above me, he keeps replying to every post I make with random stuff like this.

Please ignore him, his input is baffling to say the least. Clearly has issues understanding what is written, or is just on some weird personal vendetta.

"

whengreg wrote:

Then they removed those affixes. And that was the right decision. I'll also note that reflect is banned from appearing on Vaal side areas in maps. This was also the right decision.

If you ran a map with a dangerous curse, would you instantly die by attacking a normal enemy, or would it just make the map more dangerous?

If you ran an unidentified map with a dangerous curse, would you be able to notice before you started combat, or would the first clue come when you exploded? (And don't tell me not to run un-ided maps; there's a literal challenge for running these. This is a part of the game.)

I'm aware that "rolling past dangerous mods" is a good strategy to follow. Reflect is a unique map mod, because of the number of builds it affects, the impossibility of actually running the map anyway, and the instant death that it causes.

It is true, and that's why I have been mostly sticking to playing builds that completely ignore reflect (chaos, poison, pets [totems/minions] or this time around a duelist slayer ascendancy).

I also assume that by reflect mods you cannot deal with you mean corrupted, unidentified maps. I do agree that there should be some sort of a hint that you rolled a reflect mod on those, to counter it... even if it means leaving it instantly.

If I remember correctly, there was a statement made years ago during beta where they said that the game is supposed to be punishing, despite how frustrating it can get.

"

SuperMotte wrote:

"

yamface wrote:

"

Shioks wrote:

(2 rings remove reflect)

You should never be stacking reduced reflect stats because they're useless. All it takes is 1 increased damage taken debuff and you're dead.

If you can't mitigate 1% of your own damage than you are a glasscannon that deserve to get smashed for running such a stupid build.

Edit:
1% of 16% of your damage or whatever is the current reflect value