League of Legends Player Analytics

Slides:



Advertisements
Similar presentations
ADABAS to RDBMS UsingNatQuery. The following session will provide a high-level overview of NatQuerys ability to automatically extract ADABAS data from.
Advertisements

Phase 3 PAT / Research project. PAT - Research project - Phase 3 Big purpose Investigate problem In Word report provide evidence of full investigation.
PART A Emac Lisp   Emac Lisp is a programming language  Emacs Lisp is a dialect.
1Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall. Exploring Microsoft Office Access 2010 by Robert Grauer, Keith Mast, and Mary Anne.
INFORMATION MANAGEMENT Module INFORMATION MANAGEMENT Module
WATCH LIVE SOCCER ONLINE. When it comes to World Cup, European Cup and other big hit matches, everyone is doing what it takes to watch soccer live. From.
Surrender at 20? Matchmaking in League of Legends Mark Claypool, Jonathan Decelle, Gabriel Hall, and Lindsay O'Donnell Computer Science.
Chapter 6 ANALYZING DATA STATISTICALLY There are several commonly used parameters that allow us to draw conclusions about the characteristics of a data.
Nerfs, Buffs and Bugs – Analysis of the Impact of Patching on League of Legends Artian Kica, Andrew La Manna, Lindsay O’Donnell, Tom Paolillo Mark Claypool.
Mazetool Analytics Project 2 IMGD 2905.
Stats day 7 Final Chapter 3 Day.
Graphing skills.
Learning Objectives : After completing this lesson, you should be able to: Describe key data collection methods Know key definitions: Population vs. Sample.
Splash Screen.
Descriptive Statistics
EMPA Statistical Analysis
Open-O Integration Project Introduction
“All About the Stats” 7th Math Unit 6 Data.
Game Evaluation Michael Awada.
TagPro Analytics Project 3 IMGD 2905.
Chapter 3 Describing Data Using Numerical Measures
League of Legends Game Analytics
PRESENTATION AND DISCUSSION OF RESEARCH FINDINGS
Class of 2016 Advisory 3/2/16.
Proposal report organization
Review Data IMGD 2905.
Nerfs, Buffs and Bugs – Analysis of the Impact of Patching on League of Legends Artian Kica, Andrew La Manna, Lindsay O’Donnell, Tom Paolillo Mark Claypool.
In-class Presentations
U-Pick Game Analytics Project 5 IMGD 2905.
Data Analysis for Game Development
Proposal report organization
Presenter Date | Location
Who Is The Best Player In Major League Baseball?
Exploring Values, Needs, Wants, Goal Setting & Decision Making
League of legends Garic Hill.
Riot Game(s?) Presentation by Matthew Tran.
5.6 “I can find the maximum, minimum, range, mean, median, and mode to explain what each does and does not indicate about a set of data.”
Data Analysis for Game Development
Continuous Improvement for Writing
FIFA 18 Player Analytics Project 1 IMGD 2905.
Graphing skills.
Ivan Ramler and Choong-Soo Lee
Mazetool Analytics Project 2 IMGD 2905.
U-Pick Game Analytics Project 5 IMGD 2905.
DAY 3 Sections 1.2 and 1.3.
Year 2 End of Key Stage Information
CPSC 531: System Modeling and Simulation
Data Presentation Carey Williamson Department of Computer Science
Good Behavior Game Overview
Student Presentations
League of Legends Player Analytics
Project Pathfinding IMGD 4000 Due: March 28th, 11:59pm.
Lab Reports What goes into a lab report? Why do we need a report?
Unit 6B Measures of Variation Ms. Young.
League of Legends Game Analytics
Chapter 1 The Where, Why, and How of Data Collection
Unit 3 – Web design Final Project
Carey Williamson Department of Computer Science University of Calgary
Nagendra Vemulapalli Exam2 Overview Nagendra Vemulapalli
Mazetool Analytics Project 2 IMGD 2905.
Heroes of the Storm Analytics
Lindsay Liebert & Julia Calabrese March 26, 2018 Block 2
Continuous Improvement for Writing
Drift and Sounder* Analytics
The Where, Why, and How of Data Collection
U-Pick Game Analytics Project 5 IMGD 2905.
Project Behavior Tree IMGD 4000 Due: April 7th, 11:59pm.
Preparing Written Reports
Chapter 1 The Where, Why, and How of Data Collection
Presentation transcript:

League of Legends Player Analytics Project 1 IMGD 2905

Overview Set up tools for game analytics pipeline Apply to Riot's League of Legends Pipeline: Basic queries this project, but preparation for more advanced in project 3

League of Legends Most popular game in world [1] Played by more than 27 million people each day Professional leagues (e-Sports) 32 million viewers 2014 at World Championships 8.5 million simultaneous (compare to 16 million for soccer World Cup) Team versus team game (5v5) Teams based on player ranking (~25 ranks) Players each choose 1 Champion Over 130 choices 10 unique per game Champions have abilities and level up in game Player can buy items to enhance Champion [1] Raptr - The Offical Blog (2015). Most Played Games: November 2015. http: //goo.gl/bVytCX

Parts Part 0 - Setup Part 1 - Matches Played Part 2 - Champions Played Part 3 - Compare Players Part 4 - Match Data Writeup Submission Grading

Part 0 - Setup Named “part 0” since don’t write up  but critical for rest of projects! http://web.cs.wpi.edu/~imgd2905/d17/projects/proj1/setup.html Install Python Windows or Linux (or Mac?) Get Riot API Key Install RiotWatcher Test It Out (hello.py)  Fix before proceeding! Install spreadsheet

Part 1 – Matches Played Player “Faker” (the “god” of League) See “basic.py” Understand each line Copy and modify to get data needed Output in comma separated values (“csv”) Graph in Excel Days, Match, 0.00, 0, 0.03, 1, 0.06, 2, 0.39, 3, 0.42, 4, 1.01, 5, 1.05, 6, ...

Part 2 – Champions Played Champion Faker played most Obtain from Champion ids Compute “mode” Mode() in Excel Cross-reference with static champion list (static_get_champion_list(), match[‘champion’]) Commonly needed E.g., Leona is 89 Compare oldest half and newest half  Was there a change? 67, 236, 119, 64, 25, 202, ...

Part 3 – Compare Players Repeat above analysis but for additional player e.g., another professional or your friend Must have done competitive/ranked matches Re-inforce above methodology Graph with 2 trend lines, table with 2 players https://www.downlossless.net/videos/lol-best-moments-106-faker-vs-bronze-4-player-league-of-legends-15u5n4h594h4d6f6b6x4e6.html

Part 4 – Match Data Length of Faker’s matches Histogram Need to pull out full match data Summary statistics Min Max Mean Standard Deviation for match in match_list: fullMatch = r_w.get_match(match['matchId'])

Write Up Short report Content key, but structure and writing matter Consider: Ease of extracting information Organization Concise and precise Clarity Grammar/English Graphs/tables: Number and caption Referred to by number Labeled axes. Explained trend lines Message

Grading Part 1 (Matches) - 60% Part 2 (Champs) - 20% Part 3 (Compare) - 13% Part 4 (Durations) - 7% All visible in report! (Late – 10% per day)

Rubric 100-90. The submission clearly exceeds requirements. All parts of the project have been completed or nearly completed. The report is clearly organized and well-written, graphs and tables are clearly labeled and described and messages provided about each part of the analysis. 89-80. The submission meets requirements. The first 3 parts of the project have been completed or nearly completed, but not part 4. The report is organized and well-written, graphs and tables are labeled and described and messages provided about most of the analysis. 79-70. The submission barely meets requirements. The first 2 parts of the project have been completed or nearly completed, but not parts 3 or 4. The report is semi-organized and semi-well-written, graphs and tables are somewhat labeled and described, but parts may be missing. Messages are not always clearly provided for the analysis. 69-60. The project fails to meet requirements in some places. The first part of the project has been completed or nearly completed, but not parts 2, 3 or 4. The report is not well-organized nor well-written, graphs and tables are not labeled or may be missing. Messages are not always provided for the analysis. 59-0. The project does not meet requirements. No part of the project has been completed. The report is not well-organized nor well-written, graphs and tables are not labeled and/or are missing. Messages are not consistently provided for the analysis.