Raid Shadow Legends Block Damage is a skill that allows a champion to prevent themselves or allies from receiving any damage inflicted by the enemy. This skill is commonly found on HP and Defense Champions to aid the survivability in battle. However, Block Damage Skill can be countered with Ignore Block Damage skill or Remove Buff skill or Steal Buff skill. If a champion has both Shield and Block Damage buff, Block Damage only prevents damage from reducing from HP only.
Makes the Champion immune to all forms of damage.
Block Damage FAQ
Here is a list of frequently asked questions on Block Damage buff in Raid Shadow Legends.
How to counter Block Damage Buff champions?
There are a few ways to counter champions with Block Damage Buff. The first method is to apply Block Buff on the champion before he casts Block Damage buff on himself. The second method is to apply crowd control debuff (Freeze, Stun, Provoke, Sleep, Fear, True Fear) to prevent them from applying Block Damage buff. The third method is to steal or remove buff from the Block Damage champion. Last but not least, you can use champions who ignores Block Damage buff such as Mortu-Macaab.
Can Block Damage Buff be extended?
Block Damage buff cannot be extended as it will be too overpowered. In 2019, there was a player who created an Unkillable Clan Boss team using Valerie and Roshcard the Tower. Roshcard the Tower is used to apply Block Damage buff, while Valerie increases the buff duration of Block Damage. This prevents Clan Boss from killing the team and enables the player to deal sufficient damage in 1 Clan Boss key for all Clan Boss difficulty to reap the best chest reward. When Plarium found out many players were using this Unkillable strategy in Raid Shadow Legends, they added a new game mechanic to prevent these Block Damage, Unkillable and Revive on Death buff from being extended. Also, they added an ability to Clan Boss to Block Revive champions and deal damage that ignores Block Damage and Unkillable buff after 50 Turns of Clan Boss, in case players found a way to bypass it with other workarounds.