Sie sind auf Seite 1von 1




All 180+ Mordekaiser bugs ranked by importance and sorted into 17 categories
NightWind42 (EUW) submitted 3 years ago in Report a Bug

Re-posting this on the NA boards, after the EU ones and Reddit

Hey League boards! I'm Nightwind42 and I have the hobby of catching bugs on Mordekaiser. If you don't use
Reddit, you probably don't know me, but here's what I made: A somewhat big list of bugs on Mordekaiser
and finding all of the bugs that occurred during a Mordekaiser LCS game, among other things. You should
check the first link to have an idea of why I'm writing this, now.
And hi Reddit, I'm Naerlyn and you might already know me from the threads listed above, or from the other
bug lists about the new (1 / 2 or old client. I have to post this on the official Boards rather than on Reddit
UNIVERSAL RULES 📜 this time, because it contains 155k characters, while Reddit's limit is at 40k! Also, for a post this long (four
Boards User Guide times the size of the previous Mordekaiser buglist), the forum's formatting can make it slightly easier to
Boards Discord 💬 read.
Official NA Discord 💬
I've been requested to do this and it wasn't a bad idea. Here is the Mordekaiser buglist, but listing the bugs
Discuss the Boards by priority! So that the bugs implying to purchase an Essence Reaver can be put in a different place than the
Red Tracker   one that can make you lose a Nashor. Two things are factored in the importance of a bug: the impact, and
the frequency. That made the sorting very difficult at times. I'd consider a bug making you lose 5-10 cs every
single game more important than one happening every thousandth game but making you lose instantly, but
Dev Corner
what do you do about bugs that have a 100% reproduction rate when the circumstances are met, as well as
a big impact, when these circumstances are rare? Think of never being able to get the ghost of a
The Game Tryndamere, for example. For these reasons, you might disagree with me on certain points, but at least your
Gameplay opinion will probably not be much different from mine.

RANT That doesn't mean that I won't put jokes or memes here and there in the topic. Actually... since we are not
Player Behavior on Reddit, there is no bot to protect you from the rickrolls here! (Hi Griff ;) )
Story, Art, & Sound Also, you can go to the end of the post for a special category, the bugs that are fun (I can understand if you
Recruitment don't want to read everything... it is 84 pages long).
Each bug description is made of Liquid four parts:
- Description of the bug
Teamfight Tactics
- Consequences of the bug (how they affect the gameplay)
- Information about the reproduction. Mostly just how to reproduce the bug (... that's often very simple), but
Report a Bug also the reproduction rate, and sometimes speculation about what caused the bug, or which other bugs it
might be related to.
Creative Corner
- Examples, be they videos or screenshots, if I have some.
Concepts & Creations
Streams & Videos The order within each category does not mean anything. From most to least important, here we go!

General Discussion Tier 1 - These bugs will happen in every single game and will make you lose at best 5 minions, at worst a few
Memes & Games kills.
1) The second activation of the W will not damage every enemy, when the skill was bound to another ally and
both areas of effect were connecting when the spell was recast. Three most common scenarios:
Event Finder
- Two enemies are in range and only one gets damaged.
Mechs vs Minions - Many enemies are in range and only two get damaged.
- Many enemies are in ranged and all but one get damaged.
Based on a sample of 50 attempts, this bug has a 40% reproduction rate.
Ask the Community
Report A Bug Consequences:
Client Discussion 1) This will make you miss last-hits in every game.
2) It slows your push, and also your jungle clear in Twisted Treeline (because you'll have someone to jungle
Service Status
with you, hence to be bound to you).
3) And obviously, I don't have to tell you about the consequences when that happens while fighting

Culture Reproduction information: Go in lane, cast your W to a nearby minion, go inside the enemy minion wave
without leaving the connecting range of the Harvesters of Sorrow, re-cast W. The expected result is that all
This is the place to report bugs that
of the minions should take the second part of the damage, the observed result, when the bug occurs, is that
you find within League of Legends.
not all of them do. This can easily be checked through the damage shown on the enemy minions (and is
Something that occurs within the
Client, patching related issues, or easier when you put more points in W). If it's inferior to the reactivation damage... a conclusion is easy to
anything that involves gameplay draw.
(stuns not working, unintended
interactions between abilities, vision Example: Video
issues, etc.) should be posted here!
Please do NOT post about
disconnects or lag. Instead redirect
2) The dragon ghost behaves as well as a young teenager maining Vayne. In other words, it's super hard to
those problems to Ask the control it. Giving the first orders is fine, but the drake will end up at some point resetting its to-do list and will
Community. start going where he pleases, and/or will be uncontrollable for a few seconds.
So the drake will start attacking the minions around, or going back to you, when it was told to move
somewhere, attack a turret, or chase a champion.
Basically, follow these steps when Note: This bug does not involve any enemy leaving sight range.
reporting an issue and keep the
content focused on active bugs in Consequences: The dragon puts one or several attacks on the wrong target, thus wasting time on the
League of Legends (Game or Client). drake's lifetime, seconds during a fight, and/or drake hitpoints. This is made even worse by the fact that the
We want to learn about all the bugs
drake has a 0.5 attack speed and cannot cancel its attack, thus locking him for 2s every time it decides to
you guys discover, but we also want attack something.
to organize them, track them, and
make sure we have the information Reproduction information: One of the sources of this bug is related to Mordekaiser and the minions around
we need to fix them! Before you him. Him being attacked by minions or killing minions can make the drake glitch like this. This is probably not
post, please consider what kind of a all of the cause, though.
bug you're posting, and categorize it
appropriately using the suggested
tags below:
Tier 2 - Almost as important. Those bugs all happen every game or nearly, and rarely won't be impactful. The
[Gameplay] - Champions, items, two above needed their own category, though.
and game systems, etc
[Client] - The air client, patcher, 1) Let's start with a pack of other things that go wrong with the Harvesters of Sorrow (W). If you attempt to
etc cast a spell right after reactivating it, the spell has a chance of not dealing damage. Or other similar things.
[Crash] - Bugsplats Unlike the bug 1.1, those bugs can occur even when the W was self-cast, or if your circle doesn't connect
Thanks in advance for your awesome
with your ally's. Here's what can happen:
bug reports! I) W -> basic attack: The basic attack can deal no damage.
II) W -> Q: The Q can deal the damage of a basic attack only. The Q buff will still be consumed.
III) W -> E: The E can deal no damage to some of the targets, or to those that were hit by the W, or deal no
: Eeaugh! Bugs are damage at all.
gross! Ugh! IV) W -> Smite: The smite can deal no damage.

I) Mostly makes you miss minions. That's not the worst bug when it comes to fight champions. Still though,
when first you leave a minion alive because of the 1.1 bug, and then can't finish it either because this bug
occurs too, thus end up missing the last-hit, it's sad.
II) Same, but also impactful against champions, 'cause losing a hundred damage in a lane trade is quite the
issue. It also delays the activation of your Stormraider's Surge.
III) This one happens less often, which is fortunate because it slows your push as well as making you miss
minions and being harmful on trades.
IV) And here goes the gravest of all when it happens. The Smite not dealing damage. You can imagine that
it's not really good to have that happen while you're farming your jungle. But... now, you can imagine what it
becomes when you're fighting over a monster, a buff, or worse. A drake or baron. You heard it well,
Saintvicious has a champion that he can play if he wants to have an excuse for his... issues.
TLDR: Make you miss minions and lose trades or kills.

Reproduction information: (boring stuff here) Not much to say, I'm afraid. Just activate your W, then:
I) Press W again, then basic attack. The attack is expected to deal damage, but won't if the bug happens.
II) Press W again, then basic attack while your Q is activated. The attack will only deal physical damage.
III) and IV) Press W again and use E or Smite during the cast of the Harvesters of Sorrow, and that spell
won't do what it should.

II) Video
III) Screenshots: Before / After / Zooming on the health
IV) Video

2) Another bunch of bugs with the W, this time without needing another spell alongside. So the bug 1.1 was
about the W not damaging all of the opponents it should affect. But here's a bunch of other things the
second activation of that spell can do wrong:
I) Most common and most important: Deal its damage, but without healing anyone.
II) The other way around! Heals, but without damaging. Quite rare.
III) Heal one second after the ability is used.

Consequences: These can completely turn fights around against Mordekaiser or his team, and are only not
in the first category because they do not happen as super frequently as the bug 1.1.

Reproduction information:
I) The reproduction rate is fairly low, yet high enough to at least happen in many games. You can at least try
to reproduce the situation to see if there's anything related to one of the parameters involved in it, but I'd
consider that unlikely. The more information, the better, though, so I'll tell that I also had this happen on an
Anivia ulted by a Malzahar while she was surrounded by allied minions, enemy minions, enemy champions,
allied champions and enemy summoned pets (voidlings).
II) There, I can't tell much because I haven't seen that often or recently enough.
III) In the video below, it seemed related to the dashes. Lee Sin dashed away from the drained enemy the
moment the W was recast, and then the particle/projectile from the W came late, thus arrived to Lee after
his dash, causing a long delay before the heal. You can see later in the video that the heal goes towards
Mordekaiser in an earlier stage of the W.

I) Video
III) Video

3) Mordekaiser's champion ghosts lose their runes and masteries, including the keystones.

Consequences: Most of the ghosts would deal way more damage if it weren't for this. Think of the
difference there can be when you simply add the keystones. Now also add the base stats handed by the rest
of the masteries as well as the runes: not only is the ghost weaker because of it, but so are you, since you
get a portion of the ghost's bonus AP and health.

Reproduction information: None. Simply get the ghost of any champion using masteries and/or runes. This
bug has a 100% reproduction rate.

Examples: Anything could work. Here's a video though: Count the attacks done by Ziggs' ghost, three of
them go on the Amumu and no Thunderlord's. ensues. Or that video if you doubt Ziggs' having of a

4) The ghosts have inaccurate targeting. If you alt-right-click on the ground less than 100 units away from an
enemy unit, the ghost will attack the unit instead of walking on the designed location.

Consequences: There's many consequences to this.

I) If you don't know about this bug, you probably won't be able to solo Nashor as Mordekaiser is supposed
to easily be able to when he's got a dragon ghost. I explain this in the video below, but basically, you want to
move the dragon ghost in melee range of the Baron so that it tanks its attacks, and prevents you from taking
the damage debuff it applies. So you'll alt-click right next to the Baron to make the ghost go near it, in melee
range, so that it's closer to the Nashor than you are. But if you do so, because of this bug, the dragon will
take that as an attack command, and attack the Baron from its max range, thus not tanking it for you at all,
and here goes your Nash, let alone your solo Nash.
II) Moving champion ghosts like you would want them to move. I've lost the count of the amount of times a
champion has been stuck under the turret, inside a minion wave or under enemy fire, and has died for it,
because I couldn't get them to move as I had planned it.
III) Same, with the dragons. On one hand, the dragon has less risks of dying from it; on the other hand, every
attack channeled on the wrong target is two seconds of the drake wasted, because of its low attack speed.
TLDR: Makes ghosts way harder to use.

Reproduction information: Get a ghost, try to make it move near some enemies. The expected result is to
have the ghost move near the enemies, the observed one is that it will attack the enemies. This is bug with
a 100% reproduction rate.


Mordekaiser bugs - 2.4: Ghost targeting bug

5) The drake ghosts have a very low amount of health, AD, armor and magic resistance compared to their
living brethren.

Consequences: The drake ghosts will be far less menacing and useful than they would have otherwise been,
and are very vulnerable to Smite, Feast or Consume. The third screenshot will show you that their health can
be cut down by as high as 75%. Also, theoretically, that should reduce the bonus hitpoints that the dragon
ghosts give you, but the next number will add some on that matter.

Reproduction information: Check the stats of a dragon, kill it (don't forget that you need to be level 6), then
check the stats of the ghost. This bug has a 100% reproduction rate. However, I cannot tell you how the
stats of the ghost scales... since for the health, for example, it starts at 20-25% of the dragon's health, and
ends up going upwards. Also, those stats depend on time, not on the drake's level (You can compare the
screenshots 1 and 2 for the AD/Resistances part as a proof of this).

Examples: Hitpoints: Screenshot 1 / Screenshot 2 with a comparison of both drakes' health / Screenshot 3
with another comparison
AD/Resistances: Screenshot 1 / Screenshot 2

6) And they also give Mordekaiser a very low amount of health. 60 per drake level, regardless of the health
of the ghost.

Consequences: You get fewer bonus hitpoints than you would have gotten through enslaving the drake, if it
weren't for this bug. For example, at a level 6 of the drake, you'll get 360 health instead of the 1k+ that
you'd have had if the ghost were a clean copy of the monster.

Reproduction information: Unlock your ultimate, kill the dragon, and watch how much health you gain on the
Child of the Grave buff icon. 100% reproduction rate again.

Examples: Level 6 screenshot / Level 12 screenshot (Sorry for the low quality of these two screenshots, but
that was a game-side issue that has been introduced around the mid-season and fixed very recently.

Tier 3 - Many of the bugs in there are very impactful, but happen rarely. Some others are not as bad but
happen often, if not always, and some others are what prevent items to be viable or good on Mordekaiser.

A/ Rare but impactful:

1) If an enemy flashes one of your Qs, the animation will complete (Animation, sound effect) but the ability
won't do anything. So the animation will continue after the flash, but the spell will not work.

Consequences: That bug just has one consequence: Making you miss kills. Solely. But it's damn good at
that. Your third Q has a tendency to hurt, and generally, your opponent flashes it to avoid dying. Seems
pretty simple.

Reproduction information: Try to use your third Q on an enemy, have the enemy flash during the animation.
Since the Q cannot be cancelled, the attack is expected to deal damage (especially since its animation goes
through entirely), but the observed result is that it will not.

Examples: Video 1 / Video 2

2) The drake can be replaced by a normal ghost, the same way a normal ghost can be replaced by the ghost
of a drake.

Consequences: If you kill the dragon while having a champion ghost, the champion ghost will be replaced by
the dragon's. This is normal, and fine. But that happens both ways around. If you ult an enemy, then kill the
drake, and then have the enemy die by the remaining part of your ult, you lose the dragon ghost for
something that will be a downgrade in the nigh entirety of the cases.
And that's not something you can play around. Because if a fight breaks out at drake, then you have to
either save your ult and hope that you can win the fight without using it, or use it and hope that the ulted
target will die before your taking of the drake (or not die at all).
Do you avoid ulting someone while fighting over the drake lest he die during the DoT of the ultimate and
after the dragon's death?
Do you delay the taking of the drake to have that champion die before?
Do you avoid attacking the enemy you've ulted so that he doesn't die after the drake dies?
In my opinion, having to choose between these options is not really healthy, at all.
TLDR: Will either randomly make you lose dragon ghosts, or will force you to play very weirdly around your
ultimate during dragon fights.

Reproduction information: Go around the dragon. If you're testing the bug alone, lower the dragon's health.
Go find an enemy (have him around or just teleport to him), reduce his health and ult him, teleport back to
the dragon (in case you haven't figured, I'm not talking about the summoner spell teleport), kill the dragon
before the champion dies, and then as the champion dies, you'll lose the ghost of the drake to get the
champion's instead. This has a 100% reproduction rate. Its impact is huge, but such a situation doesn't
happen often.

Example: Video

3) Ghosts do not use the passive of their Runaan's Hurricane if they happen to have one (despite having its
yellow orb floating around them).

Consequences: This will affect you every other or third game, but dangerously so. An AD Carry is generally
way more frightening with a Runaan's than without. I mean, if you don't replace the Runaan's with another
item. Well guess what, same goes for the ghost. So your ADC pet will not be able to attack several targets at
once, will thus deal less damage, and also provide you less shield and less sustain if you happened to have
a Gunblade.

