League of Legends is no stranger to bugs, both big and small, and these glitches tend to surface especially with the release of new updates or champions. Recently, following the 14.14 update, the community discovered an amusing yet problematic bug.

For reasons not entirely understood, champions utilizing abilities like Ekko, Illao, and certain aspects of Rengar while targeting enemy structures such as Inhibitors or the Nexus, fail to execute their leap. Instead, these champions appear to attack from an extended range, resembling ranged champions.

This bug was thoroughly investigated and confirmed by Vandiril, a prominent content creator known for testing and showcasing it. He conducted an experiment with Ivern and Rengar, revealing that Rengar, even without using his ultimate, could attack the Nexus from within a brush, bypassing the usual melee range restrictions.

The extent of this bug’s impact is still uncertain. It’s unclear whether it affects only Ekko, Illaoi, and Rengar or if it applies to all champions with jump abilities and attack buffs. Nevertheless, this glitch provides significant advantages to these melee champions during late-game fights, allowing them to safely attack structures from a distance, much like ranged champions.

However, exploiting this bug requires the enemy to be pushed back to their Nexus turrets, limiting its impact in the early to mid-game stages. Thus, while it presents a notable advantage in certain situations, it doesn’t offer an overwhelming benefit for consistent rank climbing. Despite this, it is significant enough that Riot Games will need to address it promptly to maintain game balance and fairness.

In summary, this bug, although humorous at first glance, creates an unfair advantage for specific champions when attacking key enemy structures. Riot Games will likely prioritize a fix to ensure the gameplay consistency.

According to a recent Reddit post, players have found themselves receiving notably reduced experience, catching the immediate attention of the game’s developers.

This newfound issue arises when players mistakenly purchase and subsequently refund a jungle item, triggering an unexpected debuff that lower the experience garnered from lane minions. Such a setback fundamentally alters gameplay dynamics, placing affected individuals at a considerable disadvantage for the duration of the match.

Interestingly, this bug appears to exclusively affect a specific set of players who opt to take the summoner spell Smite while occupying roles outside the traditional jungle position. While this may limit the bug’s impact to a niche segment of the player base, its severity has nonetheless prompted swift action from Riot Games.

Acknowledging the community uproar, Riot Norak has responded to related Reddit threads, soliciting replays and ensuring investigation into the matter. This outreach has prompted an influx of testimonials from affected players.

Reports indicate that players who inadvertently bought and refunded the jungle item found themselves permanently afflicted with lower minion experience. This unintended consequence is speculated to stem from Riot’s adjustments to minion experience distribution for jungle roles, affecting players who unwittingly interacted with the item.

Even after attempting to rectify the situation through item refunds, the debuff persisted, effectively condemning affected players to a game-long handicap. However, with Riot’s active engagement and commitment to resolving the issue, a resolution is anticipated in the near future.

It is widely anticipated that the forthcoming Patch 14.9, slated for release on May 1, 2024, will include a fix for this disruptive bug, restoring balance to the game’s experience mechanics.

Despite the game’s extensive development spanning over a decade, it remains susceptible to occasional bugs and technical glitches, a testament to the complexity of its aging engine.

While minor bugs are commonplace in the ever-expanding roster of League, none have quite matched the severity of the recent afflicting Kled. In a bizarre twist of fate, Kled faces the perilous prospect of losing all health upon leveling up, abruptly dismounting and plummeting to a precarious 1 health point.

This vulnerability renders Kled exceedingly susceptible to any incoming damage, including the slightest tap from a lowly minion, spelling almost instantaneous demise.

This situation is compounded by the involuntary nature of leveling up, which occurs naturally as foes fall in battle. Thus, Kled players find themselves thrust into situations during laning phases, as the sudden depletion of health leaves them dangerously exposed to enemy aggression.

As shown by YouTuber Vandiril, the phenomenon unfolds with unsettling regularity, casting uncertainty over the gameplay experience. While URF mode may beckon with its promise of frenetic action and unrestrained chaos, Kled serves as a cautionary tale for players navigating the whimsical realm of Runeterra.

Alarming as it may be, reports suggest that this catastrophic bug is currently confined to the confines of the limited-time URF mode, renowned for its lighthearted, albeit competitive, atmosphere. Nevertheless, the widespread occurrence of this bug among Kled players underscores the urgency of avoiding the champion until a resolution is reached.

In light of these developments, players are advised to make caution when selecting their champions, lest they fall victim to the unforgiving clutches of this nefarious bug.

League of Legends boasts a sprawling player base and a dynamic gaming environment. Yet, like any complex system, it’s not immune to occasional bugs. Despite the developers’ best efforts to quash these issues with patches, the cycle of fix-and-break persists, especially during the rollout of new seasons.

The advent of Season 14 heralded a plethora of exciting changes: fresh items, revamped jungle camps, and map alterations aimed at injecting renewed excitement into the game. However, amidst the anticipation and exploration of these updates, players have stumbled upon what appears to be a troubling bug concerning the Elder Dragon since the introduction of Patch 14.2.

