One concern that many people have is that player rating systems are often too general. Iâ€™ll be the first to tell you my Composite Score rating system needs a bunch of contextual information to truly be useful. Itâ€™s simply too hard to sum up all of a playerâ€™s abilities with a single number. One major problem is all the things that go unmeasured, although thatâ€™s outside the scope of our abilities until we start tracking new things.
A second major problem, one that Iâ€™m trying to find a solution for, is that different teams have different needs for different situations. Letâ€™s say Shaquille Oâ€™Neal rates better than Rashard Lewis in Player Rating System X. The Magic should try to swap Lewis for Shaq, then, right? Obviously not. Orlando needs a big man (calling Lewis â€œbigâ€ is a stretch, but go along with it for now) that can stretch the floor and give space for Dwight Howard down low. Suddenly, weâ€™re doing so much contextual research for Player Rating System X that the player rating itself isnâ€™t that useful anymore. Instead, weâ€™re relying on shooting percentages, shooting tendencies, rebounding ability, defensive ability, etc.
It still would be nice to have one number when weâ€™re trying to evaluate players, if for no other reason than to save time. But weâ€™ve already proven that one number is useless without context. What can we do?
Create multiple sets of player ratings. Better yet, create an organic player rating system that adjusts based on whatever is important to us at the moment. The Magic need a power forward that can shoot three-pointers efficiently and create his own shot from time to time? Ok, letâ€™s rate power forwards based on that.
The next step is to calculate all of those little components and adjust them by position. Why adjust for position? If we made a player rating system based on three-point shooting ability and shot-creation alone, without adjusting for position, our numbers would tell us the Magic should acquire someone like Roger Mason and put him at power forward. That doesnâ€™t seem like a wise suggestion.
Once we have all the position-adjusted components, we can then decide which are important based on our needs. Today is the first step. Similar to how I broke down individual players by quarter, each player in the league will be rated based on how he performs from four shooting locations: close (dunks and layups), midrange (including post shots), three-pointers, and getting to the free throw line. Each rating is adjusted for position, so a center with a 90 rating on three-pointers is still very likely worse overall than a shooting guard with an 80.
The ratings will combine both frequency and efficiency. In other words, if a player rarely shoots from midrange but is efficient at it, he wonâ€™t rate that well. Similarly, if he shoots from midrange all the time but is highly inefficient, he also wonâ€™t rate well. Ratings are on a scale of 1 to 100, with 50 being average for that position.
Frequency is measured by the playerâ€™s attempts from that shot location divided by his total attempts. Efficiency is measured by his makes divided by his total attempts from that location. The only situation that is included in this efficiency measure is when a shot actually goes up, so things like turnovers are ignored.
Before I release the numbers, I should say that these shooting tendencies and efficiencies are nothing new. 82games.com has had this data available for a while now. My methods for extracting these tendencies and efficiencies from the play-by-play data are slightly different, but they are similar. The new step I am taking is adjusting these numbers by position and creating a rating system off of these adjustments. The numbers are available through Google Docs below:
If youâ€™re angry because a certain player does not rate the way youâ€™d expect, allow me to explain. First, remember these ratings account for efficiency. Superstars may be excellent shot producers (a skill I will rate in the near future), but they are not always the most efficient. Second, these ratings also account for a playerâ€™s tendencies. If a player is extremely likely to take a certain shot, his rating will be high for that. However, if he balances his shot attempts, he will not rate extremely high in any of them.
A simple way to look at it is that these ratings are attempting to describe players as much as they are attempting to evaluate them. LeBron James may only get an 80 in close shots (which is still quite high), but thatâ€™s because he mixes up his attempts. He clearly is one of the most frightening players in the world when heâ€™s near the basket.
These ratings do evaluate to an extent, but the bulk of evaluation for my new rating system will come from other components. Shooting ratings will be a big part of the context I mentioned at the beginning of this article.
This is just a first run, so changes will inevitably be made. If you have any suggestions, feel free to comment below.