Reproduction information: Have an enemy buy a Runaan's Hurricane, kill them with your ultimate. Expected
result, having the ghost hit three targets at once; observed result, the ghost will only attack its primary
target, and will not have the yellow orb around it.

Example: Video

4) One of the very few bugs that advantages Mordekaiser: If Mordekaiser's Children of the Grave (R) kills
someone while they're untargetable and out of the map (Shaco's R, Master Yi's Q and Maokai's W. I don't
know if this also works with the other untargetabilities such as Fizz's E or Xayah's R), the ghost will be totally
invisible to every player for its entire duration. Extremely rare, but also extremely unfairly powerful.

Consequences: You can just figure out by yourself on the videos. The only way the ghost can be hit is
through AoE and the attack move command, as far as I'm aware, and don't set your hopes too high, you
don't get an indication of the ghost's location upon hitting them, not can you use pink wards. So not only is
the ghost way harder to take down, it's also pretty damn confusing to face... and to play with. Mordekaiser
doesn't know where the ghost is either, until it attacks something.

Reproduction information: It's not easy to reproduce alone, and it takes some timing and knowledge of
Mordekaiser's damage to do it. Important note: I don't know if it only works against champion whose spell
removes them from the map (Shaco's R, Master Yi's Q and Maokai's W), or if it also works with the other,
standard untargetabilities such as Fizz's E or Xayah's R. The reproduction rate of this bug is of 100% when
those conditions are met.

Examples: Video 1 / Video 2

B/ Make items bad on Mordekaiser:

5) Activating a Titanic Hydra while your Q is enabled will not reset the timer of your basic attack.

Consequences: Consequence for the Titanic Hydra users: Think of Mordekaiser like Fiora, as far as the way
you want to use the Titanic. Fiora has 4 options to use her attack resets:
I) Basic attack, then Titanic Hydra, then E.
II) Basic attack, then E, then Titanic Hydra.
III) Basic attack, then Titanic Hydra and E at the same time, used on the same attack.
IV) Basic attack, then E, then you use the second E-empowered attack, then Titanic Hydra.
Let's now adapt those to Mordekaiser:
Option I: Not a good idea. Mordekaiser wants to get his Qs off as fast as possible due to them dealing major
damage and him not having ways to stick to his target, save for Stormraider's Surge. Using your Q as your
3rd basic attack is pretty risky.
Option II: Theoretically the best option... without the bug. Because of the bug, if you do that, you waste one
of your AA resets.
Option III: In this case, you lose an AA reset anyway, bug or not.
Option IV: Opposite issue as the one the first option presents: You'll use the Hydra as your 5th basic attack,
and Mordekaiser cannot always stick near his enemies for so long. Buying a Titanic Hydra might mean that
you're also interested in getting a Trinity, but even with that attack speed, five attacks in a row is not
something Mordekaiser is often allowed to do against champions at the stages of the game when he'll have
a completed Titanic Hydra.
Actual consequence: Mordekaiser simply will not buy that item, while it could have been interesting on him.
This is a consequence of this bug and of the following bug (3.6).
TLDR: Makes Titanic Hydra a weak item on Mordekaiser, while it could have been great otherwise.

Reproduction information: Grab a Titanic Hydra and try to do the combo II), which is basic attack -> Q to
reset the attack timer -> Titanic Hydra after this attack to reset the timer again. Expected outcome: Your
third basic attack's timer is reset, observed outcome: your third basic attack's timer isn't reduced at all.
This has a 100% reproduction rate.

Example: Video

6) When a minion has less current health than the magic damage dealt by this ability, the physical damage
won't be applied. This also means no life steal, no on-hit effects, no Titanic Hydra, etc.

Consequences: As I said, when that bug occurs, your attack will not apply any on-hit effects, nor will it regen
you from life steal, and will deal less damage than it should. On many aspects, it could do little. On others,
though... from most to least impactful:
I) No Tiamat / Ravenous Hydra / Titanic Hydra proc.
II) Less heal from Gunblade.
III) No stack gained on the Guinsoo's Rageblade.
IV) Just like for the Gunblade, no lifesteal (and let's ignore the case of the regen granted by an Ardent
V) No MR gained with a Wit's End.
And commenting the other way around:
The point V) does not really matter as I've yet to see a Mordekaiser build that item. Point IV) is mostly the
same, I've happened to build a Bloodthirster on Mordekaiser and you do grab a Cutlass at some point if you
plan on buying a Gunblade, but still, the situations are rare enough. Point III) is not that important either,
because even though I am a fan of Guinsoo's on Mordekaiser, it still doesn't really impact the game - it'll
take you one to three additional attacks to stack the item while you're attacking minions. So it's not much.
Moving on where it's actually impactful: Point II): As Mordekaiser, if you have a Gunblade, you'll have from
150 to 200 AD. Your Q removing the damage of the basic attack means that you will lose 15% of 150-200 as
a heal, hence 23 to 30 hitpoints per time the bug happens, and it does happen a lot.
And to finish with point I): I think I have expanded enough on how much the interaction between Titanic
Hydra and the Mace of Spades was an issue for the Iron Revenant. Guess what, that adds up to it! This bug,
alone, has made me opt away from Tiamat when I was considering purchasing it. Because in lane, you want
to use your Tiamat/Hydra on minions to deal collateral damage (hi Graves) to champions. And in lane, this
bug has plenty of occasions to occur. Also, aside from just removing you that option to poke through Hydra,
this can also considerably reduce your pushing power, as shown in the video below.
TLDR: Makes Tiamat items rather bad on Mordekaiser, reduces his sustain.

Reproduction information: Check the damage dealt by your Q, and use your Q on a target whose current
health is lower than this damage (past resistances). The Q is expected to deal physical and magic damage,
but will only deal its magic portion. Reproduction rate of 100%.

Example: Video

7) You cannot bind a Knight's Vow to Mordekaiser's champion ghosts, even though they are technically
allied champions.

Consequences: Knight's Vow is a pretty neat item on support Mordekaiser, and by support Mordekaiser I'm
not just referring to the role, but also to the playstyle. There are builds for Mordekaiser mid, jungle and top
that make him support a carry... and the Vow compliments them pretty well. Mordekaiser always has a big
portion of his shield that simply goes to waste because it constantly decays. The Knight's Vow allows you to
just stack up your shield while you stay back, and use it on the damage "share" of the Vow. Additionally,
adding a part of the carry's damage to Mordekaiser's already great sustain does him wonders, and I don't
need to talk about the stats of the item that include movement speed.
Now all of this sounds great... but even greater when Mordekaiser can be on both ends of the item by
himself. Have his ghost bring him the regen on top of the shield it generates and on the health you get back
thanks to a hypothetical Gunblade, and gaining movement speed so long as the ghost is alive (you tend to
make your ghost kinda clingy). These things should be super good on Mordekaiser, but cannot be due to the
fact that you cannot bind yourself to the ghost, that is a copy of a champion, and considered as an ally
Lastly: There's a consistency issue when you can bind Zeke's Convergence to a ghost, but not Knight's Vow.
TLDR: Makes Knight's Vow considerably weaker than it should have been for Mordekaiser.

Reproduction information: Buy a Knight's Vow, get a champion ghost, try to bind the Vow to the ghost, it
won't work despite being expected to. 100% reproduction rate.

Example: Video: You can see that after binding the Zeke, I try to bind the Vow as well, and the HUD reads
"Invalid target selected; select a valid target." when I try to put it on the ghost.

C/ The bugs that didn't belong above but couldn't fall below:

8) The dragon ghost doesn't gain Mordekaiser's bonus AD.

Consequences: The dragon ghost's AD is pretty low, and most of the damage of that thing comes from the
percent health damage that it inflicts with every hit - especially when it comes to hitting turrets early on.
By pretty low, I mean that it can be between 50 and 80 AD early into the game. Ghosts are supposed to
receive 100% of your bonus AD, so you could almost double that amount by solely using Gunblade, AD
marks and the Natural Talent mastery. Basically, without the bug, the drake would on average deal 30% to
50% more damage... which is an estimation based on calculations that can be flawed because I have no
clue of how the drake ghost's damage is actually calculated. I should, but it just appears not to go that way.

Reproduction information: Get some bonus AD, unlock your ult, kill the drake to grab its ghost, see that its
AD remains gray. If you want the proof that it's not just visual, buy 100 AD.

Example: Screenshot (I had 65 bonus AD from the Scimitar).

9) Mordekaiser does no longer get any of the gold that the ghosts receive. When a ghost kills a minion or a
champion, Mordekaiser gets the kill credit, so this is not affected by the bug, but every other way the ghost
would receive money does not make Mordekaiser gain any. It used to, at least around Spring 2016. This
I) Mordekaiser's Relic Shield (and other items of this category).
II) The passive gold generation of the ghost's support items.
III) Skarner's shrines. If two champions (and only two) stand on one to capture it, each will be given 15g. If
it's Mordekaiser and a ghost, he will only get 15g instead of 30.
IV) The ghost's Cull.

Consequences: The consequences aren't hard to guess: you lose gold compared to what you'd have got
without this bug. With a Relic Shield or Targon's Brace, it's fair to estimate that you'll get an average of 5
minions executed thanks to this item, per ghost. Which means an average of 100 gold over the course of
the game. And Mordekaiser bot lane does buy a Relic Shield, so that's 100 gold gone per ghost with that
item already. Besides, your own support might have his own Shield/Targon/FotM. In which case, his
executed minions have a chance to be shared with the ghost, and their money to be lost.
The other things matter less. Note that this bug should also affect other things... if they weren't bugged
themselves. I'm referring to Draven's passive, to TF's, or to the ghosts' support items (Their own minion
share thanks to the Relic Shield line, the coins of the Ancient Coin line, the on-hit of the Spellthief line).

Reproduction information: Get the ghost of a champion, and attempt to share gold with it through any of the
four aforementioned means (so, the afourmentioned means?). This is expected to make the ghost give you
back the gold it'd earned, but will not. Reproduction rate of 100%.

Example: Video for I) and IV) / Another video for I)

10) The ghosts attacks only apply some on-hit effects from the items, and not all of them. Here's a list of
what does not work, sorted by importance:
I) Zeke's Convergence (this should have gone in the category 3.B). Its visuals appear, though.
II) Energized attacks (the charges are never consumed, and the bonus damage is never dealt).
III) Guinsoo's Rageblade.
IV) Blade of the Ruined King... or not always.
V) Executioner's Calling and the upgrades. You might say that it's because the attacks of the ghost deal
magic damage, but to that I'll reply that they apply Black Cleaver stacks, and that when a ghost has a way to
deal physical damage (Jarvan's passive, Recurve Bow, etc.), the Grievous Wounds still don't apply.
VI) Charge of the Energized attacks (attacking does not charge them).

I) Here's time to go back on what I wrote about the bug 3.7. Zeke's is also a fun item on Mordekaiser,
working as a great replacement for the nerfed Rylai's once you get close to the target, because of the
ignited storm applying a slow twice as good as the Scepter's... if the conditions can be met. It appears that,
similarly to the Knight's Vow, using the Convergence with your ghost could be very useful, especially the
ghost of an AD carry. It appears that you have a way to activate your own Zeke's Convergence once you
have a ghost, by simply pressing R to move the ghost (cf. bug 3.11, the next one, which is actually still in a
pretty long while considering how much I have to say about the current one).
You can actually bind the Convergence to the ghost, unlike the Vow. You can also then activate it by
pressing R (note: if that weren't the case, this bug would have stood here due to allies being supposedly
able to bind the ghost). It will put a storm around you and the red thingies around your ghost. It will attack its
target, which will be set ablaze... but will not take any further damage. Only the visuals of the Zeke's will be
applied, without any damage being done. Furthermore, you cannot ignite your own storm by attacking that
target, either.
So what are the consequences? It thwarts that entire strategy and cuts down the damage of your ghost by a
large margin (which always means that it also reduces your shield generation), as well as denying you the
ability to get your 40% slow thanks to your firestorm.
II) Now that bug comes with one downside, and one plus side - note that in my opinion, the downside is
greater. When your ghost has a Statikk Shiv, a Rapidfire Cannon or a Kircheis Shard (I'll ignore that item later
on, just include it with the others) and has 100 Energized stacks, their following attack will not deal any
additional damage. Nor will it consume the stack, so they'll just have the little Energized particles around
them, will stay at 100, and will never deal their additional damage. That's where the positive aspect comes:
if that Zeal item happened to be the RFC, from the point when it's charged on, it will always give the ghost
bonus range, as it will never lose its stacks.
III) Give a ghost a Guinsoo's rageblade (... or so to speak) and it will not be able to stack it, meaning that it
will not:
- Get the bonus AD, thus deal more damage.
- Get the bonus AP, thus give you more AP (you get 30% of the ghost's AP).
- Get the bonus AS, thus deal more damage.
- Reach 6 stacks, thus deal more damage.
Just a loss of damage overall.
IV) And if the ghost has a botrk, it will not deal its bonus damage either. This just means a raw loss of
damage, and it's not hard to figure out by how much: think of the difference between an ADC with this
effect, and without. Also, that means generating less shield - as always.
V) More situational, but would still be rather handy to have these Grieving Wounds, considering that
Mordekaiser very rarely builds GW-inflicting items himself. Morello makes mana wasted and he won't invest
so much just for CDR, Exec's Calling is not an item Mordekaiser can update - armor penetration is not really
what he needs at all.
VI) It doesn't matter much considering that the ghost cannot use the Energized stacks, but it should gain 10
stacks per attack it issues (potentially amplified by RFC's passive), and will not. This can matter in Caitlyn's
case, that I point out below in 9.7 (she can use these items in some circumstances).

Reproduction information: For the Zeke's, just buy one as Mordekaiser, don't bind it to anyone (you'll put it
on cooldown by ulting), grab a ghost, bind it to the ghost, press R to have it activate, then get the ghost to
attack something. You'll expect the ghost to apply a DoT to the target and your storm to be set ablaze by
hitting this target, but instead, only the burning particles will be shown without any actual effect being
For the rest, just buy the item on the champion you want the ghost of, grab its ghost, and follow the steps,
this should not really need any further development - I'm already at almost two entire Word pages for this
one bug.

I) Video
II) and VI) Video
IV) Video (what happens after the headshot will be addressed later and is specific to Caitlyn.)
Haven't got any recording for the other two, sorry!

11) Mordekaiser has two different options in order to control his ghosts: he can either hold alt and right-
click, to make the right-click control the pet and not himself, or he just presses R while hovering the
direction or target he wants the ghost to go to. If he does the latter and presses R, this will activate his
Zeke's Convergence (if he has one, of course). If he uses the alt way, it will not.

Consequences: That is probably not intended to work that way, and certainly not this exact way. I doubt that
Riot planned for champions to be able to activate the Zeke's by controlling their ult-pets... let alone by only
making that work with one of the two ways to control them. But the consequence here is that Mordekaiser
can keep his Zeke's unbound, then kill an enemy to grab their ghost, then bind the Zeke's to someone, then
activate it literally whenever he wants (since he just has to rely on alt to control the ghost before he wants
to make use of the item).
This should also allow you to activate your own Zeke's on your ghost, if it weren't for the bug 3.10.1.

Reproduction information: Buy a Zeke's Convergence, don't bind it, grab a ghost, bind the Zeke's to anyone
(ghost included), try pressing alt, then R, and watch the result for either. 100% reproduction rate.

Example: Video

