[Suggestions] Show less common lanes for champs (but warn it's based on small sample), allow for Gold+ or Platinum+ as options, and...

[corylulu]

Just a few suggestions I think would make the site a lot more useful than it already is.

1. Show less common lanes for champions. If people want to find out builds for a niche jungle Teemo build, they should be able to find it. Just give those roles a yellow border around them to illustrate that they have a low sample size.
2. Allow people to also pull from Gold+ games instead of only Platinum+ games. Sometimes the Platinum+ pool is too small and shows some fairly bad data as the "highest win rate". This would also improve results for the 1st suggestion.
3. In addition to "Most common" and "Highest win rate", include an optional "Alternative Build" which finds the most successful/common build that isn't the most common or most successful. This would be great for finding builds for things like AP Bruiser Udyr, AD Teemo, or something similar. I would also be good for replacing "Most common" when the most common build is also the highest win rate.

I'd be willing to help make the site changes for this, but it would require some database/datamining changes that don't have source, so it would require help on your end. Any of these things sound appealing to you?

[matmalone]

1. In my humble opinion, the threshold criteria it's using now for whether to include the role could be better. I'm sure the absolute quantity of people playing mid Ezreal is much greater than the quantity of people playing support Galio (currently with just 559 games).

2. I've been thinking about this as well. Personally I think there's a lot that could be done here that would be really interesting. For example, what's a good Malphite build when you're against an AP champ in lane? My suspicion is that including too much info on the existing champion page might be too cluttered. Might be better as a separate feature -- if not a totally separate site.

[corylulu]

@matmalone I think at the very least, they are things that the API can include, even if the site doesn't so that people could make use of it still. Making a whole new site for it seems like a lot of redundant work when including it wouldn't be terribly difficult by comparison.