Friday, January 17, 2014

Some pick/ban stats from week 1 EULCS

Despite the fact that Gragas was played in 9 out of the 16 games, he was only banned one time.

Yasuo, on the other hand, was banned 4 times by blue team and 3 times by red team, for a total of 7 bans, but was only picked two times.  His winrate was 50%; MIL lost to FNC with him and CW beat ROC with him.

Kassadin was banned 6 times by blue team and 8 times by red team, for a total of 14 bans.  In the 2 games he was open, he was picked one of them---and SK lastpicked him against SHC, after SHC had already locked in Gragas.  The game Kassadin was open and unpicked, the midlane matchup was Ziggs (SK) vs LeBlanc (MIL).

Midlane was almost always last-picked.  In fact,  in only 5 games did the red team not last-pick mid, and in 1 of them their midlane pick of Zyra seemed like it could have been a support.  Of the 5 games that mid wasn't last picked, in 4 of them support was last-picked and Renekton was last-picked in the last game.

There was a fairly broad variety in midlaners, with 13 different champions used in that role (7 only a single time).

Looking at supports, Annie had a 100% pick-ban rate, open in 5 games; she had a 60% winrate.  And in all but one game that she was picked, she was against a Thresh; the other game, SK-MIL, the matchup was Annie-Leona.

Leona was banned 4 times and picked 5 times, with a 40% winrate.

Thresh was picked 10 times and banned 4 times, so he was only available and unpicked in 2 games.  Those two games were GMB-CW (Kennen-Lulu) and SK-MIL (Leona-Annie).

Overall, there were 9 different supports picked; of these, 4 were played only one time.

ADC was probably the role with the least variety in picks; only 6 ADCs were picked, and 2 of them (Sivir, Vayne) only one time---the stars were Jinx (9), Lucian (10), Caitlyn (7), and Ezreal (4).

Despite that, ADCs weren't often banned.  Lucian and Jinx were each banned once and that was it for ADC bans.

First-picked champions were usually jungle or toplane.  Toplane was first-picked 4 times; Jungle 7; ADC 1; and support 4 times.  Three of the four support first-picks were Annie; the other was Thresh, and both Annie and Leona (the other two most-popular support picks) were both banned that game.

Toplane seemed to be ruled by Shyvana, Renekton and Dr. Mundo.  Of these champions, Mundo was banned 5 times and picked 8, making him one of the most-picked/banned champs of the week.  Renekton was played 8 times as well but not banned a single time.

Shyvana was banned 3 times and picked 9---in toplane.  She was also picked an additional 3 times in the jungle; the only game she was ignored in was MIL-FNC, in which MIL ran toplane Gragas against Renekton.  (That was the same game that was the only one with the last-pick Renekton.)

There were 8 distinct champions played in toplane.

Jungle saw 9 different champions played; Vi (9) and Lee Sin (9) were played much more than other champions, but Elise saw 4 games as well.

Special mention goes to Gragas, who was played in 3 different roles---midlane predominantly but also top and support for a game each.

What do you think we'll see in NA?  More or less variety?  What champions will be snatched up early, and who will counterpicks be saved for?

Wednesday, January 8, 2014

How to Theorycraft Effectively


To some people, that word is scary---OMG NUMBERS EW, while to others it's exciting---I'm gonna figure out the BEST way to set up/build my champion, and then beat you because my build is better!

For me, theorycrafting is definitely the latter.  I love seeing what the numbers tell me and then applying that in my gameplay!  The goal of this article is to get you to feel the same way---or help you theorycraft more efficiently if it's something you already do.  :)

Note that this guide assumes you have access to Microsoft Excel 1010+, but you can do most of what I discuss with Google's spreadsheet tool.

Step 1.  Come up with a good question.

That's it!  Come up with a question that you answer, but make sure it's a good question.  Examples of good questions: "Are hybrid pen marks or magic pen marks better on LeBlanc if I'm vs a Riven starting Doran's Shield?  What about against an Ahri starting Doran's Ring?" or "On Annie, if I'm going to be poking with Q 3-4 times between Ws, should I max Q first or should I max W first?  And what will the implications on my mana pool be?"

Examples of bad questions: "What's the best build order for Caitlyn?" or "What should my support runes be?"

Now, the last two questions are definitely good questions to ask.  But they're bad theorycrafting questions---they're just too general!  A good question needs to have a very specific way to answer it using numbers from the game.