12) Mordekaiser can heal an enemy Braum when the heal particles go through his Unbreakable (E).

Consequences: It could make sense for Braum to block the heal, but not to receive it in lieu of Mordekaiser
or his ally. Braum cannot steal Sona's heal, nor could he take the projectile of a Mikael's Crucible or of
Soraka's Q buff. Now even though the conditions are fairly rare in Summoner's Rift, being a 3v3 player made
me put this in tier 3 instead of 4.
When this bug occurs, it will completely turn the tide of a fight. For the many of you who don't know,
Mordekaiser's W heals himself and one ally for a tremendous amount. We're talking of 500ish hitpoints at
level 9, on two people. Well guess what? Braum can deny your healing of this amount, and take on himself
both heals, meaning that neither you nor your teammate will get the +500 hp, but Braum will instead get a
+1000, which is basically a full restore (except that it doesn't cure poison, paralysis, burn, sleep or other
status effects).
In 5v5, that bug will not happen so often because most Mordekaiser players don't go bot lane. In 3v3,
however, Braum is currently at the top of the meta and Mordekaiser and him go in the same lane, which
happens to be a 2v2 lane. So this has a lot of ways to happen again.

Reproduction information: For once, the reproduction is a bit tricky. If possible, do that when Mordekaiser
doesn't have any ally minion around. Find an enemy minion wave (so, Braum's wave). Kill two melee minions
and two rangeds. Put Braum between those two minions, facing Mordekaiser. Have Mordekaiser press W
and Braum E. Both minions must be inside the AoE of Morde's W. Reactivate W before the shield wears off,
and watch as Braum steals one of the two heals.
To sum up the situation, you must have in a very close line: The ranged minion > Braum > Braum's shield >
Mordekaiser > The melee minion.
By the way... That bug will not happen if the bugs 1.1 or 2.2 decide to occur at this very moment.

Examples: WARNING, WATCH WITHOUT SOUND! Video 1 / Video 2 that you can watch with sound but that
doesn't have any sound anyway

Tier 4 - The bugs that are also very impactful but happen even less commonly, or are slightly less important
when they occur.

A/ Rare but impactful:

1) Jhin's ghost does not lose bullets upon attacking.

Consequences: That one has two consequences and is pretty well-known for the second one, because it
completely has the potential to be gamechanger. But if the second one is a really positive consequence, the
first one is negative for Mordekaiser.
I) If Jhin dies while he had zero, two, three or four shots remaining, he will never have access to his fourth
shot, because he will be stuck on the amount of bullets he had left upon dying (except if he had zero, where
he'll simply reload to four, and then be stuck on four).
II) If Jhin dies while he had one shot left, he will always be stuck on the fourth shot, thus get the forced crit
and missing health damage on every single of his attacks, which is pretty devastating. It's also funny when
paired up with the RFC bug (3.10.2).
However, the second bug comes with a drawback: Jhin isn't necessarily indefinitely stuck on his last bullet.
After 10 seconds of being out of combat, Jhin fully reload and so does the ghost, so you need to be wary of
that delay and keep him in combat regularly enough lest he lose his Super Sayan form.
So, as I said, this bug can be gamechanger, but goes down in tier 4 because for it to happen, you need to:
a/ Face a Jhin,
b/ Get the ghost of the Jhin,
c/ Do so while he has his last shot (the first consequence of the bug would otherwise belong in tier 6),
d/ Have all of this happen without dying because it would make you lose the ghost,
e/ Have things to make Jhin shoot at after the fight,
f/ Not kill a dragon right after the fight.
Note: Graves' ghost loses pellets and reloads normally upon attacking.

Reproduction information: Ult a Jhin, kill him when he has whatever amount of bullets you want to see the
bug for. The ghost will have the same amount of those. Expected result of Jhin consuming one bullet for
every of his attacks, observed result of him, well, not consuming a bullet for any of his attacks. 100%
reproduction rate.

Examples: Video 1 / Video 2 / Video 3

2) Mordekaiser's W causes FPS issue to some people.

Consequences: It seems to have gotten better lately, but I've seen someone complain about it only a few
weeks ago. This can affect literally anyone. The Mordekaiser player, his teammates, the enemies, can create
unfair advantages or disadvantages, and surely isn't really fun for the person or the people on the receiving
end of that issue.

Reproduction information: Nothing I can really tell to help here. I've personally never had that bug, but have
seen it complained about so many times - be it by people on chats or forums, or by teammates or
opponents, aware of the issue or discovering it as a sour-tasting surprise. So I can't even tell if that's only
affected people with bad computers or with a certain setup, nor can I speak about the reproduction rate.

3) Lulu doesn't seem to like Mordekaiser, at least when it comes to her E. Here's why:
I) If Lulu uses her Help, Pix (E) on an ally Mordekaiser, Pix will not attack alongside Mordekaiser when he has
his Q activated.
II) If she uses it on a champion ghost, the ghost will not get a shield.
III) If she uses it on a champion ghost, Pix will not attack alongside the ghost.

Consequences: First of all, let me get this out of the way: in duo lanes, Lulu is bad with Mordekaiser.
Mordekaiser needs a support that will go forwards, CC, get close to the enemies and stick to their faces.
This comes from numerous reasons: Mordekaiser has a hard time reaching ranged targets (and even some
melee ones) on his own, so having someone to keep them where they are is very appreciated by him (I
mean... the player. Knowing the lore, I'm not so sure that the champion would feel that way. Anyway.).
Secundo, that allows Mordekaiser to make use of the movement speed buff granted by the Harvesters of
Sorrow. Then, still about this spell, Mordekaiser can bind himself to the ally that's in the faces of the
opponents to have it start dealing damage before he can arrive (and potentially allow him to activate his
Stormraider's when paired up with his E), and lastly, he can heal his ally thanks to this very spell.
Since I've just written ten lines about something that wasn't about the bug, this just goes to explain why this
issue isn't one tier above: you don't wanna pick Mordekaiser bot when the support is a Lulu, and vice versa.
And the consequences are just that Mordekaiser loses damage. He loses Pix's damage for every Q-
enhanced attack that he casts while he's shielded (so up to three times per Lulu shield), and that damage
easily goes past 120 for a support Lulu, and 200 for an AP one. Same for what's lost on the ghost, except
that it will affect more than just three attacks, and will also deny you a good amount of passive shield. The
second part of the bug doesn't matter much, except that it prevents Lulu from applying Athene's, Ardent
Censer or the Windspeaker buff to the ghost.

Reproduction information: This bug is not related to the bugs 3.6 (for the first part of this bug) or 3.10 (for
the third part) because Pix's attack is an on-attack effect, and not an on-hit. However, the third part might
have something to do with the fact that ghosts cannot use the passive of the Runaan's (3.3).
As to how to reproduce the bug, here again, nothing complicated, just follow the steps of the bug
description: Shield a Mordekaiser as Lulu, have Mordekaiser activate his Q, watch as Pix's attacks do not
follow his in spite of the fact that they should. Then shield a Mordekaiser's ghost, and it will just move Pix to
the ghost without actually doing anything (aside from preventing Lulu from using her own passive).
Reproduction rate of 100%.

4) The Harvesters of Sorrow will not grant an assist unless they actually damage the enemy. This means: If
your bound ally turned back towards you and got 75 bonus movements speed, you won't get an assist. If
you activated the second effect of the W when he had minions around, thus healing him, you won't get an

Consequences: Every few games, you'll lose assists because of this. For me, I would say that it happens on
average every four games, but that's because I am aware of the bug, thus try to do something besides
simply healing or speeding up when I try to get the assist, and also because I do lots of things on my own.
I saw someone say that it was normal and not a bug, and was similar to Janna not getting an assist for her
passive, but that's wrong. Janna's thing is a passive, Morde's an active, so I will rectify their statement: It's
as if Soraka wouldn't get an assist for healing someone with her W, or as if Sona wouldn't for speeding
someone up with her E.

Reproduction information: Find a teammate and bind your W on him. Then:

I) Have that person walk towards you for just a fraction of a second, then kill an enemy you haven't damaged
yourself, and/or:
II) Re-cast W when that person is near enemies other than the one you want to test the bug on, then have
them kill a champion you haven't damaged.
You'll see that you won't get an assist despite being expected to receive one. Reproduction rate of 100%.

Example: Screenshot proving that Mordekaiser gives movespeed to Lemonnation / Screenshot showing that
he didn't receive an assist in spite of Lemon getting his

5) There are many, many, many bugs when some ghosts lose one or several of their passive abilities. Putting
all of them here would defeat the purpose of this list, so here go the most important:
I) Teemo doesn't have his poison.
II) Fiora's ghost doesn't generate vitals around her enemies (anymore?).
III) Jax's ghost doesn't have his attack speed passive.
IV) Kled's ghost doesn't use his W.
V) Kled's ghost doesn't gain courage.
VI) Quinn's ghost doesn't mark her enemies as vulnerable (... and, thus, doesn't get bonus damage from her
VII) Xin Zhao doesn't have the passive of his W.
VIII) Cho'Gath doesn't get his E.

Consequences: I'll deal with all of them at once since it really is mostly the same issue with all of them: That
reduces the damage of your ghost by a very large amount. They're already ranked by importance, but you
see how much impact that can have in Teemo's or Fiora's case. When it comes to Jax, Kled (IV)) and Xin, it
also affects your damage to turrets.
And again, in all of those cases, since a part of the ghost's damage is given back to you as shield, those
bugs also make you less tanky. You might read that a lot.
In Kled's case, for the part V), it just prevents him from remounting, which means regaining a third of his
total health (on average) and regaining its former movement speed.
In Cho's case, it's probably going to become outdated in one patch (or, will be outdated by the time I finish
this list), but the idea is the same, except that the causes can be different due to Cho's E being a toggle and
not a passive.

Reproduction information: There's nothing to say, just get the ghost of every of these champions and try
attacking with every of them.

Examples: I) Screenshot: There is no poison icon over the minion with the purple cloud.
II) Video
III) Video (You don't need to watch all of it, just the first dozen of seconds or a bit further, the rest is used
IV and V) Video
VI) Video

6) Sometimes, when an enemy dies to your ultimate, you will not get their ghost.

Consequences: That bug is pretty rare. Rare enough so that I've never had it myself over hundreds of
games. But apparently common enough for dozens of people to report it to me. So it's somewhat
uncommon, but eh, the consequences can be pretty rough, as in tier 2 or tier 1 levels of rough. There's a
slight difference between getting a ghost and not getting it, especially when you ulted specifically for the
ghost and not for the damage or the sustain. So when it happens, this bug is consequent enough to be
called gamechanger.

Reproduction information: I have no clue of what triggers the bug. When I've asked some other people to
give me an estimation of how often they encountered the bug, the answer I've got was "as frequently as
facing Trundle", which I keep as a quote because I found that funny. So let's just pray for Riot not to buff the
troll too much.

Examples: WARNING, WATCH WITHOUT SOUND! Video 1 / Video 2 that you can watch with sound. In both
cases, you can see that the enemy still has the ult on them when they die, and by far.

B/ More common, less serious

7) The ghosts will attempt to attack enemies that are in range, even when they're in a bush the enemy
doesn't have vision of.

Consequences: You're sitting in the botlane bush with your Nautilus ghost. The enemies think you've already
gone back to base fifteen seconds ago, but little do they know! You are actually patiently waiting in the bush
for that enemy ADC who is very soon going to pick up that juicy minion wave that's just in front of- NAUTILUS
WHAT ARE YOU DOING! Ngh, let's try something else, your thoughts go as Nautilus revealed you by attacking
that nearby minion. Mordekaiser certainly doesn't have the speed to catch a super hero on the run, so your
Nautilus is not gonna become a villain number one.
All of this to say that this ghost will gladly reveal your position when you'll attempt to ambush with it while
near a minion wave. All of this combines with the fact that you cannot tell the ghost to stop its actions! If
you press S, that will not interrupt the ghost's actions, and there is no alt-S command (cf. Special Tier 1.3).
Oh and you can try to move the ghost around in the bush, but... I now have to take you back to the bug 2.4,
which means that by doing so, you might tell your ghost to actually attack a minion without wanting any of it.

Reproduction information: Put your ghost in a bush while there's a minion wave nearby, watch as the ghost
will attack the minions. Even with auto-attack activated, a champion will never do this if the enemies have no
vision of the bush he's in, which is actually a way to check if the bush is warded, and a plus of keeping auto-
attack on.

8) If Mordekaiser attacks someone with his Q, if the said someone dies even at the very beginning of the
animation, at its first tenth, the animation as well as the sound effects will complete, even though nine tenth
of it didn't have a target.

Consequences: Two consequences here: Commonly makes you miss minions because it will delay the next
attack you'll be able to cast, and more rarely puts you at a disadvantage in trades if your enemy decides to
engage you at this very moment. Yes, the Q takes a hell of a long time to cast.

Reproduction information: Find a minion with very low health and under the fire of other minions, Q it and
watch as you'll lose most of a second for it.

9) If Mordekaiser flashes during the cast of his E or (second) W, the animation of the spell will be issued
from his post-flash location, but the effect will not be moved and will be applied from where Mordekaiser
was prior to his flash.

Consequences: Flashed spells are a fun trait of all of the champions that have one. Not only do they feel
better than flashing before casting the spell (See Riven's R, Cassiopeia's R, anyone's Tiamat, Amumu's Q, E
or R, among numerous other examples), they also are better by giving the opponent less time to react to the
spell. Having that option taken away from Mordekaiser removes an opportunity to have him be funnier and a
bit smoother.

Reproduction information: Press E then flash immediately, or press W, wait a second, then press W and
flash immediately. 100% reproduction rate.
Note: Annie shares this bug with her W, that can be suspected to work similarly to Mordekaiser's E.

Tier 5 - You know the story, same but less important.

1) If Mordekaiser casts his W when he is alone, if a champion then enters the binding range, they will have
their own W circle. If however, it is a minion that joins, it will not get bound by the spell.

Consequences: It's funny. Sometimes, you would want to be able to self-cast your W without binding it to
anything, because you want to wait a slight bit before recasting it, and there is a very low life minion near you
and nothing else around. But here it's the opposite! Minions and champions will behave differently towards
your W, and if you happen to cast your W while you're alone but have a minion wave come towards you with
its first minion just barely outside your binding range... There, that issue will matter a lot.
That's obviously not the only situation, just the most annoying one. Overall, it just matters when you want to
start casting your W as soon as possible, slightly before the minion wave joins, or slightly before you join the
minion wave. It just denies you access to the first part of your W's effect (or well, to a part of it, since both
units will not be close to each other from the very start of the ability, in the cases involved here).

Reproduction information: Cast your W while you're over 1000 units away from the nearest minion or
champion, then walk closer to get into that 1000 range. No minion will be bound by your W, while it would
have been the case if you had tried the same thing with a champion instead.

2) Mordekaiser can stop trying to attack targets when his W pops at the end of the 4s of the effect (despite
having auto-attack enabled). It might also have something to do with the Q, it happened to me before the
third strike of the Mace of Spades. Similarly, when Mordekaiser re-casts W while having his Q enabled, that
Q can take longer than normal to come.

Consequences: This mostly makes you miss minions. It's perfect when combined with the bug 1.1, because
you start by missing the minion because your W fails to damage it, and then you miss it again because your
attack arrives too late. More rarely, it also comes as a downside in trades by making you miss about half a

Reproduction information: Re-cast W while having your Q activated, and the attack that comes after the W
might bug in either of the two aforementioned ways. Fairly low reproduction rate, it doesn't happen every
game, and requires either to be used to Mordekaiser, or to pay attention to it, to notice it.

