Not Updated For Current Season
This guide has not yet been updated for the current season. Please keep this in mind while reading. You can see the most recently updated guides on the browse guides page
x
x

Did this guide help you? If so please give them a vote or leave a comment.
You can even win prizes by doing so!
Vote
Comment
I liked this Guide

I didn't like this Guide




Your votes and comments encourage our guide authors to continue
creating helpful guides for the League of Legends community.
I like what you did here! I'm a bit skeptical of your build, but I really like the concept of AD Malzahar, and I love how well you explained everything!
With that said, here are some things to improve:
.
.
Great explanations and details, I love reading guides like yours :)
I will wait to vote until you have done something to deal with the bb-coding and links that I mentioned. Just PM me when it's done or if you have questions.
Great job so far!
-Teyso
P.S. PM me to let me know if / when you want a rating. I will wait indefinitely if you want, just PM me when you want the rating.
Could you add the comparison between your DPS in your combo vs AP Malzahar's? It would be great to see it.
Soon!
Could you add the comparison between your DPS in your combo vs AP Malzahar's? It would be great to see it. Also, some screenshots of game results would help us notice your build is successful or not ;)
Don't own him, but if I see a
It's awesome, I had tried AD malzahar before but this build is better, and the tips & tricks are great. I would suggest to play AD malz always as ADC, because in mid the voidling can't chase the enemy long enough. Keep it up to S3!
You said that a level 1 Voiding would do 60 ad after 14 seconds. But how is that possible if the minion has a base damage of 25 at level 1 and the damage increases by 50% (12.5), That would make the ad 37.5 not 60.
True, I made a mistake and added +100% base damage instead of +50%, but it will actually have 47,5 AD thanks to the 10 bonus AD you have from runes and masteries. I'll correct it asap, thanks for pointing it up!