Let's look at our "good" examples.  In the first question, we're wondering, do we want MPen or HyPen marks on LeBlanc?  That's half the information we need---our OPTIONS, and our champion's STATS that affect our options.  However---it's not enough.  Your champion's stats are affected by the enemy's stats as well, and so we need to know what the enemy is.  Riven starting Doran's shield, for example, is going to be a lot harder to poke down with autoattacks than an Ahri starting Doran's Ring.  If you're against a Doran's Shield, that's 8 damage per auto that you're losing, and Riven will also have higher base armor than Ahri.  On the other hand, you're likely to get more autos per Q/W/E against a Riven than against an Ahri because Ahri is also ranged.  So when looking at the total damage you do in one "rotation," you're going to want to include more autos vs a Riven than you would against an Ahri.

If that doesn't make sense, don't worry---there will be examples later on!

Now let's look at our second question, about Annie.  This question is somewhat more simple than the first one, because we've provided even more information---there will be 3-4 Qs between Ws.  Annie's Q gains less damage per level than her W does, but it's slightly longer range and on a shorter cooldown; also the fact that it's targeted makes it easier to land and then back away.  So which spell would you want to scale if this is going to be your combo?  We can easily extend it to 2 Qs between Ws or 1 Q between Ws (in fact, "How many Qs between Ws do I need to make it worth it to scale Q over W?" would be another good question to ask).  However, Annie also doesn't have the freest of mana costs if she's spamming her spells.  So we add the second part---how sustainable is this?  Given the amount of regen that you have, how many rotations will you be able to get through?

Now let's talk a bit about the "bad" examples.  "What's the best build order for Caitlyn?"  Well, what are you trying to accomplish?  Max DPS upon reaching 6k gold into your build against a tank that's built Sunfire and Spirit Visage and also has a Warden's Mail?  Or a build that will help you take down towers as efficiently as possible only 4k gold in?  Or a build that will minimize the time it takes for you to clear a wave of creeps?  Or a build that's best for dueling the enemy ADC?  These questions could have very different answers.

And finally, "What should my support runes be?"  Well, what champion are you playing, first of all!?  Runes for Lulu will be different from runes for Taric will be different from runes for Janna.  And furthermore, runes can change a ton on the matchup and overall game flow---if I'm gonna be 2v1ing as Nami, I might do scaling mana regen quints, but if I'm in a 2v2 as Vayne-Nami vs Lucian-Leona, I probably want flat HP instead.

What you should notice, though, is that bad questions are made up of multiple good questions.  That is, if you have a general question like "What should my support runes be?" then you can break it up into smaller, more specific questions, which you then answer separately.

For the rest of this article, I'm gonna be using the question, "What should my offense quints be on Sona?"  This is split up into several sub-questions.  Separate cases include vs Zyra (a stand-in for a ranged support) or vs Leona (a stand-in for a melee support); and different options for offense quints.

(If you want to skip straight to the result, check out the end of the charts section of my Sona guide here (not linking that section directly cos sometimes the numbers change).)

Step 2.  Decide what stats you need in order to answer the question.

In general, if you're looking at an offensive thing (how much damage do I do to ----, how can I best do damage, etc.), you need to know your AP, your AD, your flat ArPen, your flat MPen, your percent ArPen, and your percent MPen.  You also need to know your enemy's stats---armor and magic resist for the most part.

Of course, these stats will come from different sources: items, runes, masteries, base stats, and hypothetically auras that your team has, so you need to make sure you include all of these sources!

Here are the stats that I use for this particular question.

So I have Zyra Armor Base and Scaling; MR Base and Scaling; the same stats for Leona; and also rune (Yel/Bl) and mastery (M) armor and MR.  I do NOT include items on Zyra or Leona, but if I wanted to then I could make two more boxes for each of them; if I wanted to include percent armor/MR increase that would be another thing I'd want to make a box for.


There are several reasons for this.  First of all is error checking---you might just make a mistake when trying to make a calculation!  It's a lot easier to trace mistakes back if there are no values directly in the formula.

And second, League of Legends is NOT a static game!  Patches happen ALL THE TIME, and the spreadsheet that you just spent all day making might be completely irrelevant in as short a time as 2 weeks from now when all of your champion's base values are changed!  You do NOT want to have to change everything just because of something so minor as an increase in base armor by 2 or a decrease in base AD by 1.5.

If your calculations say "+(47+3*$C3)" where C3 is champion level, and suddenly Sona gets a buff to have 53 AD at level 1, then we'd have to edit everything.  However, if the calculation says "+($A$4+$A$6*$C3)" then all we have to change is the cell A4 that has Sona's base AD written in it and increase that number by 3.