3) Mordekaiser's E can fail to generate any shield.

Consequences: That is fortunately fairly rare, because when you used it against champions, your E is your
tool to regain a lot of shield (see an example here, watch carefully for when Altec casts his E). It will hit the
champion(s) as well as the minions around, give bonus shield thanks to its effect; all around, that spell can
fill your shield bar on its own, which is an entire quarter of your health added. Well when that bug occurs,
you don't get that shield.

Reproduction information: That bug seems to be pretty rare. I've only noticed it once. It doesn't mean that
it's only happened once though, for it's hard to see during an actual game, as you often chain your spells
thus don't use the E alone.
I can't tell much about how to reproduce this bug as, well, I have no clue. I can only do wild guesses: is it
related to the W? does it make it so you only generate shield off of some of the targets, instead of being an
all-or-nothing thing? Maybe and maybe not, I'm not the one with the answer to this question.

Example: Video

4) The dragon ghost loses 100 movement speed when ahead of Mordekaiser.

Consequences: The drake is sloooooooow without that. And it's an absolute ahead: You can be on the
opposite side of the map as the drake's, it will have 100 fewer movement speed if it goes further from you,
and will be back to the higher speed if it goes towards you. It means that you want to stay ahead of the
drake if you want it to have a decent speed, it means that you cannot just stay behind the drake, W it and
rely on it to speed you up because you'll be faster than it.
Note: A member of the support once told me it was intentional. But that person was not a member of the
dev team, and on the same message, he told me that the other bug that I mentioned there was intentional
as well. And this bug was that the dragon now had a leash range when Mordekaiser was using a skin other
than the classic skin. So... I do not really trust it. At all, actually.

Reproduction information: This was brought by patch 6.11, without anything in its notes mentioning it. Just
get the ghost of the drake, click on it to see its speed, do not cast your W, and compare the drake's speed
depending on the direction he's moving towards.

Example: Video / Before 6.11

5) The attacks from ghosts can't deal the bonus true damage on the Rift Herald if they attack him on his eye,
even if it's champion-ghosts.

Consequences: It's less impactful now that the Herald's been changed, but still, it makes you less flexible
as you should have been while taking this objective down. If you want to take it quickly, you must get your
ghost to tank it, even when it's a squishy ghost, which isn't necessarily what you'd want. So this bug can
make you lose a ghost or will slow you down.

Reproduction information: It's probably another of these on-hit bugs, so you might wanna check if it's
related to any of the 3.10 bugs, codewise. As for how to reproduce that bug, grab a ghost, attack the Herald
with it, and tank the Herald's attacks yourself to have the ghost attacking on the back of it. 100%
reproduction rate here.

Example: Video

6) Ghosts can't use lifesteal anymore, even off of physical components of their damage. However, Death's
Dance functions properly on a ghost (as in, will heal them off of the physical damage they deal).

Consequences: This makes your squishy ghosts squishier, and prevents many solo Nash possibilities. An
ADC's ghost is supposedly a very powerful weapon, but it not being able to lifesteal makes it way easier to
take down in fights (and when ghosts tend to be less focussed than their living counterparts, so lifesteal
was even more valuable). And when it comes to the solo Nashes, since you want your ghost to tank all of
the damage at the beginning, not having this lifesteal anymore makes the task a lot harder.

Reproduction information: Nothing interesting, get the ghost of a champion with lifesteal, have it take
damage than attack a unit, watch as it doesn't get any health back despite being expected to, 100%
reproduction rate.

Example: Video: The ghost has a botrk but doesn't gain any health back from its attacks.

7) Mordekaiser's opponents can see the drake glitching. Staying still when it moves, apparently. It happened
numerous times, but I couldn't get a video because I am rarely on the far side of the mace and because this
doesn't affect the spectate client.

Consequences: It's disturbing for the team facing Mordekaiser, and I don't think they can react to the
dragon's movements as fast as they would have without the bug, if the animations are bugged.

Reproduction information: You've gotta face a Mordekaiser for that, then I don't know what triggers the bug.
I can't even say whether it's rare or common, but it has started appaearing just a few months ago.

8) Ghosts cannot use the passive of their support items anymore. The passive just isn't here. Three cases:
I) Relic Shield line: No blue orbs around the ghost, so nothing happens when it attacks minions.
II) Ancient Coin line: No mana or gold coins pop up, regardless of whoever killed the minions.
III) Spellthief line: The ghost doesn't get the bonus damage or the gold upon hitting enemies.

Consequences: Prior to the occurrence of this bug (so, when ghosts could still make use of their Relic
Shield) was another one, that would make it so that they would not lose the Relic Shield stacks upon using
them, meaning that you could get 26 CS out of two waves of minions, by executing all of them with the
ghost. Obviously, that was also a bug, and it probably isn't fixed yet. Its reproduction conditions just got
wiped away.
But this bug put aside, here's what the 5.8 issue takes away from you. For every ghost having one of these
items, you lose on average (depending on the level of the item):
I) 120 - 140 gold (4 to 5 stacks, two on cannons and two-three on melee minions) as well as some pushing
II) 120 - 160 gold (4 coins, including two from cannons).
III) 48 - 90 gold (6 stacks), as well as 60 - 90 premitigation damage to champions or turrets.
Of course, this is all supposing the 3.9 bug to be fixed (the one that prevents you from gaining the ghost's
gold). But were those two bugs corrected, you'd get an additional 50% gold on killing a support with your ult.

Reproduction information: Get the ghost of any champion with one of those three items. 100% reproduction

Example: III) Video

9) Attempting to get a champion ghost to attack a unit near a turret will cause it to attack the turret instead.
It doesn't really affect the drake ghosts because they're way too buggy for that to be noticeable anyway.

Consequences: Another issue, adding to the others, that makes ghosts harder to use and manipulate
efficiently. Like, don't expect to pull of the sick 420 mlg mechanical outplay by your ghost (involving insane
orbwalking and eye-popping jukes) when it's that hard to control.
More accurately, this is mostly about hitting minions under the enemy turret, and more rarely champions (it
matters less, because when you attempt to hit a champion, you can afford to click a bit further away from
the turret, whereas for a minion, when you do that, you might hit another minion instead, while you were
aiming for a last-hit).
So that's another thing that makes you miss last-hits, and sometimes (rarely) kills.

Reproduction information: Grab a ghost, go near an enemy turret while there are enemy minions around it,
and try using your ghost to attack a minion just under the turret. Expected result: The ghost will attack the
minion. Observed result: The ghost will attack the turret. Reproduction rate of 100% so long as you click
close enough to the turret (the ghost just prioritizes the turret, and then the bug 2.4 applies, I think). 100%
reproduction rate.

10) If you have a ghost, champion or dragon, and tell it to attack an enemy inhibitor by using alt-click, it
works fine. If, however, you use R instead, the ghost will either refuse to move, or go in melee range before
attacking the inhibitor, or even go in melee range without doing anything. If you press R on the inhibitor while
having the ghost in melee range of it, it works fine. The same bug happens on the Nexus, but everything is
fine against turrets. (crosses fingers)

Consequences: This is an issue for those who aren't aware of how the bug exactly works, because you
might think that the ghosts cannot attack inhibs/Nexuses, and you might not know how to get the ghosts to
attack those structures. Needless to say that since they are supposed to add a lot to your pushing power,
especially when it comes to dragon or ADC ghosts.

Reproduction information: That's gonna look similar to the previous bug: Grab a (ranged) ghost, press R on
an inhibitor or Nexus to tell it to attack this structure, and watch what will happen. It can be various things,
but the ghost will not go and attack the structure from its max range.

11) The passive of Varus's ghost doesn't work. You could argue that it's because the ghost doesn't actually
kill things by himself since the kill credit is given to Mordekaiser... but a Tristana ghost can use the passive
of her E without any problem.

Consequences: That's already a small inconvenience when you're using the ghost to push a turret, because
you would benefit from the passive used on minions in that case. But it's even worse in teamfights, where
the ghost isn't going to get its huge boost of attack speed for killing champions, which severely reduces
your damage potential. Of course, all of this requires to have a Varus's ghost, which doesn't happen in every
game. But now... let's look back and write a summary of how much these bugs add up, just to Varus's case.
So the ghost doesn't benefit from:
- Varus's passive
- Blade of the ruined king
- Guinsoo's Rageblade
- Runaan's Hurricane
- Fervor of Battle
- The stats from his runes and masteries
- Lifesteal
Doesn't that start mattering a little bit? And we're talking about an ADC without Statikk/RFC, so it avoids
some other things there.

Reproduction information: Get the ghost of a Varus, try to get it to kill minions or champions (without an
emphasis on the "try", it shouldn't be that hard). The ghost is expected to gain some attack speed, but it will
not get any. Reproduction rate of 100%.

12) Ghosts don't have the Dragonslayer stacks that Mordekaiser and his team have.
Note 1: Shaco's clone has those Dragonslayer stacks.
Note 2: The note 1 might be outdated thus wrong, but there has been one moment when this bug and the
note 1 were true simultaneously.

Consequences: Five types of drakes, two categories!

I) Ghosts don't get the bonus AD (thus damage) and AP (thus AP for you) granted by the Infernals, don't get
the speed of the Clouds, don't get the objective damage of the Mountains, and don't get the regeneration
of the Oceans (that's ranked by priority order).
II) If you have an Elder buff, the ghosts will not use it. Not only won't they have it, visually or factually, but
they won't use yours either. You have an Elder buff meaning that all instances of damage that you deal are
going to apply a DoT on your opponents, the ghosts' damage are a part of your damage (and can heal you
through your own Gunblade), but the ghosts' damage are not going to apply that DoT despite the fact that
they should being pretty clearly highlighted by the way I worded this sentence.

Reproduction information: Get Dragonslayer buffs and a drake, and you can then check:
- The ghost's buff list (no Dragonslayer icon anywhere),
- The ghost's visuals (no small fire / pale trail / watery effects / I don't know the visuals for the Mountains /
big fire),
- The effects on the ghosts.
All of them will be missing with a 100% reproduction rate.

Examples: Video / Later in the same video / Even later in this video.
The rest of that video is for two other bugs, the 4.5.3 and 9.9.

Tier 6 - Some of the bugs there can still ruin your game! They're just rare.

1) The sound effects of the second cast of Mordekaiser's W can be heard through fog of war, if the enemy
Mordekaiser is in the fog that's in your screen. Yes, I get that a juggernauty metal suit shouting things while
making metal crash on the ground is noisy and that it could be realistic, but go tell that to Super Galaxy
Rumble first, and then we can talk, okay?

Consequences: I spotted a Mordekaiser doing Herald thanks to this while not having vision of him. I stopped
him because of this, while I wouldn't have known otherwise. So, this was one example, but theoretically,
anyone aware of that bug could be able to:
- Spot any dragon or Herald attempt,
- Spot a Nashor attempt,
- Track the path of a jungle Mordekaiser.
Granted that the last one isn't entirely certain, because I don't know if that requires the W to not be self-
cast or not. But anyway, if someone decides to exploit this bug, they can do wonders with him. Well, not
wonders for Mordekaiser, I'll let you imagine.

Reproduction information: Have an enemy Mordekaiser use his W in the fog of war, and put your screen
where the Mordekaiser is, still without having vision on him. Now there are three guesses that I can make,
without any certainty of them being true. Just three potential and completely uncertain conditions that my
example cannot deny:
- Mordekaiser might need to be bound to an ally and to have both circles connect,
- Mordekaiser might need to be damaging an enemy with his W,
- This bug isn't guaranteed to have a 100% reproduction rate.

2) Mordekaiser's E can be delayed by a full second without a reason. I only got that once and it was quite
weird, but I know that my ping didn't change the slightest. What happened was: I cast my E, while having my
W on, keep walking up to the target I was aiming for, hit him once, and finally my E goes off. I only pressed E
once and my other keys were pressed after it. The delay was about one second, if not more.

Consequences: Two possibilities:

I) Make you miss last-hits because of the E ending up being cast after the minion's/minions' death.
II) Make you lose a fight. And by lose, I don't mean just coming out on the losing end of a trade, but dying
instead of killing your enemy.

Reproduction information: I do not know at all. I've only had that bug happen once (even though I am really
sure of that I saw), and I suppose that I would have noticed it if it occurred another time too. I don't have
any footage of this, and cannot give any further information as to how it's reproduced or if it involves any
special circumstances. Just remember that I had my W on while this happened. Oh, I don't say that this
played a role into it, I just say that this is a possibility that isn't to be overlooked or forgotten.

3) If an ulted target dies by the fountain turret, it will not generate a ghost.

Consequences: It shouldn't matter much because, well, it involves killing someone on your fountain, so the
game has a high chance of having been decided already by then. However, this bug has a 100% reproduction
rate, while even a 20% reproduction rate would have made that jump to tier 1 if it didn't thankfully have that
condition of the target having to die from the fountain.
To sum this up, this is a bug that makes your chances of coming back from a grim-looking situation dwindle

Reproduction information: Ult someone, then have him die by the fountain's obelisk. Expected result: The
champion generates a ghost upon dying, observed result: the champion does not generate a ghost upon
dying (that's a boring sentence). This has a 100% reproduction rate (I might have already said it just a few
lines before).
Note: I wrote "by the fountain", not "on the fountain". If you kill it by yourself inbetween two obelisk's ticks
of damage, you should get the ghost.

4) There's an issue with the drake generating less shield than it should.

Consequences: Honestly, this is just going in tier 6 because I'm used to it being that way, but it might
deserve being higher. This makes you less tankier, not by a lot, but still a handful of hitpoints after every
attack of the drake.

Reproduction information: Get a dragon ghost, attack things with the pet, watch your shield before and
after, and do some math.

Example: Screenshots and math

5) A ghost drake's attack cancels if the target moves too far from the pet. The drake is made so that its
attacks cannot be cancelled, and so works the ghost.

Consequences: This makes you lose an attack from the drake, in spite of it being very valuable. The drake
has a low attack frequency (0,5 AS) but all of his attacks hit a lot (and massively refill your shield), so all of
them count.

Reproduction information: Have the drake channel an attack on an enemy that's running away from it, and if
it's going far enough, the attack will be cancelled.

6) The drake doesn't do the damage it should do. More, less, I don't know, but I've tried many another way
to calculate, and anyway, something's off. I even tried counting the Nashor's Tooth passive being added to
the Drake's attacks.

Consequences: I don't know! Since I don't know how that damage is calculated, I don't know how far off it
is from the reality. And this isn't even caused by the amplified damage of the drake against targets with
Dragon Slayer stacks, as I've also tried counting against enemies without any dragon buff. And I counted the
damage that's based on a percentage of the current health of the target.

Reproduction information: Uh, simply attack something with the drake and watch how much it does. Then
get lost in the math.

7) Ghosts can apply on-hit effects to turrets (or at least some of them, for example the damage from
Recurve Bow).

Consequences: Slightly increases the damage of some ghosts against the turrets. It's positive for
Mordekaiser, yay!

Reproduction information: Take a champion ghost with a Recurve Bow, have it attack a turret. This item is
the best for reproduction purposes, because it deals physical damage when the rest of the attack issued by
the ghost is magic, so the effect is pretty easy to notice.
Now, however, I'm not sure of which on-hit effects work and which don't. I know for sure that some don't
(for example, a Jax's ghost will not deal the bonus damage granted by its R passive on turrets... even though
I'll go back on that later).
This has a 100% reproduction rate for the effects it affects.

8) Champions that have forms will always have their ghost use one certain form. Which means that:
I) Udyr's ghost will always be in Bear stance.
II) Jayce's ghost will always use his hammer.
III) Jinx's ghost will always use her minigun.
IV) Elise's ghost will always use the human form. Also, after giving Mordekaiser her ghost, Elise will respawn
in human form.
V) Nidalee's ghost will also always use the human form.

