Explaining the Ivern-Neeko Daisy bug, its game-breaking potential, and practical counter-strategies for players
The Bizarre Ivern-Neeko Daisy Interaction Bug
A peculiar and unintended interaction between Ivern’s ultimate ability, Daisy!, and Neeko’s passive, Inherent Glamour, has surfaced in League of Legends, creating a scenario where Ivern can passively generate gold without being present on the map. This bug fundamentally breaks several core game mechanics related to ownership, damage attribution, and reward distribution.
This game-breaking bug allows Ivern to claim minion kills, champion takedowns, and gold from anywhere on the map while Neeko, disguised as Daisy, performs the actions.
League of Legends’ immense complexity, with its vast roster of champions, intricate item system, and layered mechanics, creates a fertile ground for unexpected interactions. While Riot Games maintains a rigorous patching schedule to address balance and functionality, the combinatorial explosion of abilities means some bugs can linger undetected for extended periods, only emerging under specific, rarely-seen conditions.
Patches primarily target widespread balance issues and critical gameplay bugs. However, hyper-specific champion interactions, especially those involving newer or reworked mechanics like Neeko’s mid-scope update, can slip through initial testing. The constant introduction of new content ensures that the game’s codebase is in a perpetual state of flux, making absolute bug eradication a practical impossibility.
Mechanics of the Bug: How It Works
Neeko’s updated passive allows her to disguise herself as any allied unit, champion, or neutral monster. When Ivern summons his ultimate pet, Daisy, she is classified as an allied unit. This qualifies her as a valid transformation target for Neeko. As showcased by content creator Hextech Lab, Neeko can successfully assume Daisy’s form, but the disguise initially appears purely cosmetic, as Neeko cannot normally attack or cast spells while mimicking non-champion entities.
The bug activates when Ivern equips items with on-hit effects, such as Kraken Slayer, Wit’s End, or Blade of the Ruined King. Despite Neeko being the player-controlled entity dealing the auto-attack, the game’s code incorrectly attributes the on-hit damage source back to Ivern, the original summoner of Daisy. This flawed attribution cascade extends to all subsequent rewards: gold, experience, kill credit, and assist logic.
Consequently, every minion last-hit by a Daisy-disguised Neeko grants the gold directly to Ivern. In a more severe escalation, if Neeko secures a champion kill while in this form, Ivern receives the kill gold and credit, while Neeko is entirely removed from the assist tracker. This creates a bizarre spectator and scoreboard view where Ivern’s kill count increases without him dealing any visible damage.
Strategic Exploitation and Game-Breaking Implications
The most direct exploitation involves lane assignment subversion. Ivern, typically a jungler, can build an on-hit item and then have Neeko (playing in a solo lane or as support) transform into Daisy. Neeko can then farm the lane safely or aggressively, funneling all gold directly to Ivern’s inventory. This allows Ivern to gain a massive gold advantage from the jungle *and* a lane simultaneously, accelerating his item spikes far beyond normal limits.
Practical Tip: For teams looking to experiment with this before it’s patched, the most effective setup is Ivern jungle with an early Kraken Slayer component and Neeko support. The bot lane becomes a gold-generating machine for Ivern, while the ADC can focus solely on harassing the enemy lane, creating immense pressure.
A more critical broken mechanic involves tower aggro. Since the game registers Ivern as the damage source, but Ivern is not physically present within tower range, Neeko can dive enemy champions under their own tower with impunity. The tower will not target her because, from the game’s perspective, the damage came from an off-screen Ivern. This enables risk-free, zero-counterplay dives that completely undermine defensive lane positioning.
Common Mistake to Avoid: Players attempting this bug often forget that Neeko’s own attack damage is still low. The damage comes primarily from Ivern’s on-hit effect scaling. If Ivern is under-farmed and his on-hit damage is negligible, the strategy falls apart. Ensuring Ivern has at least one completed on-hit item is crucial for the bug to have meaningful impact.
Counterplay and How to Respond
Facing an enemy team using this bug requires specific adaptations. First, identify the strategy early: an Ivern building atypical on-hit items paired with a Neeko is a major red flag. Ward deep to spot if Neeko is transforming into Daisy in a lane. The counterplay revolves around targeting Ivern directly. Since he is the financial beneficiary, crippling him with aggressive invades, constant ganks, and lane pressure is paramount. Killing Ivern sets back the gold funnel significantly.
Optimization Tip for Advanced Players: Draft champions with strong true sight or reveal abilities. A Lee Sin, Rek’Sai, or Twisted Fate can reveal Neeko’s true form, breaking the disguise and nullifying the bug mid-engagement. Similarly, high-burst compositions can focus and eliminate Neeko quickly before she can output sustained damage to leverage the on-hit effects.
On the macro level, communicate with your team to collapse on any lane where Neeko is farming as Daisy. She is a high-priority target because she represents two champions’ worth of threat. Forcing her out of lane or killing her disrupts the gold funnel and wastes the enemy team’s investment in this niche strategy.
Outlook and Likely Patch Resolution
Due to its highly specific conditions—requiring both an Ivern and a Neeko in the same game, with Ivern building off-meta items—this bug is unlikely to become a widespread ranked menace. However, in coordinated play or specific niche queues, its potential to break game economy is significant. Riot Games’ bug reporting system is efficient, and once such an interaction is verified, it typically lands on a high-priority fix list.
Players can expect a fix in an upcoming patch, possibly as a server-side hotfix if usage spikes. The correction will likely involve adjusting the damage attribution logic for on-hit effects when applied by a transformed Neeko, ensuring the correct champion receives credit for their actions. Until then, awareness is key—both to exploit it cautiously and to defend against it effectively.
New Megabonk update finally introduces damage caps: Full patch notes
League of Legends patch 25.14 notes: Kled rework & Yunara’s abilities explained
LoL patch 25.05 notes: Lane swap punishment, Hextech Chests, Arena overhaul & more
No reproduction without permission：SeeYouSoon Game Club » Bizarre Ivern bug takes LoL jungle tax to a new level Explaining the Ivern-Neeko Daisy bug, its game-breaking potential, and practical counter-strategies for players