Riot Games has temporarily disabled the support champion “Bard” in all modes in League of Legends. “The wandering protector” could crash the entire game when interacting with the abilities of other champions. Riot Games took drastic measures and disabled the champ in all modes worldwide.
This is what Riot Games has done: The developers at Riot Games have disabled the support champion “Bard” in all game modes. Bard is not playable in ranked or in the popular mode “ARAM”.
As an explanation, it is stated that there are “in-game issues”. The deactivation occurred on Friday, April 22.
At the time the champion was disabled, it was unclear what the exact problem was. Riot remained silent on the matter.
Mobility can crash the game
Why was he disabled? A YouTube video explains the problem:
- There apparently are issues when Bard’s ability E interacts with a structure activated by abilities like Anivia’s W or Trundle’s E.
- If Bard exits a structure created by Anivia or Trundle with his E, it crashes the game for all players. It freezes and then gets dropped.
- The error clearly does not occur all the time, but in enough cases to justify disabling Bard.
Basically, one could deliberately end a game by crashing it if the match’s progress was not going as planned. YouTuber Vandiril calls the problem “literally game-breaking”:
What comes next? Riot Games says they will bring Bard back into the game once they have found a solution for the game-breaking bug.
At the moment, there is still no schedule for when Bard will be playable again in LoL.
Does this happen often? With nearly 160 champs interacting with each other, issues with the champs occur repeatedly. Recently, we reported on MeinMMO about a bug with the champion Rek’Sai, who could take players down to 1 health point with a single hit. This error also originated from a mobility ability:
LoL: Players demand that Riot immediately disables a champ because he destroys the game