Consequences: Positive in some cases and situations, negative for others.

I) Maybe that stance is the most useful, for a ghost, so that's a plus side in many situations: you get a stun
bot with lots of tankiness, meaning that it also decently increases your own health pool. However, this is
mainly positive, but can will come in as a downside in some rare situations, when you'd instead want the
burst of the Tiger stance right after getting the ghost, or the DPS of the Phoenix stance. The Turtle one,
however, seems pretty useless.
So don't get me wrong, in nearly every situation, this is a plus, or at least something neither good nor bad.
II) Now this one is negative. That ghost doesn't have anything to gain in being melee, considering that it
cannot use abilities, so you just trade a ranged character for a melee one without any compensation.
III) I guess it's even here. Sometimes good, sometimes bad, since both weapons are useful. Potentially
slightly more of a plus side, but just slightly. Things would be different if she could use her Runaan's, though.
IV) This one is bad. Being AP, Elise doesn't do much damage with her basic attacks, so she would be much
more efficient as a spider, dealing bonus magic damage, and having spiders alongside her. You lose about
three quarters of the damage that this ghost would have had without this bug (would have had every time
she'd die in spider form while being ulted).
V) And this one doesn't really matter. It's slightly better that way, but she deals little damage anyway. Unless
she's AD, but I haven't seen anyone but Erick do that, and I don't play on the same server or level as him.

Reproduction information: For every single of them: Try to get the ghost of all five of these champions by
killing them on all of their stances/forms/weapons, and you'll see that their ghost will always only use the
aforementioned "form".

9) If a champion has a stacking mechanic, the ghost will lose all of the stats. [Those bugs would all belong in
different tiers, and only two of them should be here. The deserved tier is written before the bug description.]
This means that:
I) Tier 6: A Bard ghost can't use his meeps. Video
II) Tier 6: The ghost of a Veigar loses the AP from the passive.
III) Tier 7: (would have been 6 before the small rework) Kindred's ghost doesn't have any Hunt stacks.
However, they can mark camps... and killing them doesn't give a stack.
IV) Tier 7: Thresh's ghost loses the souls of the "living" champion (quotation marks because... well... he isn't
that much alive to begin with. What does using the revenant of an undead resemble?).
V) Tier 7: Zed's ghost doesn't have the AD granted by the ultimate's passive.
VI) Tier 9: Sion's ghost loses the stacks on his W.
VII) Tier 9: Ghosts lose their Jaurim's Fist stacks.
VIII) Tier 12: Ghosts lose the Tear stacks.
IX) Tier 12: Nasus's ghost doesn't have any Q stacks.

I) You all know, or should know, that Bard can hurt a lot through his basic attacks, because of how much his
meeps empower them. He gets bonus damage, AoE damage, slow, AoE slow, bonus damage and more
bonus damage... Here again, I would say that this bug cuts down one half to three quarters of the damage of
the ghost.
II) It could seem useless, but not at all! Here, it's not about the damage the ghost will deal. It's about how
much AP you'll have. For the entire duration of the Child of the Grave, you gain 30% of the AP of the ghost.
Considering that a Veigar can get up to 250 bonus AP when not more, and that 250 can be further amplified
by 35% thanks to a Deathcap, that's already 100 AP that Mordekaiser loses access to. It is huge.
Those two bugs are obviously only here and not above because they only apply when the condition is met,
which is getting the ghost of one of those champions, so that really won't happen every game, but rather
once every... let's say 15 games for Bard and 40 for Veigar.
III) This means that Kindred doesn't get her bonus range. Nothing else, the rest goes on her abilities. It was
way more important before her last big set of changes, when the loss was actually a damn high amount of
on-hit damage.
IV) This case is similar to Veigar's! Except that the AP lost is lower. However, that also makes Thresh very
squishy, as he doesn't get any armor per level and only relies on what he builds and what he gains from the
souls. Being deprived of having the latter and not having much of the former due to being a support and not
a bulky tank, this ghost isn't the best at soaking damage. But the primary loss in this is the AP from the
V) The ghost will deal less damage. Not that much, but still a fair amount. And well, the exact amount will
obviously depend on what the Zed had killed.
VI) Less health on the ghost means that it dies quicker, but also, and especially, that you gain fewer
hitpoints for enslaving it. A Sion with 300 CS will have 600 more hitpoints than his ghost, and thus the ghost
will give you 150 fewer HP than it should.
VII) Same as Sion's case, but it doesn't matter as much, because:
a/ Nobody keeps this item that long,
b/ I even think that this item isn't fully stacked for a majority of the time when it's held,
c/ The amount of HP lost isn't even high - 150 at most for the ghost, which means 38 for you. Again, at
VIII) None. Ghosts don't use mana.
IX) None. Ghosts don't use active abilities.
You could argue that it's normal for the ghosts to lose the stacks that their living brethren had, because it's
not fair for them to have what they worked for turn against them. And if you do, your point is straight up
invalid, because that's the principle of that ultimate, and every level you gain and every item you buy turns
against you anyway.

Reproduction information: None, just grab those ghosts and watch as their stats will be lower, depending on
the case. 100% reproduction rate.

10) If Mordekaiser has a high attack speed, his Q will go on a lower speed than his normal attacks.

Consequences: Mostly none because you don't have a high attack speed. But sometimes you do. I've build
Nashor's Tooth and Guinsoo's Rageblade more often than you'd think, and Triforce is also a good item for
the Kaiser. So when you happen to reach that breakpoint, your Qs will go off slower than they should, and
this has a wide range of possible consequences: as always, it can make you miss minions, but the most
likely things are that it can make you lose a fight because of the reduction in DPS that ensues, or that it can
allow an enemy to escape when they wouldn't have otherwise been able to.

Reproduction information: Pack lots of attack speed (by the way, did you know that Mordekaiser doesn't
reach 2,5 AS with six Phantom Dancers?), and compare the speed of your attacks and the speed of your Qs.
Or just count how many Qs you can get per second, or in ten seconds (without CDs, of course). 100%
reproduction rate.

Example: Video

11) Graves' ghost is insanely hard to use. I don't know why, but it has a higher fail rate than the dragon ghost
and that goes to say a lot. If that would be on every champion instead of just Graves, it would be tier 1, and
this bug only falls five tiers below because it will only matter if you can get the ghost of one specific

Consequences: Saying that this makes this ghost hardly useful at all is not even a real exaggeration. It
screws over this ghost badly. The ghost can:
- Attack minions when you tell it to attack a turret,
- Attack minions when you tell it to move (while clicking away from the minions, I should know how to work
around Mordekaiser's other bugs - refers to 2.4),
- Not attack instantly sometimes in spite of its basic attack being up and ready to use (and the enemies fully
in range),
And that's not even really all of it but you get the point: this ghost will hardly ever listen to what you tell it to
do. Attacking instead of moving, or the other way around, attacking something else than what you wanted,
not attacking... For the ghost of something that hurts with its basic attacks and whose sole goal is to use
those basic attacks (since you don't get a Graves' ghost for the stats it gives you - Graves isn't known for
building tons of health or AP), that's a real shame!

Reproduction information: Get the ghost of a Graves and just try to use it. Watch what happens and
compare it with what you wanted. Reproduction rate of about 70% per command issued.

Tier 7 - Just like the tier 6, we are still in a category where if the conditions are met, the bugs here can be a
big inconvenience.

1) Kha'Zix's ghost doesn't keep the evolutions, thus losing the ability to become stealthed in bushes.

Consequences: It almost just matters for the R upgrade, so not so much because Kha doesn't always
evolve that spell (The loss of range due to not having the evolved Q doesn't really hurt you that much). But
the difference between having and not having that passive is that you cannot make your Kha sneak from a
bush onto someone with your W on him, nor can you refresh the passive of the ghost for entering bushes
the enemy has vision of (the stealth would remove their vision on Kha's ghost, thus granting it its passive

Reproduction information: Get the ghost of a Kha'Zix with Q and R evolved, and watch as the ghost gets
neither the bonus range nor the passive Void Assault in bushes.

2) Jhin's ghost doesn't have the passive from the Captive Audience.

Consequences: Situational. It'd matter in skirmishes or teamfights, involving at least three enemies (Jhin,
one person for Jhin to kill to trigger the passive, and one last person to be affected by it). These explosive
flowers can snowball the fight in your favor, by slowing the enemies and forcing them to focus on moving out
of the explosion's way, or to take a serious amount of damage. So that bug can lose Mordekaiser
teamfights, when he gets the ghost of a Jhin.

Reproduction information: Get the ghost of a Jhin, have it kill an enemy champion. It's expected to spawn a
flower on the enemy's corpse, but will not do anything. Reproduction rate of 100%.

Example: Video

3) If Mordekaiser attempts to ult Elise the moment she turns back into human form, the ultimate's
animation and sound effect will play, but the spell won't be cast.

Consequences: Can make you lose a kill when you're trying to chase an Elise. The ultimate has a pretty long
cast, during which you cannot move, so this gives Elise a decent amount of time to get out of the range. All
of this considering that the Children of the Grave is Mordekaiser's way to apply the Rylai's slow from the
longest distance.

Reproduction information: Use your R on an Elise, and have that Elise transform from spider to human form
a tenth of a second later. Reproduction rate of 100%.

4) A drake ghost's attack won't deal any damage if you level up ult while the attack casts.

Consequences: That's generally not much of a problem since the conditions are pretty specific, and you
also won't have any trouble avoiding that bug if you're aware of it. But if you aren't (well... like me when I
found out about it), you may lose one drake attack, and that means a lot (as I've already said, on champions
or turrets, every drake attack matters).
That bug will not happen frequently, fortunately, due to its condition.

Reproduction information: Get to level 11 or 16, don't use your skill point, get the ghost of the drake, have it
attack something, put a point in your ult while the attack is flying. Reproduction rate of 100%.

5) The damage dealt by a ghost's Tiamat doesn't generate any shield for Mordekaiser.

Consequences: That's pretty obvious, you'll have less shield while you have one of those ghosts. In terms of
numbers... so long as you're fighting inside an enemy minion wave, your ghost's Tiamat should give you 22%
of its AD as a shield for every of its attacks, considering that the Tiamat hits three minions in melee range
and two from further. So if you've just killed a 200 AD Fiora and are trying to take down her jungler right
after, for every of the ghost's attacks (or, let's say, its first five attacks because the minions will die from
your and its AoEs), you'll lose 44 hp (as in, will not save 44 hp).
Now if you're in the middle of a teamfight, that's probably gonna be a higher loss, because the shield
generation is halved against minions. So that bug doesn't so rarely matter after all.

Reproduction information: Get the ghost of a champion with Tiamat, have it attack a minion in the middle of
a minion wave. You'll get 12,5% of its AD as a shield, instead of 12,5% + 2,1 to 6,3% per minion around.
Reproduction rate of 100%.

6) Kalista's ghost can't dash, regardless of how I try to do the command. All the other parts of the passive
work fine - those that have negative effects on her.

Consequences: That would mostly be useful in order to catch up to people. Sure, you could also use it
during a teamfight, but if you focus on making your ghost jump around, you might kinda get distracted from
your own champion. So that bug actually mainly just prevents you from chasing people by either dashing
while attacking the champion you chase, or using minions as a way to gap close towards them.

Reproduction information: Get the ghost of a Kalista, try all of the buttons or combinations of buttons that
could make a ghost of Kalista dash, but nothing will happen. This also has a 100% reproduction rate.

7) Tryndamere's ghost can stack Fury, but he does not seem to be able to crit off of that fury. Either that, or I
am really, really unlucky, but since it happened two days before Critmas, I’ll go with the first option.

Consequences: Pretty straight-forward here again, the ghost loses some of its damage. Let's give some
math: After the fury bar is charged, the ghost would deal an average of 21% to 35% more damage (21% at
65% crit chance, 35% at 0% crit chance). Considering that a Tryndamere ghost is all about bringing you a
huge DPS if you manage to snag this Pokémon (since his ult is a pretty big counter to yours, as you can't
use yours for both the highest shot at getting the ghost and the highest damage), when that DPS gets
reduced that much, it kinda defeats its purpose.
And once again, I have to point out the fact that this... reduces the shield you are going to generate through
your ghost (what, have I already said something similar before? Naah).

Reproduction information: Get the ghost of a Tryndamere with 65% critical chance, have it go up to 100 fury,
and watch as the ghost will not always crit in spite of its theoretical 100% crit chance. Reproduction rate of
100%, unlike the actual crit chance.

8) Teemo's won't turn invisible, nor will it gain the attack speed boost. Even if both Teemo and Mordekaiser
stand still without being damaged.

Consequences: The stealth part isn't that important, it's mostly about the fact that it makes the ghost lose
access to the attack speed passive. Even though that doesn't matter as much as if Teemo's ghost weren't
bugged on another aspect already and would have access to its poison, but it still loses access to a pretty
sweet buff that gives him up to 80% bonus attack speed.

Reproduction information: Get the ghost of a Teemo, stay immobile for as long as you want, try to put the
Teemo ghost in a bush if you want, it'll never turn invisible. Reproduction rate of 100%.

9) Lulu's ghost comes without Pix. Don't tell me it's because you only take one soul, Sejuani is still on her
pig, and Nunu comes with Willump. And by the way, why do you get both their souls? Okay, the ability is
called Children of the grave, but the ghost is called Child of the grave. Anyway, Lulu's ghost doesn't have a

Consequences: Same as with the bug 4.3. You lose the damage of the passive for every attack of Lulu,
which can easily go up to 120 to 200 damage per hit, making the ghost lose more than half of its damage
(And it still feels like Lulu doesn't like Mordekaiser).

Reproduction information: Get a Lulu's ghost, have it attack something, watch as Pix won't attack. And even
beforehand, as soon as you get the ghost, you'll see that Pix won't even be there to begin with, which
arguably makes it hard for it to attack. 100% reproduction rate.

Example: Screenshot not even with Lightshot

10) Mordekaiser's ghosts don't apply stacks of Braum's Concussive Blows.

Consequences: Usually doesn't matter, even though it matters more in Twisted Treeline, once again due to
how often Braum is played (as a duo laner, like Mordekaiser). Because of this bug, you'll have the Braum's
stuns delayed after you get a ghost (in comparison with when they should have come), and that can (rarely)
get a fight turned around. However, there's one point in particular that can matter: when you have the ghost
of a ranged champ, Braum Qs an enemy and you cannot get in melee range of that enemy. Your ghost
should be able to add the missing three Concussive Blows stacks, to stun the target even if you cannot get
in range for it yourself, thus to eventually allow you to get in range.

Reproduction information: Get a ghost while you have a Braum in your team, have Braum attack something,
have the ghost attack said thing, and the something will not gain further Concussive Blows stacks, despite
being expected to. Reproduction rate of 100%.

11) Kog'Maw's ghost has more attack speed than the normal Kog... even when the latter has one more
point in Q. This is perhaps due to the ghost counting too many points in Q.

Consequences: I don't know much about that bug, so I could be wrong here, but from what I've seen, the
effect is basically to give Kog'Maw something like the bonus AS from the rank 5 of his Q even if this rank
wasn't reached. If so, then the impact is rather small, as it will be a 20 to 0% AS boost (scaling down with
Kog's points in Q).