If you get confused about seeing too many things like $X$8 in your formula and not being able to read it well, you can name your cell!  Right click on the cell, and this menu will pop up:

You can click Define Name and then type whatever name you want into it.

Then, you can make a formula like this instead!

If you don't want to define names, there's another thing that you can use to help you figure out where formulas are referencing which values:

Colors!  They start to repeat after a while, but most formulas won't reference too many things, especially because of the next part.

Step 3.  Figure out what intermediate values you need, and calculate them.

You really don't want your formulas cluttered, first of all.  In general, my rule-of-thumb is to avoid having more than 8 cells referenced by a particular formula; if I need to reference that many values, then I should be splitting up the calculation.

In general, you NEVER want to be adding up multiple pieces that contribute to a single stat within your final formula.  What I mean by that is, you should never have something like

=(DAMAGE/(1+(AR_RUNE+AR_MASTERY+AR_ITEM+AR_BASE+LVL*AR_LVL)/100).  Instead, you would want all of those sources of armor added up into a single cell and then the formula to be =DAMAGE/(1+AR_NET/100).

There are a few reasons for this.

First of all, it makes it easier to find mistakes!  (This is always a reason.)  Second, what if Riot did something SUPER EVIL like changing the order of percent pen vs flat pen again!?!!?  You would have to go through your final formula in every single cell and change it!  Ewwwwww....Whereas you can just change the armor formula itself if you do it this way.

And what if you just want to change your situation?  Suppose suddenly you're curious about what if Leona has W active?  Or if Renekton decided to take the % increase in armor/MR mastery?


Finally, sometimes the intermediate steps can give you interesting information.  "Oh, I didn't realize that an increase by ---- in armor actually led to a ---- damage change at this point in the game."  All of what you do here should help you to build your intuition of what numbers mean what.  And so the more "useful" numbers you see the better.

Let's go back to our example.  I actually have 2 sets of intermediate values.

First, I calculate net stats amor/MR/AD/AP/Flat and % Pen:

Why are all of those numbers there 3 times!?  Well, because the next set of intermediate values I calculate are the PHYSICAL and MAGICAL parts of Sona's damage, SEPARATELY.

Let's look at the formulas I use.

First, Magic Mod:


Phys Mod:


And for reference, X8 = Enemy Armor:


And X9, Enemy Magic Resist:


See how this could be confusing if I didn't do intermediate calculations?

Now, below that entire chart of constants, I have the following cell that explains to me:

Magic Modifier = 1/(1+(MR*(1-%MPen/100)-FlatMPen)/100).  Physical Modifier the analogous for physical damage. 

So if I forget exactly what it is that I did (say 4 months from now), I have a note reminding me exactly what I've done.

(n.b. the magic modifier is what you multiply your magic damage by to get the amount of damage actually dealt to the enemy champion accounting for their MR; same thing for phys modifier only for physical damage.)

Ok and now let's look at the actual damages set of numbers.

As you can see, it's "just" a ton of different potential combinations of damages you might do.  The standard trading combo is AA+Q+QC, but you might also get AAs in between Qs...and then because this is level 6, you also have to wonder about your ult, etc. etc.

Here are the formulas for a few of the cells:

Powerchord Magic:


It references the current chord damage (which is a weird enough scaling that I just enter it by hand each level), AP, the AP scaling on chord, and of course the magic modifier.

Autoattack, Phys Damage:


Just your AD * the physical modifier.



Summing things up in that column

And then Net is just the sum of the physical damage and the magic damage.

See!?  Not too bad :)

Now, you might be wondering about my use of $....

Step 4.  Make your formulas universal enough that you can autofill EVERYTHING!

This probably shouldn't be its own step, but whatever.  This is the SINGLE MOST IMPORTANT THING TO DO.  Well, one of them anyway.  You need to be able to click on a cell and then drag it to autofill an entire region.  And then one you've filled all of the unique things, copy-paste that section to autofill everything else.

If you don't know how autofill works, or static values with $, just google "excel autofill" (without the quotes) and read a tutorial.

I'll give you an example of what I autofilled in these sheets.

Here's the picture of the values section again:

Magic Modifer and Physical Modifer were each typed out one time, and then dragged horizontally to autofill the rest.  Additionally, every value that is not blue was autofilled from the closest blue column to the left (e.g. Y9 the formula is "=X9").  And if a value is unchanging across the entire grid, I just autofilled it also to equal the cell directly to its left.  Or if it's only changed for one of the blue columns, I autofilled it for the rest of the blue columns from the first blue column.

Basically, I made it so that if anything changes, I need to edit AS FEW CELLS AS POSSIBLE.

I also made it take as little time to fill in the grid as possible.

For those of you not familiar with autofill (I'm not making an entire guide about it), keep in mind I'm using the same word to talk about two things --- first, the ability to copy a formula to other cells by clicking the corner of the starting cell and then dragging it along the region; and second, the ability to have other cells change automatically by having their values just be "=STARTINGCELL"

What $ does is it holds either the row or column or both constant when doing click-and-drag autofilling, which is equivalent to copy-paste.  Cut-and-paste works differently; it basically renames itself to the new location, so precedents and dependents are not affected in any way.

Step 5.  Decide how you want to present the final data, and fill in that formula.

In this example, all I care about are the net damages.  So I'm gonna remake the chart with only net damages instead of the intermediary damages as well.

The formulas here are all of the form "=F9," i.e. they just reference the upper chart.  Again these charts can be autofilled by just clicking and dragging, once across and then once vertically.

I also added a conditional format.  The rule is simply:

And then I actually copy-pasted each row vertically saying copy formatting only to apply the conditional format to each row individually of the chart.  This isn't too bad because you can power-of-2-increase the amount that you're copying (i.e. first row is formatted, copy it, then copy first 2 rows, etc.).

You can use more complicated conditional formatting as well though.  Here's the format I used for the cooldown charts:

You should attempt to do as much conditional formatting as possible!  Formatting by hand is f*king obnoxious!

I want to stop for a moment and mention DECIDNG HOW TO BEST PRESENT DATA IS REALLY, REALLY, REALLY, REALLY DIFFICULT!  IT TAKES A LOT OF PRACTICE TO GENERATE CHARTS THAT ACTUALLY CONVEY WHAT YOU WANT THEM TO CONVEY AND ARE EASY TO READ!  However, it's also REALLY, REALLY IMPORTANT!  If you do a whole bunch of calculations but you can't look at any of the numbers at the same time, it's gonna be really hard for you to actually learn anything from your calculations.


Ok, maybe this is actually the most important thing!

I want to introduce you to a feature of Excel that you may or may not be familiar with:  Dependent and Precedent tracing!

Here's how you do it: Find the Page Layout tab at the top, and then you'll see a section that looks like this:
Say you have A1 highlighted.  Then if you click "Trace Precedents" it shows you arrows from all cells that A1 references leading to A1 (i.e. the precedents of A1), and if you click "Trace Dependents" then it shows you arrows from A1 to all cells that reference A1.

This can help you a TON to catch mistakes made when potentially overusing autofill or forgetting a $ somewhere or putting a $ that you didn't mean.

And then the final thing you should do is always the check of "Does this make sense???"  If it says that your Q is going to be dealing 70 damage at level 1 with 0 bonus AD or AP, you proooobably made a mistake since Q only deals 50 damage!  Make sure you didn't accidentally put a - sign when you meant a + or something like that.

You can also edit your source cells to see if numbers change the way you expect them to.  Let's give Zyra 100 armor.  Now is the amount of damage we're doing to her slightly less than half of our stated damage (slightly less than to account for penetration that you might have).


This comes AFTER you've done all your error checking, AFTER you've done the pretty formatting.  Absolutely dead last.  Now you're ready to change your starting values and compare numbers.

Notice how in the stats section I have some orange cells and some purple cells?  Yeah, those.  The orange cells are cells that I can change the values of in order to adjust starting info---say suddenly Sona is speccing 21 into offense and has penetration, or I want to give her a Haunting Guise---or, more reasonably, I just want to see what happens with different options for offense quints.  I can change those numbers and then look at the change in results of my final charts.

And then the purple cells are cells that I can change based on the champion level.


"Awww but I really like having AP reds on Sona..."  Well we showed here that it's not actually good.  So don't do it.  If you're doing theorycrafting, the numbers aren't lying to you.  Adjust your gameplay or rune/mastery choices based on what the numbers tell you!

That does come with one caveat---say you get more DPS from AD as opposed to AS, but you feel like you play better due to the faster AA animation.  Sure, go for AS!  That's something that's qualitative, and theorycrafting can only help you make quantitative decisions.  Qualitative ones are still up to you!