Riot’s ridiculous bug in the latest patch that made people laugh

League of Legends is an incredibly difficult game where it’s sometimes easy to see developers make mistakes by ignoring two unpopular champions or unexpected interactions involving elements not normally seen in games.

Considering that the number of items in the game is infinite, these are unavoidable situations. Usually the reaction of the public in this situation is a few jokes and a lot of fuss about it. However, Riot Games’ latest mistake was so obvious that players couldn’t figure it out.

A terrible bug in a new League of Legends patch

One of Riot Games’ goals was to scale down patch 12.8. Stopwatch . This component of Ionia’s hourglass or guardian angel has become very (too?) powerful in Summoner’s Rift, and as such the studio wanted to limit its offensive use.

Patch 12.8 introduced the following change: Empty pocket: You can no longer buy a stopwatch if you have a guardian angel or a jonya hourglass.

A good decision that deserves the approval of the public. The problem is that players have found a fairly obvious way around this change.

This is because a stopwatch can no longer be purchased once you have one of the items it uses in your inventory. However, by using it, you can still get your goods before you are done.

The only thing that has changed in this direction is the order in which we must exchange. If you have a “timer” in your inventory, you must buy a second one and then complete the item.. This completely disables the change. It is true that gold management can take a little longer, but when this strategy is used it is usually because the advantage is enough.

It’s unbelievable that Riot Games didn’t verify this issue before adding the fix to the item system. A good solution might be to avoid buying a stopwatch if you already have it in your inventory.. However, the creators of League of Legends seem to have neglected to “trick” the player, which in this case is pretty obvious.

The good news is that Riot Games seems to have figured out the issue and will likely fix it with a 12.9 patch coming in two weeks.