Reproduction information: Get the ghost of a Kog'Maw early on, and see that his attack speed is higher than
that of its living brethren. Now try again with a Kog'Maw with five points in Q, maybe the problem won't be
there anymore. It's just a guess, even though this time it's more likely to be true than the last suppositions.
So far, that bug has always applied so long as the Kog'Maw only had one rank in his Q.

Example: Normal Kog'Maw / Ghost Kog'Maw

12) Nocturne's ghost has a higher attack speed than the normal Nocturne. Same explanation as for
Kog'maw. (Note: There was no problem with the old Rek'sai)

Consequences: Again, if that bug works the way I think, that will not do anything past the fifth rank of
Nocturne's W. Anyway, it's a small positive bug for Mordekaiser, giving the ghost slightly more AS.

Reproduction information: Same as the 7.11, replacing Q with W, including the part about the reproduction
rate of the bug.

Examples: Screenshot

13) If Mordekaiser has a Titanic Hydra, if he Qs and flashes during the cast of his Q, the animation of the
Titanic Hydra will be moved, but its damage will neither be dealt in the pre-flash corner, nor in the post-flash
one (so it won't deal any damage, save for the one on the target of the Q).

Consequences: This doesn't really have any consequences because that bug has to bypass another bug to
occur, as well as meeting three other conditions. So here are the four final conditions:
I) Mordekaiser must have a Titanic Hydra, which, as I said earlier, is unlikely as a consequence of the bugs
3.5 and 3.6.
II) Mordekaiser must want to flash his Q for some reason.
III) There must be other enemies around, otherwise you don't care about the Hydra not hitting anyone.
IV) Mordekaiser must not trigger the bug 3.6, as this bug would negate the effect from the Hydra.
If all of these consequences are met, then Mordekaiser loses some AoE damage. Yes, that's very little. This
bug should go further down... except that if the bugs 3.5 and 3.6 were fixed, it would go up instead. So it'll
go here.

Reproduction information: Find any kind of target with other allies around, Q it while you have a Titanic
Hydra, flash during your Q, and watch as nothing gets damaged around. Reproduction rate of 100%.

Example: Video

14) Zilean's ghost doesn't have his passive.

Consequences: That depends on the level of the Zilean, there, thus on whether he's gone support or mid. It
mostly shouldn't have that much impact, given that after a minute, a level 11 Zilean only stores 60
experience in his passive. However, if you manage to get the ghost of a level 18 Zilean (so, assuming he's a
mid laner, I don't think you should have many people below this level if their support is already maxed out on
experience), it goes up to 144 after 60 seconds. It's not much, but it can still matter.

Reproduction information: Get the ghost of a Zilean, and you won't be able to use its passive. Reproduction
rate of 100%.

Tier 8 - Mostly ghost bugs that have little impact and in rare situations. They can still deny cause
Mordekaiser's team to lose a buff, or his ghost to deal 20% reduced damage.

1) Zac's passive doesn't cleanse him off of the Children of the Grave. However, Zac takes no damage from it
while in passive form, despite being intended to lose a part of his health every second.

Consequences: As I wrote, the ultimate is supposed to be damaging Zac so long as this spell and Zac's
passive are both ongoing. But instead, while using the passive, Zac is completely protected from it, meaning
that Mordekaiser may miss kills or even lose fights because of it. It not only lowers the damage that Zac will
suffer, but it will also affect Mordekaiser's tankiness a lot. Every second, the ultimate drains a portion of the
enemy's full health. He heals for 100% of the damage dealt and shields himself for an additional 25% of it.
And considering that Zac tends to have a lot of hitpoints, this does mean a lot.

Reproduction information: Ult a Zac with his passive up, make him use his passive while your ult is still up.
As his passive gets activated, he is expected to keep losing a portion of his maximum health every second,
but will not lose it. Reproduction rate of 100%.

2) If a ranged ghost throws a basic attack and dies during its travel time, the attack will deal physical
damage, thus reducing the damage it will deal because you are pretty likely to have more magic pen than
armor pen.

Consequences: That only affects one attack, so it's not much. It'll just reduce the damage of this attack by
40% on a 120 armor/MR target if you have Void Staff, Liandry's and Sorcerer's Shoes, or 27% on a target
with 42 armor/MR target. For an ADC dealing 600 damage, that's a difference of 240/162 damage.
But just for one attack.

Reproduction information: Find a ranged ghost, throw a ranged attack at it to take it down, and have the
ghost cast its own attack while the opposite one is flying to it. Reproduction rate of 100%, if I'm not

3) If a ghost has a Raptor Cloak (or Talisman of Ascension / Ohmwrecker / ZZ'Rot Portal), they will constantly
get the movement speed bonus, not only near turrets.

Consequences: Very slight. It's something positive for you, makes your ghost faster, but will only matter if it
can get to catch someone thanks to it (and then to apply Rylai's slow with its attacks), but the 20% boost is
rarely enough. Still something positive though!

Reproduction information: Nothing to say, I don't even think it's because Mordekaiser is considered as a
turret for them (well why would he, after all), because the ghosts can be further to him than the Point Runner
passive should allow them, without losing the speed.

4) The attacks of Graves' ghost will do both physical and magic damage, to minions, champions, monsters
or turrets. The first pellet hit on any unit will apply its normal magic damage, but every other besides this will
deal physical damage. Also, the ghost has a cigar.

Consequences: It means that this ghost will deal less damage than it should, because of your own magic
penetration. Every of its attacks. When Graves attacks from close range, it's more or less of a 50-50 split.
So you just have to halve the calculations in 8.2, and you get a 20% and 14% damage loss, in those cases.

Reproduction information: Get the ghost of a Graves, have it attack something... I guess it's not hard to

Example: (Screenshot)[]

5) Putting at once three bugs with Ivern's ghost (all on the passive):
I) Ivern's ghost can use his passive. However, he will use it through clicking, not alt-clicking.
II) When Ivern's ghost frees a blue/red buff, Mordekaiser can pick up both the normal buff and the buff
granted by Ivern's "crystal" left on the ground.
III) (?) Smiting something marked by Ivern's passive will do a normal smite instead of fully freeing the

I) That is just weird and totally not the way this should be. All normal click actions are meant to be
Mordekaiser's, and alt-clicks ghosts'. The main consequence of this is that if you are not aware of how the
bug makes this work, you are either not going to manage to use the ghost's passive, or will waste quite
some time experimenting during your game before you can finally get it right. It also means that in order to
mark a camp, you also have to attack it as Mordekaiser, since your right click inputs two different orders at
once. And it also means that right-clicking anywhere else will both make you stop attacking as the Kaiser and
cancel the channel of the ghost's passive.
II) Both buffs are most likely to go to Mordekaiser in every case, due to him being melee and picking the
crystal before he gets enough time to leave the range. Except if there was someone else there. So that
makes you miss a buff every time you get one thanks to the passive of Ivern's ghost.
III) Disclaimer: I am not sure whether this is a bug or not! It would probably rather fit in the Special Tier 1, but
let's put everything about Ivern just here. I don't think that if Ivern has someone else in his team having a
Smite, the someone else can use the smite to activate Ivern's passive. I don't think it works like that and I
think it makes sense the way it currently works. However, in the case of a ghost, Mordekaiser is the one
owning Ivern, and works... together with Ivern, in a way. So this just prevents Ivern from using his passive to
its full extent.

Reproduction information: Take a smite on Mordekaiser for good measure, and get a ghost of Ivern.
I) Try using Ivern's passive in the way you feel is most logical considering that telling the ghost to click on
something is done with the alt + right click command. And try to press both alt + right click and simple right
click on the camp, and see that only the latter does something, as opposed to the former being expected to
be the one and only one working.
II) After you've done the step 1 on a buff and done it again in order to free the camp, just watch. You don't
have anything to do. You'll get the buff first for "killing" the monster by yourself (ghost's kill credit -> your kill
credit), then another time because of the crystal (instead of just picking up the buff once and leaving the
crystal for any of your teammates).
III) Use Ivern's passive on something then smite it and watch as the smite deals damage instead of
completing Ivern's passive.

Examples: Thanks to Vandiril for this!

I) Video
II) Same video with a suited timestamp
III) Same video with a suited timestamp v2

6) The damage on Mordekaiser's Q can come out later than the animation's completion.

Consequences: Little outside of niche cases where that extra time could allow an enemy to get a kill off. In
this case, I don't know if Mordekaiser's damage still goes through or not. If yes, it means that in the very
situation I've described, it turns a fight around for Mordekaiser's opponent, by literally stealing the kill the
Kaiser should have grabbed. If not, it means that he will be allowed to get a trade kill, while without the bug,
the Master of Metal would have received his kill credit and survived.

Reproduction information: No clue. Sorry. That bug seems very rare.

Example: Video: I actually got tricked into thinking that Altec's third Q did not deal any damage in this fight,
while what actually happened was that the damage came super late. You might wanna watch this in 0,25
speed, but here's what happened: Morde's Mace of Spade's animation went through without any damage
being dealt to Apollo (who still had heal up at this very moment), then LemonNation's basic attack went
through alongside its own damage, then Altec flashed, heal and took the Morgenstern's damage exactly at
the same time, not losing or gaining any hitpoints in the process.

7) The ghost of the drake, like the other ghosts, can't attack wards (I'm going back on this in Special Tier 1).
However, it can decide to attack a ward by itself if you attack it too.

Consequences: Little in terms of gameplay (it will just make the dragon waste one attack), but potentially
interesting about the code.

Reproduction information: I'm not entirely sure, but try attacking a ward while your dragon is nearby and
supposedly not told to do anything. In that way, the drake should try to attack the ward alongside you.
Reproduction rate unknown.
I'm just wondering what it matters in terms of code, and that's why this bug was important to mention: I
suppose that all ghosts and other kinds of "superior" pets are specifically coded to not be able to attack
entities that aren't champions, buildings, minions or monsters. What does it mean that a dragon ghost
actually has a way to attack those wards?
I have never seen this happen with a champion ghost.

Example: Video

8) Related to the previous one: The drake ghost has a way to cancel his attacks, as you could see if you
watched the video.

Consequences: Goes alongside the previous bug, but it also had to go in this category to have both of them
stay tied.

Reproduction information: Same as the previous bug.

I put that bug as a distinct bug from the previous one because of what it implies codewise. Here, it's not
about what ghosts and pets can do, but about what drakes can and can't do. Drakes cannot cancel their
attacks, yet it's the second case in which I've seen one do it (cf. 6.5). For this and for the 8.7, I'll let Riot
conclude about what it means.

Example: Same video

Tier 9 - Mostly ghost bugs that will slightly affect Mordekaiser, denying Mordekaiser up to 50 to 100 hp.

1) If a Braum ghost has 3 stacks on an enemy and kills the enemy with the 4th attack, if the damage of the
passive is enough to kill the unit alone, the base damage of his attack won't be applied (nor will the on-hit

Consequences: Little and that's a word I'll use a lot from this point on (that's kind of the point of those
tiers). It will simply mean that if Mordekaiser has a Gunblade, he will be healed less from this attack than he
should have if that bug hadn't been here. Also, he will gain less shield off of it. What do I mean by "less"
here? Something between 10-20 hitpoints (level 9 to 18 Braum) and 18-36 shield, estimating some damage
reduction from resistances. This adds up to a best total of an additional 28 mitigated damage if Braum is
level 9, and 56 if Braum's level 18. I can't believe I just wrote 6 lines about this bug.

Reproduction information: Get the ghost of a Braum, have it stack 3 Concussive Blows on a target and
simultaneously put that target around 20 hp, then land one final basic attack on the ghost. Watch as no
bonus damage will be taken from Braum's passive, unlike what was expected. Reproduction rate of 100%.

2) Aatrox's W gives additional physical damage. The Blood Price of Aatrox's ghost will instead give him
additional magic damage. Yet Jarvan's Martial Cadence and the Recurve Bow both add physical damage as
they're said to do, even for ghosts.

Consequences: I suppose it makes it so that for ghosts, Jarvan's and the Recurve Bow's passives will deal a
proportion of their intended damage that will be lower than the Blood Price of an Aatrox's ghost.

Reproduction information: Get the ghost of an Aatrox using Blood Price. Attack a minion three times. Get the
ghost of a Jarvan. Attack a minion. Get a ghost with a Recurve Bow. Attack a minion. Watch as only Aatrox's
attack will have its damage be fully magic. 100% reproduction rate.

3) When a Kassadin's ghost kills an enemy without needing the bonus damage from his W, he doesn't deal
that bonus damage (thus generates less shield for Mordekaiser). The normal Kassadin always deals this

Consequences: Exactly like 9.1, with a loss of 3 hp + 5 shield (100 AP Kassadin) to 10 hp + 18 shield (800
AP Kassadin). Not very big numbers.

Reproduction information: Get the ghost of a Kassadin (that has W unlocked), reduce a minion to single
digits of health, attack that minion with the ghost, watch as Kassadin won't deal as much damage as it
should have. Reproduction rate of 100%.

4) Twisted Fate's ghost has no passive. (E works fine.)

Consequences: None so long as the 3.9 bug exists and that prevents the ghost from sharing its money with
you. If that bug were to be fixed, then you'd lose 1-6g every time the ghost would slay a minion.

Reproduction information: Get a TF's ghost, kill minions with it, watch as nothing special happens.
Reproduction rate of 100%, and what a boring description.

5) Mordekaiser can't W a Wukong clone, while it's considered a champion for the purposes of targeting.

Consequences: Little, because in most situations you can still W the original version of Wukong anyway. But
sometimes, for some odd reason, you'd want to W the decoy (for example, if Wukong is 1010 units away
from you without any other ally - even minion - nearby, would he cast W, you'd catch up with the decoy and
be able to use your Harvesters of Sorrow on it to gain some movement speed). And I like the fact that I
chose for my example the least impactful case possible.

Reproduction information: Have a Wukong use his W, try to W his Decoy, it won't work. Reproduction rate of

Example: Video

6) However, Mordekaiser can use his W on... Jayce's Acceleration Gate. He can actually use his W on all the
things Gnar can bounce off (thanks to Vandiril for the second time). However, if he uses the W on the
Acceleration Gate, it will be invisible yet still deal damage.

Consequences: Inconsistency galore! There are some things that you should completely be able to W
according to logic (Wukong's decoy as mentioned, but also Maokai's saplings or Zed's shadows, I think - at
least not Syndra's balls and Jayce's gate and not those, for sure). It doesn't have that much impact since
it's rare not to have any other unit that you can W and that is in a good position for it (except that Syndra's
balls are a great way to use long-range Harvesters).
However, that Acceleration Gate thing is very confusing. I mean the fact that it just becomes invisible. I've
seen many people, even among Mordekaiser mains and Mordekaiser mains that are clever and know the
game, who ended up thinking that the Gate was negating your W (since it becomes invisible), without
noticing that it was still there and working, just invisible.

Reproduction information: As shown in the previous and future videos. Just W those things. Reproduction
rate of 100% for all of these.

Example: Video

7) Caitlyn's Headshot makes her interact very weirdly with the other bugs, that involve
I) If a Caitlyn ghost has a Statikk/RFC/Kircheis Shard, she will only be able to proc it by using her Headshot-
empowered attack. Her Headshot-empowered auto won't make her gains Energized stacks for an unstacked
Statikk/RFC/Kircheis Shard, though.
II) Once Caitlyn's ghost gets her first Headshot off, she then starts applying botrk's damage, as physical
damage, on every auto-attack.
I don't know how it works with Guinsoo's Rageblade. Perhaps the same, perhaps not.

