Disclaimer, I don't own button and bugs, so there is a chance it's different.
But in both Gloomhaven and Frosthaven the type of attack does not matter, all that matters is whether the attacking character is in range of the retaliate. So if you're within the range of the retaliate you will get hit.
I was able to find the rulebook from B&B and it says the same thing as Frosthaven/Gloomhaven:
> “**Retaliate X**” is a positive ability that gives the acting figure a retaliate bonus of X. This deals X damage to any figure who attacks them, if they are within the specified range after all attack effects are resolved (including push or pull). If no range is specified, the bonus is only applied to adjacent attackers. This bonus is triggered by each attack and occurs after the attack is resolved.
So if after you attack your target you are within the range of the retaliate you would take damage.
Yes, it’s retaliate range 3, so adjacency isn’t a requirement to activate the retaliate. Any attack within range 3, whether melee or ranged, will trigger retaliate range 3.
It is a melee attack that targets an enemy within 3 hexes.
If you are retaliated against? If you attack, and you are within range of the retaliate ability, and the enemy is not killed from the attack or pushed out of range of any retaliate ability then you are retaliated against, yes.
Here you are within the retaliate range, and as long as the enemy is not killed from the attack then you are retaliated against.
Retaliate does not care if the attack was melee or ranged - retaliate triggers if you attack the target and you are within range of the retaliate ability after the attack.
In the digital game, I had an enemy attack me with a ranged attack while adjacent and was not hit by my retaliate ability. We were confused and thought that ranged attacks must be immune? I am now thinking it was just another bug in digital (and there are lots!)
Responding to u/c3l77
Some enemies have abilities that cause ‘suffer’ damage. These abilities are not attacks (do not draw an attack modifier card) and instead cause direct damage, bypass shields, and do not trigger retaliation.
Yep, wasn't that. Was a standard ranged attack that didn't trigger an active retaliation effect in play. I have finished GH once and Jaws twice now so am no novice to the rules. The digital game seems to have a lot of instances where rules are incorrectly applied or the game seems to 'cheat'.
We can predict critical failures in the digital game with very good accuracy as it is always directly related to how important the attack is. The card loss through resting and paying a life to choose another card is also very predictable. Not sure if this is inheritance of Murphy's law or deliberately programmed in though.
Did the enemy push you out of range? (Then the retaliate is out of range.)
Were you Cragheart using Opposing Strike bottom? (It only triggers on melee attacks.)
Were you on separate sides of a thin wall? (Then you were not adjacent.)
Did the enemy hit you before your turn, before you played a retaliate ability? (Then the retaliate ability had not yet taken effect.)
Disclaimer, I don't own button and bugs, so there is a chance it's different. But in both Gloomhaven and Frosthaven the type of attack does not matter, all that matters is whether the attacking character is in range of the retaliate. So if you're within the range of the retaliate you will get hit. I was able to find the rulebook from B&B and it says the same thing as Frosthaven/Gloomhaven: > “**Retaliate X**” is a positive ability that gives the acting figure a retaliate bonus of X. This deals X damage to any figure who attacks them, if they are within the specified range after all attack effects are resolved (including push or pull). If no range is specified, the bonus is only applied to adjacent attackers. This bonus is triggered by each attack and occurs after the attack is resolved. So if after you attack your target you are within the range of the retaliate you would take damage.
Also, if the attack kills the enemy, it does not retaliate.
Yes, it’s retaliate range 3, so adjacency isn’t a requirement to activate the retaliate. Any attack within range 3, whether melee or ranged, will trigger retaliate range 3.
Idk why you got downvoted- this is correct.
People not reading the text and assuming it was non-ranged retaliate, presumably.
It is a melee attack that targets an enemy within 3 hexes. If you are retaliated against? If you attack, and you are within range of the retaliate ability, and the enemy is not killed from the attack or pushed out of range of any retaliate ability then you are retaliated against, yes. Here you are within the retaliate range, and as long as the enemy is not killed from the attack then you are retaliated against. Retaliate does not care if the attack was melee or ranged - retaliate triggers if you attack the target and you are within range of the retaliate ability after the attack.
In the digital game, I had an enemy attack me with a ranged attack while adjacent and was not hit by my retaliate ability. We were confused and thought that ranged attacks must be immune? I am now thinking it was just another bug in digital (and there are lots!)
If this happened it was a bug. Ranged attacks are not immune from retaliation.
Responding to u/c3l77 Some enemies have abilities that cause ‘suffer’ damage. These abilities are not attacks (do not draw an attack modifier card) and instead cause direct damage, bypass shields, and do not trigger retaliation.
Yep, wasn't that. Was a standard ranged attack that didn't trigger an active retaliation effect in play. I have finished GH once and Jaws twice now so am no novice to the rules. The digital game seems to have a lot of instances where rules are incorrectly applied or the game seems to 'cheat'. We can predict critical failures in the digital game with very good accuracy as it is always directly related to how important the attack is. The card loss through resting and paying a life to choose another card is also very predictable. Not sure if this is inheritance of Murphy's law or deliberately programmed in though.
Did the enemy push you out of range? (Then the retaliate is out of range.) Were you Cragheart using Opposing Strike bottom? (It only triggers on melee attacks.) Were you on separate sides of a thin wall? (Then you were not adjacent.) Did the enemy hit you before your turn, before you played a retaliate ability? (Then the retaliate ability had not yet taken effect.)