The player base has become convinced that the Elder Dragon’s mechanics have been compromised. Traditionally, after a team secures four dragons and claims the dragon soul, the Elder Dragon is expected to spawn after 6 minutes.

However, reports have surfaced indicating that the Elder Dragon is now emerging a full minute earlier, spawning after only 5 minutes.

This concern gained traction as players took to forums and social media platforms to voice their concerns. One player’s initial suspicion prompted others to corroborate the anomaly, lending weight to the assertion that something indeed seemed amiss within the game’s mechanics.

Intriguingly, testing conducted by players confirmed the discrepancy. According to in-game tooltips and evidence, the Elder Dragon is indeed spawning prematurely, aligning with the altered five-minute interval following the acquisition of the dragon soul.

Curiously, amidst the community, there appears to be no explicit mention of this adjustment in the official patch notes, further fueling speculation and raising questions about transparency in communication between developers and players.

As discussions surrounding the Elder Dragon bug continue to unfold, players find themselves navigating an uncertain landscape where the line between intended changes and unintended.

However, despite the efforts to enhance his appeal, its gameplay reception has been mixed. Early statistics reveal lackluster win rates, suggesting a steep learning curve for players as they grapple with understanding the champion’s mechanics.

Some players even argue that the champion’s playstyle diverges significantly from traditional roles, further complicating its integration into team compositions.

Smolder’s bug that disconnects the entire enemy team

Yet, amid the uncertainty surrounding his performance, a significant bug has emerged, casting a shadow over its release. Reports have surfaced detailing a critical issue wherein encounters involving the champion and teams with the Elder Dragon buff result in mass disconnections among the opposing players.

The bug appears to trigger when Smolder executes its ultimate ability during teamfights, making enemy champions freezed and causing them to disconnect.

Evidence captured in Reddit clips depicts unsettling scenes where entire enemy teams disconnect mid-game, effectively handing Smolder players undeserved victories. While reports of disconnections have circulated in recent matches, the correlation between his presence and the frequency of disconnects raises suspicions of a systemic issue linked to the champion’s abilities.

As the community grapples with the ramifications of Smolder’s unintended impact on gameplay, concerns mount regarding the integrity of competitive matches and player experiences.

The prevalence of disconnection incidents, particularly in conjunction with the interactions with the Elder Dragon buff, underscores the urgency for Riot Games to address and rectify the underlying technical issues plaguing the game’s stability.

In light of these developments, the trajectory of Smolder’s reception remains uncertain, with its potential overshadowed by the disruptive effects of unresolved bugs.

While the regular cadence of patches typically resolves most issues in the game, these particular bugs demanded immediate attention from the developers to maintain the integrity of gameplay.

League Patch 14.2 micropatch

• TF: Red Card didn’t slow the primary target
• Karthus: Weirdness with Wall of Pain resists
• Unflinching: Weird interactions with Graves’s Smoke Screen that gave people infinite stats

One of the identified issues pertained to Karthus and his W ability, Wall of Pain. An unintended interaction occurred when enemy players traversed through the wall, resulting in an abrupt and excessive increase in magic resist for the affected champions. This unintended behavior not only disrupted the balance of engagements but also nullified Karthus’s ability to inflict further damage on those affected.

Similarly, Graves faced a critical bug related to his W ability, Smoke Screen. This ability, designed to reduce the visibility of enemies, inadvertently provided an unintended near-infinite stat boost to players walking through the smoke.

Intriguingly, this exploit only manifested when players with the Unflinching rune entered the Smoke Screen, turning what was meant to be a powerful debuff into a game-changing buff. This interaction significantly compromised Graves’ strategic plans and gameplay effectiveness.

Twisted Fate, the third champion, encountered a specific issue with his W ability, Red Card. Prior to the fix, the ability failed to apply its intended slow effect to the primary target, affecting only those in the immediate vicinity.

This prompted Riot Games to swiftly implement a fix, ensuring that Twisted Fate’s Red Card now functions as intended, maintaining the balance of his abilities in the game. Notably, Twisted Fate has been a topic of extensive discussion within the League community due to ongoing changes tested on the PBE aimed at enhancing his critical strike build.

In conclusion, the developers’ proactive approach in deploying a micropatch ahead of the scheduled major patch reflects their commitment to addressing critical issues that could significantly impact the game’s balance.

Riot Games, in its ongoing efforts to maintain a dynamic and engaging gaming environment, frequently introduces patches that can significantly impact the meta and gameplay.

Despite the constant evolution of the game, certain champions can sometimes be overlooked or experience bugs, especially if they aren’t among the player community’s most favored choices.

A notable exception to this is Aatrox, a champion enjoying substantial popularity. However, the recent buff intended to improve Aatrox’s passive, Deathbringer Stance, has inadvertently given rise to a troubling bug.

As demonstrated by League of Legends content creator Vandiril, the change to Aatrox’s passive on the PBE prevents its cancellation, providing a quality-of-life improvement to the ability.

Regrettably, this seemingly positive adjustment has introduced a more significant problem. When Aatrox uses his Q ability immediately following his passive, the Q fails to deal damage on any enemies.