Consequences: I don't even know how I should put the consequences. Negative if you consider how
Mordekaiser should work as a whole (aka with the fact that the ghost loses RFC/Statikk/Botrk procs),
positive if you compare that to how other ghosts work. So in the first point of view, you lose several
RFC/Statikk/Botrk procs, and in the second one, you gain some. That's about all I can comment on this.

Reproduction information: You can use the ghost of a Caitlyn with all of those items at once. Then you have
to try to:
I) Attack minions. The Botrk will only start doing anything on your first Headshot and on every attack that will
come after it.
II) Try to stack your Energized stacks. No matter what you do, it'll only work by moving.
III) Try to use those stacks. It'll only work on Headshots.
100% reproduction rate!

I) Video
II) Video

8) The ghost of a Jayce does not get any bonus from transforming his weapon from cannon to hammer upon
being turned into a ghost. He should:
I) Get a movespeed boost and become ghosted thanks to his passive.
II) Get additional damage thanks to his R.
Note: Udyr does get the movespeed from his E and stats from passive upon being turned into a ghost.

Consequences: Little again. You just lose a little bit of movement speed, but also one burst of damage (the
damage of Jayce's R). Which is not nothing, as 20/60/100/140 + 25% bonus AD can be quite a lot.

Reproduction information: Kill with your ultimate a Jayce that was using his cannon. The ghost will instead
use the hammer (cf 6.8.2), but will not get any of the bonuses obtained from switching forms. 100%
reproduction rate.

9) Jax's ghost does something weird with its R's passive on turrets. Instead of doing normal attack - normal
attack - R-attack - R-attack - R-attack - R-attack (and R-attack for every blow afterwards), it will do normal
attack - R-attack - R-attack - normal attack - R-attack - R-attack.
The video below will explain everything!

Consequences: Not that much. A normal Jax will always have access to an empowered attack on his next hit
after attacking a turret (if he had at least issued two hits on the turret), and this ghost will not. That's just it.

Reproduction information: Attack a turret with Jax's ghost and watch the pattern that unfolds. 100%
reproduction rate.

Example: Video with a supposedly clear explanation

10) The attacks of champion ghosts against inhibitors or Nexuses will deal physical damage to these
structures, instead of magic.

Consequences: I don't know. I don't know if that changes the amount of damage the ghost will deal to
these structures. If yes, it goes up to tier 8, if not, falls down to tier 11. And if it's uncertain, it'll stay there.

Reproduction information: Get the ghost of a champion, have it attack an inhibitor or Nexus (despite some
aforementioned bug). The damage it deals is expected to be magic, as is all of the damage of the ghosts'
basic attacks (which means the main damage of their attacks, disregarding all on-hit effects), but is
observed to be physical, with a reproduction rate of 100%.

Tier 10 - Mostly ghost bugs that affect the hitpoints of the ghost, or the damage they can take, without
directly affecting Mordekaiser. Or bugs that affect items that Mordekaiser will more than rarely buy.

1) A Cho'gath ghost doesn't have a passive.

Consequences: Prevents Cho'gath from regaining health upon killing minions.

Reproduction information: I may skip the reproduction thing from now on when it's really trivial. It is trivial,

2) The passive of Irelia's ghost gives her 10% tenacity even with no enemy around.

Consequences: Irelia has 10% bonus tenacity for Mordekaiser's 1v1s (as in, Mordekaiser and Irelia's ghost
against one champion).

3) If a ghost has a Banshee's Veil, the veil will only activate one or two seconds after the ghost is spawned,
regardless of the cooldown on the veil for the original champion.

Consequences: That's just pretty illogical. The Veil should activate as soon as you get the ghost... or at the
very list, 45 seconds later. Those two seconds can't have any rational reason (I mean, in the code, sure, but
that's not what I mean).

4) A Sivir ghost doesn't use her passive.

Consequences: Won't gain movement speed upon attacking champions, reduces the chase potential of the
ghost, hence Mordekaiser's chase potential. I think the kiting aspect of this passive can be ignored.

Example: Video

5) If Mordekaiser has a RFC fully charged, activates his Q and right-clicks an enemy minion, he will just use
the RFC (without casting the attack afterwards) and will cancel his attack order. This will be similar with the
bug 14.5, but the difference between those is in that attack being cancelled against the player’s will). This
bug doesn’t have a 100% reproduction rate.

Consequences: You shouldn't have a RFC to begin with. Consider that bug without consequences.

Reproduction information: Follow the description. Buy a RFC on Mordekaiser, stack it, activate your Q and
right-click on an enemy minion (or any kind of unit). Reproduction rate below 100%.
However, this bug is interesting because Mordekaiser's Q isn't meant to be cancellable, whereas this issue
may force a cancel of your attack after the RFC gets used.

6) If Mordekaiser has a Death's Dance and the ghost has any way to deal physical damage (Jarvan's passive,
Recurve Bow, for example), this physical damage won't heal Mordekaiser.

Consequences: Little to none. Although this item has a passive that could be really cool on Mordekaiser, the
other one is pretty useless. And the heal that this bug makes you miss isn't that high anyway.

Reproduction information: Use one of the cases I quoted as examples (Jarvan / Recurve Bow).

7) Malzahar's ghost doesn't have a passive. It doesn't activate, and isn't shown as being on cooldown

Consequences: Will make that ghost easier to kill, and will remove it its ability to block a CC. Considering
that ghosts are well used as meat shields against skillshots, that this one ghost is pretty squishy and that
you'd need it alive to keep some of its AP.

Example: Video

8) When the ghost of a Wukong activates his passive, he gains bonus armor and magic resist... and loses
base armor and magic resist.

Consequences: Little. The ghost only gets ever so slightly squishier.

Reproduction information: Put a Wukong ghost near enemies and check its armor and magic resist stats
before and after. By that, I mean the gray and yellow numbers in the detailed resistances stats.

9) Vayne's ghost doesn't have her movement speed passive (the Silver bolts work though).

Consequences: Same as Sivir's case in 10.4, except that it also reduces her chances at catching up with
someone, which is actually fairly important since she can apply your Rylai's effect for you.

Example: Video

10) Trundle's ghost doesn't have his passive.

Consequences: The ghost isn't as tanky as it should be (in terms of sustained tankiness).

11) Nidalee's ghost doesn't have her "On the Prowl" hidden passive, giving experience to lower-leveled allied
nearby champions.

Consequences: If her level is above yours, you should get 5 exp every 5 seconds (or was it 10?) while this
ghost is alive and near you. And so should your teammates if it's above theirs.

12) If a ghost has a black cleaver, their attacks will put cleave stacks on the enemy champions. If
Mordekaiser has a black cleaver, only his attacks will add a cleave stack on the enemy champions, his
ghost's won't (unless both have one). So far, everything's alright... or is it? If Aatrox and Mordekaiser both
have a black cleaver and if Aatrox's ghost attacks an enemy champion, his attacks will put one cleave stack
on him. Except the attack empowered with Blood Price (his W). With further tests, it appeared that if a
standard Aatrox attacked an enemy, his W-empowered attack would only put one stack on him, not two.
What does that mean? The ghost's empowered attack, despite dealing purely magical damage, put one
cleave stack for his cleaver, and one for Mordekaiser's cleaver. Kinda weird.

Consequences: None. You don't have a Black Cleaver.

Example: Video

13) I so badly want to put this bug higher up just for the sake of its description. You cannot E before you land
on the ground after a flashed Q on a plant followed by a QSS. W works fine, though.
I suppose this doesn't require any clarification.

Consequences: None. This situation will never happen. You need to:
a/ Have a QSS,
b/ Be in front of a blast cone,
c/ Have your flash up,
d/ Have your Q up,
e/ Think about doing the trick of attack-flashing the plant to gain some time,
f/ Know that you can only do this on Mordekaiser if the said attack is a Q,
g/ Have your QSS up,
h/ Be willing to use your QSS for this,
i/ Have your E up,
j/ Have an enemy that you need to hit with your E before landing on the ground.

Reproduction information: Just follow the instructions *malefic grind*.

Oh well.
a/ Walk in front of a blast cone,
b/ Q the blast cone,
c/ As soon as the Q start, press flash on the other side of the blast cone,
d/ QSS while in the air.
e/ Try pressing E.
It will only work when you land on the ground. If you tried to use your W instead of your E, it would have
Oh, and from what I recall, if you don't flash, it works fine. Also, don't ask me how I found this.

Example: Of course there's one, take this video.

I took an entire page to describe a completely useless bug.

Tier 11 - Now the bugs don't affect the gameplay anymore. They are just clarity issues.

1) Mordekaiser's Q lost its 1! / 2!! / 3!!! thing.

Consequences: Clarity. Harder to read which stack of Q you're at. It actually matters when it's not always so
clear whether one of your Qs was consumed by attacking a minion who died in the meantime (cf bug 4.8).

2) When Mordekaiser has a ghost, his ultimate icon often remains normal instead of being highlighted as it

Consequences: It makes you sometimes think that you can use your ultimate, while you still have a ghost
alive. Even if it sounds somewhat stupid, in practice, it can be confusing, and you can have that thought
during one or two seconds. Sure, you understand that it was only a bug after that period of 1-2 seconds. But
sometimes you've flashed into someone in the meantime, expecting to be able to ult them. And it was at
this moment that he knew... he fawked up.

Reproduction information: Reproduction rate below 100%. Perhaps around 50, I'm not sure at all.

Example: Screenshot

3) Ghosts can crit, but the crit damage will be displayed as standard damage.

Consequences: Very little. Just clarity details.

Examples: Video: A Jhin is forced to crit on his fourth shot, and he does crit, but it's not displayed as such.

4) The ghost of the drake doesn't have his buff bar anymore (showing that he has armor pen and buffs
against teams with Dragonslayer stacks).

Consequences: It's pretty impactful here. Few people know about this Ancient Grudge passive.

5) See that indicator on the Scuttle Crab? It's from Mordekaiser's champion page and should be a ghost-
targeting icon. I had to take the screenshot from there, because I never saw this indicator ingame.

Consequences: Damn that indicator would be super convenient. I think I've talked enough about how bad of
an experience it is to try and control the drake. Well that indicator would at least give you an idea of what it's
gonna attack beforehand.

6) Ghosts' attacks can... lag?

Consequences: Just weird visuals.

Reproduction information: No clue. I've only seen that once. It was quite bizarre, though.

Examples: Video

7) How can ghosts have 1% crit chance when they don't even have runes/masteries?

Consequences: I'd say none because nobody has ever cared about this 1% crit on ghosts. It took me almost
a year to notice this, so...

Reproduction information: It's pretty funny. For this to happen, your normal champion must have 1% crit
chance from their runes to begin with. But the ghosts don't use their champions' runes.

Example: Screenshot.

8) Ghosts can appear as not having items. Unless it’s just that Nocturne decided to become spookier.

Consequences: At least that clarity issue matters more than the one above. Still not so important though.

Reproduction information: I don't really know. It happens somewhat frequently, but not always.

Example: Screenshot

9) The armor number should be yellow if it's increased by something.

Consequences: None.

Example: Not gray.

10) Ghosts have very weird base armor and magic resist stats, check the examples.

Consequences: None as well, the total numbers remain the same.

Ghost's armor / Normal armor
Ghost's magic resist (A level 5 melee champion has 36 magic resistance… certainly not 5).

11) Ekko's ghost has the sound of some of his attacks played a bit before the attack applies (damage,
passive proc). It did it for the first 3 attacks, then every third one.

Consequences: Slightly weird, consequences range from very little to none.

12) Some values are missing on Mordekaiser's champion page. Technically, that cannot be referred to as a
"bug", just as an issue, but hey, since I don't make a count this time, I can just not call it as such and it
won't change anything.

Consequences: At first thought, you'd suppose that this page should give useful information about the
champion. Well as a consequence of this, it doesn't.

13) Unlike Jhin's, Graves' ghost does lose pellets upon attacking. But the ammo indicator right below its
health bar will always stay on 2.

Consequences: Clarity. That information is useful, and it's easier not to have to keep the ghost's actual
amount of ammos in mind.

Example: Screenshot

14) If you ult a Garen and kill him while he's spinning, the ghost will always spin too, and will only briefly
interrupt in order to attack.

Consequences: That... doesn't make the ghost very clear. You usually expect to have to step away from a
spinning Garen, so that you don't take loads of damage, but it's not the case here as the spinning doesn't
deal any damage.
Also, that bug can cause serious cases of laughter, which can end up in you losing a fight because you can't
focus anymore. This is a very dangerous issue.

Reproduction information: Kill a Garen while he's spinning, with your ult. 100% reproduction rate.

Example: Video

15) The ghost of a dragon is shown as being level 1 regardless of its actual level. However, after some time,
it sometimes fixes itself to instead show the correct level.

Consequences: Doesn't matter much for a player because you tend not to care about the dragon ghost's
level, just about its stats. However, it was pretty inconvenient when I was testing the interactions.

Reproduction information: That, I don't really know. The amount of time after which the level of the ghost is
shown again seems to be random, and sometimes apparently higher than the duration of the ghost - which
quite obviously means that the real level will never be shown.

Example: Screenshot

Tier 12 - One tier below: Those bugs don't affect gameplay or clarity. They're just the result of inconsistency.

1) If used on a very low life minion, it can deal absurd damage. For example, I once had a minion with 5
health taking 4543 damage from the 4th hit. Or 1200 when I should have dealt 400. This bug seems very rare
and it doesn’t look like it impacts the shield generation.

Consequences: None.

Reproduction information: As I said, this bug is very, very rare. I keep thinking it was only my imagination, but
every time I have that thought, the bug will happen again just to prove me wrong. I don't know if it's a magic
trick to trigger it. Maybe not, if I had to guess.

2) Casting Mordekaiser's W on a Blood Lord Vladimir, then reactivating the spell near minions will cause
Blood Lord Vladimir to glitch as if he were wearing a (little oversized) black coat.

Consequences: Little. It kinda hides a great part of the screen. But for that, you need to have both champs
in the same game, with Vlad using that skin. It's a funny bug though.

Reproduction information: It's all in the description! And 100% reproduction rate.

Example: Video

3) Mordekaiser doesn't shout upon casting his E anymore.

Consequences: Loss of swag, nothing else.

4) A ghost can have little blue particles for an instant around him, upon dying from time. Might be related to
the ghost having a Tear of the Goddess.

Consequences: Absolutely none.

Reproduction information: All's in the description.

5) Ghosts can't taunt characters when the normal champion would. (Example: A Yasuo ghost won't say
anything in front of an enemy Riven using her Q, even when it's the first time she uses her Q during the
game. Yes, I tested that interaction.)

Consequences: None.

Reproduction information: The example of the description works as a way to reproduce this. Supposedly
100% reproduction rate.

6) If Mordekaiser has an Essence Reaver (don't ask me why he would), every single attack of the ghost will
give him 3% of his missing mana back. So Mordekaiser is gonna have that little shiny particle for every attack
of the Child of the Grave.

Consequences: Mordekaiser doesn't have an Essence Reaver. Mordekaiser doesn't have mana. No

7) If a ghost has an Essence Reaver, both his and your crits will make you “regen mana” (as in, have the
particles showing that you gained mana).

Consequences: Mordekaiser doesn't have mana. No consequences aside from you attempting to become a
shiny Pokémon without being shiny. And without being a Pokémon.

8) Literally most gamebreaking of all these bugs:** The Scarecrow passive of a Fiddlesticks ghost doesn't
always work.

Consequences: None.

Example: Video

9) A Bard ghost doesn't spawn chimes.

Consequences: He can't use them anyway. None.

Example: Video

10) Lissandra's ghost has the visual effects for her passive, without having it listed among her buffs.

Consequences: None.

