Is this strip armor = 1000 dmg a confirmed thing?
I seem to remember that using megavore on a whole barriered team strips armor but left barrier intact (except for the selected target obviously).
I thought that stripping was counted as enemy stat reducing, not damage.
This is one of those things I really really really really really really really really really really wish was clarified in-game.
So many mechanics and specific effects can only be learned through trial and error or dredging through the forums.
Yeah, just like the freeze mechanic. That’s not intuitive.
I’d be fine if they left stuck with simple descriptions in the tool tips, but it should be explained better on the website’s Game Guide then.
No it wasn’t. Well it was but not in the sense that you’re thinking. I encountered it once, but it was given by a troop that granted a random status effect.
I vote we just make this the Reflect is broken thread.
Speaking of which…
Sacrificial Priest did it’s thing and killed an ally. My first troop had/has reflect and had Barrier but no damage was done to Sacrificial Priest.
Which is exactly what is supposed to happen according to the patch notes:
For allies… If no damage was done to my troop then my barrier shouldn’t of been removed. What caused the barrier to be removed? Damage…
Oops, from your description I somehow had the impression that the Sacrificial Priest belonged to you. Interesting. Theory:
If you have barrier and reflect, 1st instance of damage removes barrier. No damage received, no damage reflected. You lose you barrier but still have reflect
Would it be so wrong to keep this as is? I think it would be interesting to have a new counterplay to these armor-stripping weapons. Many great game mechanics started as glitches…
The only question I guess would be if it would make delving too difficult.
What about players who haven’t completed The Warrens yet? They could face a hard time completing the delve with the random status effects being granted. Also imagine if Raid boss can also get a random status effect and has reflect. A lot of people would then lose their hero by stripping the armour.
Like bless, you can counter reflect with a dispel hero class.
The only real problem is that the interaction may be unintuitive to players. I would take that in exchange for a new way to counter rope dart teams (assuming there aren’t any other unanticipated effects).
Move over Titan, it’s Sentinel’s time to shine!
This just happened to me in GW.
The confusing thing here stems from there being several different ways “lethal damage” is implemented in the code. That’s part of why implementing the same thing multiple different ways is taught as a bad thing in early chapters of programming books. It means every time the devs make something like Reflect, they have to comb over every troop, figure out how many unique ways to do lethal damage there are, then get distracted and go to the pub for a few hours and ship the game. Nobody’s going to quit so it doesn’t matter.
Is it really just a ‘counterplay’ when e.g. our Mythic Megavore gets completely disabled (or killed) in battle by a mere status effect?
Let’s not forget that, as time goes by and new troops are added, Reflect will be increasingly common, effectively making Destroy Armor troops/weapons a borderline useless gamble.
I see what is going on here, they are trying to nerf Mang-like weapon
I can’t imagine that Reflect was designed as a counter to destroy armor, to devour, or to the lethal damage that Assassin/Archer can do.
Whoa whoa whoa. Charm triggers Reflect, against the unit that cast the Charm spell. Not the charmed unit—that is, the one that actually did the damage. I understand why the devs wanted it to be this way (otherwise Charm does even more damage, and potentially removes even more barriers), but if you can tune the Reflect effect that finely, there is no excuse for it to trigger on any of the three conditions I just mentioned.
I’d guess there’s something in the coding for Charm where it simply selects a troop with 1+ adjacent enemies and does Special damage (not reduced by traits) to those adjacent troops based on the Attack of the selected troop, similarly to Queen Ysabelle or Faunessa (although those probably count as Spell damage? Faunesa’s at least).
As such, it wouldn’t be the enemy troops actually doing the damage, despite how we visualise it, but simply (Special) damage from a troop’s spell, which then does get reflected.
I’ve always thought it would be interesting if Charm damage actually was affected by traits (and status effects like Enrage) – e.g. Charming an enemy Webspinner would be awesome; Gorgotha would block most of the damage unless the Troop was Enraged, etc.
I actually also think ‘Charm a random enemy’ should be able to select an enemy troop with no adjacents and have no effect as a result; currently it will always select from troops with adjacent units in a X–XX or XX–X situation (and thus always have an effect).
Makes you wonder exactly how much Reflect was able to be tested before being released. Would be really awesome if interactions with existing effects were listed at release!