This bug significantly impacts Aatrox’s gameplay, especially considering that his Q is a fundamental source of damage, and it disrupts the fluidity of his combos. Players are now forced to wait for the complete animation of his passive before launching the next attack, resulting in a slower and less effective combat experience.

As of now, this bug is limited to the PBE, suggesting that Riot Games may address and rectify the issue before the changes hit the live servers.

Until September 18, it was widely believed that this gacha Jhin skin could exclusively be obtained from Cosmic 2023 Capsules. However, League of Legends streamer and content creator I Keep It Taco has debunked this notion.

Bug that allows you to get Dark Cosmic Erasure Jhin through Hextech chest

“There’s a bug that allows you to unlock Dark Cosmic Erasure Jhin ($200) with regular Hextech Chest and Keys. If you’ve been saving them for years, abuse it.”

Apparently, there’s a glitch that allows you to acquire this Mythic Variant skin using a regular Hextech Chest and some keys.

Unfortunately, the odds of getting it this way are not in your favor, and the drop rate is exceptionally low. I Keep It Taco, a dedicated Jhin player, had only a 0.0003% chance of getting Dark Cosmic Erasure Jhin. Even after opening over 600 chests and more than 50 orbs, he still didn’t get it.

“Someone did the math and the chances of me getting it in the hextech chest are 0.0003%. I opened 600+ boxes and 50+ orbs. We couldn’t open 1000+ cause we ran out of chest so we got more keys for next year when we get more boxes. WE TRY AGAIN NEXT YEAR”

When questioned about this bug by MattyLoveGaming, I Keep It Taco mentioned that Riot had made an error, which is why you won’t find this skin in the regular Hextech Chest loot pool.

If you’re hoping to obtain this skin through Hextech chests, it’s advisable to open as many as you have, especially if you’ve been saving them for a special occasion. However, the chances of obtaining it through rerolls are next to impossible.

Sadly, according to the content creator’s post, this interaction has already ended in 19 September. So, your best bet is to focus on opening Hextech chests and hope for some luck for the next year occasion.

However, if you prefer not to exploit glitches, you can still obtain Dark Cosmic Erasure Jhin by opening the limited-time-only capsules. But act quickly, as the event is coming to an end with the arrival of patch 13.19 on September 27.

Since her introduction on the League PBE earlier, the champion has been completely ‘fine’, and the community has been making sure Riot is aware of all of her unusual interactions with pre-existing features.

Briar changes on PBE to address bugs

Briar will get a round of adjustments, updates, and bug fixes that address certain known difficulties that the champion is encountering on the PBE, according to a tweet sent earlier today by League dev and Briar champion designer August Browning.

The first modification she’s getting is a patch that will allow her to obtain more healing from health regen items (like potions) while she’s low on health. Briar is the only champion in the game that does not have a basic health regen, and all of her abilities require health to perform, therefore this patch is obviously needed.

Furthermore, her W, Blood Frenzy, will now prioritise huge jungle monsters over tiny ones, making camps like Raptors and Krugs more effective.

The major change for Briar in these rounds of PBE updates is the how her ultimate wipes CC. Her ult, Certain Death, fires a long-range missile at an opponent champion, which Briar then flies to.

According to League content creator Vandiril, he provided us with a demonstration video of Briar’s wonky interaction with Mord. While the missile will clear her of any CC, it is not intended to cleanse Mordekaiser’s ult, Realm of Death. This bug was reported early today, prompting a rapid reaction from League developers.

Briar is currently slated to arrive on live servers with Patch 13.18, which is set to release on September 13.

Team Liquid and Golden Guardians faced off in the LCS’s Lower Bracket semifinal match on August 13. Which team would receive a straight ticket to Worlds 2023 and which would have to compete in another qualification in order to attend it will depend on the outcome of this match.

The first two games of the series were won by Team Liquid, and it appeared TL would quickly win the series. But Golden Guardians made a comeback attempt by winning games three and four.

“GG Huhi took Unsealed Spellbook and switched to Teleport. The Teleport summoner spell switched to Unleashed Teleport which caused Huhi to permanently have Teleport instead of his original summoner spells.”

The fifth game was intended to decide which team would go to Worlds, but it was interrupted by a Golden Guardians player who was impacted by a bug. In addition, LCS provides an additional justification for the remake:

“Due to the significant disadvantage caused by this bug that cannot be resolved by chronobreak, League Officials will remake Game 5 of Golden Guardians vs Team Liquid.”

Due to the bug, a pause was declared 12 minutes into the 5th game. The game was stopped for 40 minutes of the broadcast until LCS decided to remake it.

After the break, the game was resumed with no alterations other than the fact that Huhi now has Unsealed Spellbook instead of Teleport as was initially intended.

Golden Guardians’ reverse sweep did not go as planned, as Team Liquid won the match 3-2 and qualified for Worlds 2023. Commentators have questioned if Golden Guardians could have won if their streak hadn’t been stopped by the bug.

They will now drop in position and compete in the Worlds Qualifying Series against a team from the LEC to determine which team would represent the West in the final Worlds in 2023.