League of Legends Glitch Disables All chat, players Rejoice.
League of Legends has become more chaotic than ever with the sudden appearance of an emoji-spawning, potentially dangerous glitch.
Players can use the Tweet of FNATIC streamer Elosanta to insert “%i:” in the match’s Chat to activate the glitch and disable chat. While some players feel stressed by the inability to communicate in ranked modes, while others enjoy the peace of virtual harassment, many find it refreshing.
Chat can be turned back on by players typing “%” in chat. Imagine that you are in the middle of a match of League of Legends, and things get heated. Your teammate makes an error and blames you. Chat is immediately disabled, even though your colleague makes a mistake and starts blaming you. It almost sounds like a divine blessing.
The League exploit allows players to access in-chat emoticons from a collection of image codes. This communication option has been neglected by Riot Games over the years, as they have opted to use Emote popups. In-game chat can be used to spam some emojis, including ranked emblems and icons for Champion Passive Abilities and lightning bolts. Riot hasn’t commented or patched the League bug, but it breaks so many user interfaces that it is safe to assume that a Hotfix will be incoming.
League of Legends can be as toxic as poison. It is a fun game with many memorable moments. However, it is difficult to play the game without being flaming in truly evil ways. Riot even acknowledged the horrible nature of in-game communication in October last year. They wrote, “While /allchat can be a source of social interaction between teams as well as some good-hearted chatter, right now the negative interactions outweigh any positives.” However, Riot appears to have given up on the idea of repairing All-Chat completely in League of Legends matches.
This chat glitch makes communication in League of Legends easier. It’s quite funny. It also allows players to add digital flair to their sentences using the emoji. Riot should not rush to fix this one, I hope.