11) Swain's ghost doesn't have a passive.

Consequences: None. Just makes it lack the visuals upon killing a unit. So, none.

12) Yorick's ghost doesn't have a passive.

Consequences: Same as just above in 12.11.

13) The fact that a ghost can gain 1 gold from the Cull if Mordekaiser last-hit a minion and shared the gold
with them is a bug. Or something else is a bug. Either way, something's wrong there. Because normally, a
minion shared counts as a creep in the creep score, and nothing else (it doesn't give any on-kill effect, like
the passive of Mordekaiser's W or or Sion's W).

Consequences: None gameplaywise. Just weird when it comes to how things work. Refer to 14.2.

Example: Video

14) Normally, when Mordekaiser uses an emote while he has a ghost, the ghost also use his own emote of
the same kind. But if the ghost is more than 1000 units away from him, it will not do anything.

Consequences: None in terms of gameplay.

Reproduction information: 1000 units is exactly the range of your W, so see with that.

Tier 13 - Spectate client

1) The ghosts are displayed as having a mana bar, but have no resource bar when you click on them.

Consequences: None.

Example: Screen

2) If you go back in time in the replay while having a ghost on, the ghost will appear as a regular champion.

Consequences: Some clarity. Would be funny if it happened during the LCS...

Example: Video

Tier 14 - Bugs that are not exclusive to Mordekaiser, but that greatly affect him. Those bugs are back to
being important, but deserved to be put aside.

At the beginning of each bug description, I showed the tier the bug would be in if it were exclusive to

1) Tier 4: Ghosts cannot target wards or special units such as Illaoi's tentacles.
This is not a Mordekaiser-specific bug, but Mordekaiser is greatly impacted by it, hence its presence in the
buglist. Now I do consider it as a bug, because it is very unhealthy when you're engaged in a fight around
Shaco's boxes or the likes of these, because alt-clicking them will cause the ghost to... stop attacking at all
and behave weirdly for a couple of moments.

Consequences: This is something that affects all kinds of champion pets. Shaco's clone cannot attack
wards either, nor could the clone granted by Leblanc's previous passive. But that matters a lot for
Mordekaiser. Here are the consequences:
I) Quite obviously, you cannot use your ghost to clear wards, while you'd often want to. If you have the ghost
of an AP enemy and are killing a Nashor, you'd like to use that ghost to clear the pink ward you're sitting on,
instead of having that ghost's weak basic attacks go on the monster while you have to do the clearing duty
instead of Qing the Baron. Or when you'd like to use your ranged ghost to remove that ward over a wall. Or
when you want to walk to mid lane, and let your ghost deal with the pink ward in the pixel brush, just before
it gets teleported back to you because you moved too far away from it, as you wanted.
II) And now, another case where it gets very unhealthy, and why I am almost certain that I can consider this
as a bug instead of just a choice of design. Try to fight alongside a ghost when you're in the middle of Shaco
boxes, or Illaoi's tentacles, Malzahar's voidlings, Yorick's ghouls... If you happen to alt-click on their
summoned units for any reason, it will cause the ghost to stop attacking at all, and to just behave weirdly for
a couple of moments.
III) Teemo's shrooms. Try to attack the shrooms by yourself and the ghost will join you and walk near you,
aka on the shroom. Try to attack a shroom by using right click and alt-right click (so, when you want to try
and make the ghost attack alongside you), and the ghost will have a pretty high chance of walking on it
instead, since it will not be able to attack the it.

Reproduction information: Try alt-clicking wards, Shaco's boxes, Illaoi's tentacles or any other kind of
special units with any of the aforementioned champion-like pets and it won't work.

2) When someone shares a minion with you by using their Relic Shield (or Targon's Brace / Face of the
Mountain / Eye of Something), you don't get the effects that killing a minion would give you. This applies to
Sion's W or to an ADC having a Cull, for example, or in our case, to Mordekaiser's W, with his experience
For you who might say that it's intended... if it were, it would be a stupid design. That item is supposed to
allow the supports to kill some minions without making their ADC lose anything when compared to when the
marksman kills the minion by themselves. Well here as Mordekaiser, you have to make a choice. Since
every minion the support shares with you makes you lose experience, you have to either let him get his
money and lose your experience, or make full use of your W's passive and make him lose money.
Seriously though, I sometimes even consider taking the cannon minions myself if I really need the
experience for a quick level-up! That completely defeats the purpose of the Relic Shield.

3) Tier 8:Upon dashing to an enslaved champion, Lee Sin won't receive a shield, or give one.
Another bug that's not Mordekaiser-specific. Lee Sin's W doesn't see champion clones as champions. But
they are considered as champions for the purposes of most abilities, so that does not make any real sense
– especially since, for example, Shaco's, Wukong's and Leblanc's clones have been updated to be more
deceiving. Well they're not really deceiving when a spell clearly indicates that “this, there, is not a

Consequences: When it comes to Mordekaiser, it doesn't matter as much for you as it does for Lee Sin. I've
already seen a Lee die because he dashed to a ghost to get away from a grim-looking situation, to then die
because of the lack of shield. So that prevents Lee from having access to a shield he should have, in some

4) Tier 8: Mordekaiser's Q seems to be weirdly coded. This also applies to Shen's Q, and Leona's ultimate. It
is known that they aren't counted as a single target spell. Prior to Rylai's nerf, they would only apply a 20%
slow, instead of 40%, which means that they would be counted as multi-hit spells (aka, a DoT), and not AoE
spells. However, they proc Deathfire Touch for 2 seconds and not one, which means that for the purpose of
this item, they are considered as AoE spells and not DoTs. Either way, spell vamp and omnivamp only heal
you for 33% of the damage of those spells.

Consequences: Either little, or none, at the moment. I don't know whether Riot wants this to be considered
an AoE spell or not - if yes, I disagree, because in my opinion, multi-hit is more fitting here, as those are
spells that do hit multiple times. And if yes, there is no current impact. But still if yes, it also prevented
Mordekaiser from inflicting a 40% slow on his Q with the Rylai's effect (AoE spells slowed for 40%, not 20%
as multi-hit spells did).
If no, however, then it means that this spell applies the damage of Deathfire Touch over two seconds
instead of just one. Which is nice to Mordekaiser!

Reproduction information: Either way, that bug doesn't matter as much in terms of ingame consequences
as it does when it comes to the way those spells are coded. And by "those spells", I mean every spell that
buff a certain number of attacks with magic damage (there currently isn't any other: they either add physical
damage - Riven's passive - or apply over a certain time instead of a number of attacks - Rumble's passive).

5) Tier 9: If Mordekaiser uses his Q while he has a Statikk Shiv charged, the Shiv's damage will be dealt
before the damage of the attack. This doesn't apply when the attack with Q is the one that brings the Shiv to
100 stacks.

Consequences: It's a bit disturbing, but that's it. It's not as disturbing as the fact that you'd have a Statikk
Shiv or RFC.

Reproduction information: It also happens with some other champions having a modified auto-attack, like
Garen or Ekko, so there is some (demacian) justice after all, but not to all of them. For example, Illaoi
doesn’t have that on her Harsh Lesson. And it also applies to Rapidfire Cannon and to Kircheis Shard.

Example: Video

Special tier 1 - Some things that might be intended, or even are intended, but that I think are wrong
(argumentation inside)

1) Mordekaiser's W doesn't have a passive in ARAM. It used to have one, and nothing in any patch notes
mentions any kind of change.
Additionally, if you argue that he shouldn't have this passive for balance reasons, don't forget that this is a
nerfed version of the passive that Mordekaiser had in a first place (Mordekaiser only gets 50% of the
experience that the group penalty makes him miss - sure, him getting 100% of the experience yielded by
each minion instead of 25% would have been something, but that's not what this passive does anymore),
that it only works on the minions that Mordekaiser manages to last-hit by himself (which both teams will try
to deny him, his allies because they want some $$$ and his enemies because he's melee), and that
Mordekaiser overall has been toned down as a counterpart for his Dragon Force ability, the passive of his
ultimate allowing him to have that huge advantage of having a dragon ghost. Well, in ARAM, he's been toned
down as a counterpart for nothing, since the closest dragon is as far from the Howling Abyss as the Western
teams from the Summoner's Cup (I still have faith).

2) If you bind your W to the Rift Herald, her circle is super small, while a dragon's is bigger than yours. The
size of the effect of the Harvesters of Sorrow depends on the kind of unit it's around, going as follow: Melee
minions / mage minions < Cannon minions / Siege minions / Champions < Dragons. And the Herald goes in
the same category as the small minions, while the Herald herself is bigger than Mordekaiser. It's supposed
to be something rather strong and menacing, so something on which your W should have an effect as big as
on the Dragons... but that's not the case at all.

3) I don't know if that should be considered as a bug, but there is no alt-s or r-s command for the ghost,
rendering it impossible to make it stop attacking. I've talked lots and lots about the amount of issues that
affected commanding the ghosts, and this just adds up to all of the rest by making the ghosts even more
inconvenient to act around.

4) When the ghost of a Gnar has his rage bar filled, Mordekaiser's screen turns dark red. It's probably not
hard to guess why it happens, but it's Gnar's rage and not yours, and it takes a lot of your screen for
something that will not really matter much, since you aren't Gnar yourself and cannot get the ghost to use
its abilities.

5) This spell has a passive in ARAM. Curse the Dragon... But the Dragon doesn't exist, in ARAM. It's just
something that feels very wrong. Something left where it shouldn't be. In the Howling Abyss, the Twisted
Treeline, the Crystal Scar, there is no such thing as a dragon. Having an effect referring to it isn't logical.
You would have a point by saying that Ivern also has a passive doing something inexistent in ARAM or
Dominion (let me keep the memories of this game mode alive), but removing the passive from those maps
would cause him to have an empty spell, whereas that isn't the case for Mordekaiser. It would do the same
thing as his W whose passive Riot's shamelessly removed too.

Special tier 2 - Outdated bugs, if they can help recognizing a pattern.

1) This one isn't even outdated, it just can only happen in sandbox mode, but I'll just throw it there in case it
can be of any help. If Mordekaiser ults the same target twice within ten seconds (so, before the ult is over),
the second ult won't have any effect, it won't even refresh the dot. That might even be intended, but I don't
mind or care, this section isn't for the sake of showing bugs off, I'm just putting some data in here in case it
can help finding the cause of other bugs.

2) From may-june 2016 to january-february 2017, the ghosts' Sunfires/Cinderhulks/Cinders would not deal
any damage despite having their visuals up. Video

3) The old Leblanc didn't have her passive as a ghost. This is outdated, because she doesn't have this
passive anymore.

4) Mordekaiser's W used to have its passive in ARAM, but it'd stop working after, like, 4 minions. This is
outdated as the spell lost its passive in ARAM.

5) If a ghost was surrounded by two allies, one having an Aegis of the Legion and the other having a Locket
of the Iron Solari, instead of having +15 MR (Solari's aura), the ghost would alternate between both auras
and receive eiteher 10, or 15 MR. The change of aura received occurred twice per second. Video. This bug is
now outdated since there is no more magic resist aura.

6) Heimerdinger's ghost wasn't using his HP regen passive. This is outdated because he doesn't have this
passive anymore.

7) When a ghost killed a unit, it didn't gain the passive of a Serrated Dirk if it had one. This is outdated
because the Serrated Dirk was changed in preseason 7.

8) Aatrox's ghost read that it'd be revived upon dying thanks to the Blood Well, regardless of the cooldown
on that ability when it died, but the ghost will never be revived, also regardless of the cooldown on the ability
(even if you kill Aatrox ten seconds before his passive comes up, meaning that it is up when you have the
ghost). Video

Special tier 3 - As promised, grouping all of the funny bugs.

1) Casting Mordekaiser's W on a Blood Lord Vladimir, then reactivating the spell near minions will cause
Blood Lord Vladimir to glitch as if he were wearing a (little oversized) black coat. Video

2) Caitlyn's Headshot makes her interact very weirdly with the other bugs, that involve
I) If a Caitlyn ghost has a Statikk/RFC/Kircheis Shard, she will only be able to proc it by using her Headshot-
empowered attack. Her Headshot-empowered auto won't make her gains Energized stacks for an unstacked
Statikk/RFC/Kircheis Shard, though.
II) Once Caitlyn's ghost gets her first Headshot off, she then starts applying botrk's damage, as physical
damage, on every auto-attack. Video.

3) Mordekaiser can use his W on Jayce's Acceleration Gate, and the W will be invisible yet still deal damage.

4) Mordekaiser can Q flash blast cone QSS W, but he has to wait before he hits the ground if he wants to Q
flash blast cone QSS E. Maybe the video will make it clearer.

5) If you ult a Garen and kill him while he's spinning, the ghost will always spin too, and will only briefly
interrupt in order to attack. Video

6) Mordekaiser can get a permanently invisible ghost by killing an untargetable champion with his ultimate.
Video 1 / Video 2

Now, a few words that are mostly addressed to Riot. This is probably my last buglist on Mordekaiser. The
amount of hours I've spent doing this from the very beginning to now isn't to be counted in dozens
anymore, and I'll be honest, I'll be kinda bummed out it all of this goes to waste. So unless some fixes start
going through, I don't think I will ever do any work on Mordekaiser bugs again.

I would also like to remind two Riot statements, lest they be forgotten: 15 months ago, as the drake got
removed for Elemental drakes, Meddler said that they'd consider giving Mordekaiser the ghosts of the
infernal drakes. No news of it since then. Source
And more importantly: " We have some time set aside to get these two clusters resolved, but that got
pushed back a wee bit due to end of year Assassins follow up :(." Source
We are now six and a half months after this comment, and probably five months after the final aftermaths of
the preseason update. I've seen one bug be fixed.

This also does make me worry as regards to your statement concerning rewarding the people who made
use of the previous honor system, and I will use this post to also write a message about this. When our
honors got taken away, I had a total of 3136 honors, and had a red ribbon that I haven't lost once since
November 2012. Proof of the former, proof of the latter. So not only do I expect to be disappointed because
I really don't think the compensation will match in any way the amount of honors that I've had plus the fact
that I had a ribbon, just like I am disappointed in the fact that you can only honor one person and that you
cannot honor opponents; not only do I expect to be disappointed, but I am also not sure that I should
expect anything at all, considering how we haven't had any news of the aforementioned announcement in

I really needed to say that at some point, I suppose. But let's not make the final note negative...

Big congratulations for anyone who'd have actually managed to read this through! As I said on Reddit, I
wrote a book that was just barely longer than this post, and 84 isn't really small.
I didn't expect this post to be that long, but hey. Too late now.

Login to comment


D 138 comments Sort comments by: Best New



PePsiLemoNN (EUW)  - 3 years ago

Login to comment Permalink

SoccerTrolls (NA)  - 3 years ago

Login to comment Permalink

NightWind42 (EUW)  - 3 years ago

Login to comment Permalink

TheSingularity (OCE)  - 3 years ago

Login to comment Permalink







© 2020 Riot Games, Inc. All rights reserved. Riot Games, League of Legends and are
trademarks, services marks, or registered trademarks of Riot Games, Inc.

Privacy Notice Terms of Service

Fantasy Violence
Mild Suggestive Themes
Use of Alcohol and Tobacco
Online Interactions Not Rated by the ESRB


© 2020 Riot Games, Inc. All rights reserved. Riot Games, League of Legends and are
trademarks, services marks, or registered trademarks of Riot Games, Inc.

Privacy Notice Terms of Service

Fantasy Violence
Mild Suggestive Themes
Use of Alcohol and Tobacco
Online Interactions Not Rated by the ESRB