Fantasy points formula

[FTP-ashario]

Version 110 saw the introduction of a new set of calculations for determining fantasy points earned. In summary, the two main changes to the calculations are:

- batting points are awarded relative to the total runs scored in a match. For example, scoring 50 in a low scoring match will earn you more points than scoring 50 in a high scoring match
- points awarded for wickets are based on the batting order of the player. For example, less points are awarded for dismissing the #11 batsmen compared to a batsman in the top 6.

There are also two sets of weightings used when calculating points. One set is used for senior and youth one day matches. Another set is used for Twenty20 matches.

Particular thanks are extended to MOD-R0b1et, who was the driving force behind the development and testing of the new calculations.

(this thread is a work in progress)

[FTP-ashario]

Points per player = batting points + bowling points + fielding points

Batting Points

Before batting points are awarded, two 'multipliers' need to be calculated, the runs ratio and the strike rate ration.

Runs scored ratio
To account for the different conditions the batsmen face, the effective total runs scored in the game must be considered for this calulation the total runs scored with availible resources is considered. This is used to scale the effect of runs scored by generating a "runs ratio".

If the second innings is incomplete (the first always will be), an estimate of the final score they would have achieved must be made, to do this the lower total of that assuming overs were the limiting factor or that assuming wickets were the limiting factor is taken:
Total if overs were the limiting factor = Score * (300/balls used)
Total if wickets were the limiting factor = Score * R (R defined from table below)

Code: Select all

Wickets lost: 0     1     2     3     4     5     6     7     8     9     10     
Ratio:        100   6.92  3.46  2.34  1.78  1.46  1.28  1.16  1.08  1.03  1


For the purposes of our calculations, we assume the average total runs scored in a match is 410.

Team batting first gets 125ao (45overs).
The chasing team reaches the target to get 127/3 off 34 overs.

Total if overs limiting = 127 * (300/204) = 187
Total if wickets limiting = 127 * 2.34 = 297

So the second innings will be considered to score 187. Therefore the effective total score of the game is 187+125 = 312.
That makes the runs ratio 410/312 = 1.31.

In this game each run scored will earn 1.31 points.
For example, a batsman scoring 45 in the game will earn 45 * 1.31 = 59 points.

Strike rate ratio
The strike rate ratio is calculated using the actual totals and balls faced, simply 100*runs/balls.

For the purposes of our calculations, we assume that 75 runs per 100 balls is the average strikerate for batsmen.

The strike rate ratio = 75/actual strike rate for the match.
This ratio will be used to scale strike rates before assigning strike rate points.

In our example game:
Strike rate ratio = 100*(125+127)/(270+204) = 53
strike rate ratio = 75/53 = 1.42

In this game, each batsman's actual strike rate will be multiplied by 1.42 before awarding strike rate points.

Strike rate bonus/penalty table
Strike rate bonuses are multiplative to the runs scored and calculated from adjusted strike rates.
Adjusted strike rates are calculated by the players strike rate * strike rate ratio.
For example, if a batsman scored 45 from 67 balls, he would have an adjusted strike rate of ( (45/67) * 1.42) = 95.4.

The percentage bonuses/penalties applied are as follows:

Code: Select all

Adjusted strike rate <10         10-34.99    35-59.99    60-84.99   85-109.99  110-159.99 >159.99   
% bonus             -40%             -20%        -10%           0        +10%        +20%    +40%


Milestone points
For scores >=100, 40 bonus points
For scores 50-99, 20 bonus points
For scores 25-49, 10 bonus points
Dismissed, -10 points
Dismissed for a duck, -10 points (so a duck scores -20)
For each six hit, 4 points.

Graham Gordon scores 17 (off 47) in the our example match, with 1 six.
run points = 17 * 1.31 = 22.3 points
dismissed = -10 points
adjusted strikerate = 1.42 * (100*17/47) = 51
strikerate penalty = -10% for strike rate = -2.2 points
sixes = 1 * 4 = 4 points
TOTAL BATTING POINTS = 22.3 -10 -2.2 +4 = 14.1 points

Bowling Points

Points for each wicket
Each wicket scores points based on the batting order position of then batsman dissmissed with this table:

Code: Select all

Batting position:  1  2  3  4  5  6  7  8  9 10 11
Points scored:    26 26 25 24 22 18 14 11  8  6  3


Milestone points
Bonus points are allocated for the number of wickets taken as follows:
2 wickets = 5 points
3 wickets = 10 points
4 wickets = 20 points
5+ wickets = 40 points

Economy points
Points are awarded for economy rate as follows assuming at least 3 complete overs are bowled by the bowler.

Code: Select all

Econ rate: <1.5rpo | 1.5 - 2.49 | 2.5 - 3.49 | 3.5 - 5.49 | 5.5 - 6.49 | 6.5 - 7.49 | > 7.49
Points:         40           20           10            0          -10          -20      -40


Finally, there is a 6 point bonus for each maiden over.
These are added together to gain the total bowling score.

Graham Gordon achieves bowling figures of 3/37 from 10 overs, bowling 1 maiden (his wickets are the 2nd, 3rd and 7th batsmen).
Wicket points = 26+25+14 = 65
Milestone points = 10
Econ points = 0
Maiden pts = 1*6 = 6
TOTAL BOWLING POINTS = 65+10+0+6 = 81.

Fielding Points

Catch by keeper or fielder: 10 points
Stumping by keeper: 10 points
Runout by keeper or fielder: 10 points

Graham Gordon took 2 catches. His fielding points are 2*10=20 points.

Graham Gordon's total points allocated for this match = 14.1 (batting) + 81 (bowling) + 20 (fielding) = 115.1.

[FTP-ashario]

Points per player = batting points + bowling points + fielding points

Batting Points

Before batting points are awarded, two 'multipliers' need to be calculated, the runs ratio and the strike rate ration.

Runs scored ratio
To account for the different conditions the batsmen face, the effective total runs scored in the game must be considered for this calulation the total runs scored with availible resources is considered. This is used to scale the effect of runs scored by generating a "runs ratio".

If the second innings is incomplete (the first always will be), an estimate of the final score they would have achieved must be made, to do this the lower total of that assuming overs were the limiting factor or that assuming wickets were the limiting factor is taken:
Total if overs were the limiting factor = Score * (120/balls used)
Total if wickets were the limiting factor = Score * R (R defined from table below)

Code: Select all

Wickets lost: 0     1     2     3     4     5     6     7     8     9     10     
Ratio:        100   6.00  3.00  2.04  1.60  1.36  1.21  1.13  1.06  1.03  1


For the purposes of our calculations, we assume the average total runs scored in a match is 300.

Strike rate ratio
The strike rate ratio is calculated using the actual totals and balls faced, simply 100*runs/balls.

For the purposes of our calculations, we assume that 127 runs per 100 balls is the average strikerate for batsmen.

Strike rate bonus/penalty table
Strike rate bonuses are multiplative to the runs scored and calculated from adjusted strike rates.
Adjusted strike rates are calculated by the players strike rate * strike rate ratio.
For example, if a batsman scored 45 from 67 balls, he would have an adjusted strike rate of ( (45/67) * 1.42) = 95.4.

The percentage bonuses/penalties applied are as follows:

Code: Select all

Adjusted strike rate <40         40-64.99    65-89.99    90-104.99  115-139.99  140-164.99 >164.99   
% bonus             -30%             -20%        -10%            0        +10%        +20%    +30%


Milestone points
For scores >=100, 40 bonus points
For scores 50-99, 20 bonus points
For scores 25-49, 10 bonus points
Dismissed, -10 points
Dismissed for a duck, -10 points (so a duck scores -20)
For each six hit, 4 points.

Bowling Points

Points for each wicket
Each wicket scores points based on the batting order position of then batsman dissmissed with this table:

Code: Select all

Batting position:  1  2  3  4  5  6  7  8  9 10 11
Points scored:    33 33 31 27 22 17 13 10  7  5  3


Milestone points
Bonus points are allocated for the number of wickets taken as follows:
2 wickets = 10 points
3 wickets = 20 points
4 wickets = 40 points
5+ wickets = 60 points

Economy points
Points are awarded for economy rate as follows assuming at least 3 complete overs are bowled by the bowler.

Code: Select all

Econ rate: <2.6rpo | 2.6 - 4.59 | 4.6 - 6.59 | 6.6 - 8.59 | 8.6 - 10.59 | 10.6 - 12.59 | > 12.59
Points:         40           20           10            0           -10            -20       -40


Finally, there is a 10 point bonus for each maiden over.
These are added together to gain the total bowling score.

Fielding Points

Catch by keeper or fielder: 10 points
Stumping by keeper: 10 points
Runout by keeper or fielder: 10 points

[darkmatter]

What about teams who reverse the order, or who play their best batsmen at 4,5 and 6.

Surely a better method would be to (using the calculation to work out a batsman summary) - rank them by ability.

So a batsman who rates accomplished(64/100) could be the top, followed by accomplished (22/100) then reliable (98/100)

the (*/100) is just a numerical representation of how close they might be to the next summary - which assuming the summary is worked out by number - then visualised by a word - is the way it is calculated.

I agree with the rest though.

[RightArmOver]

I often play a bat at 7 and an all rounder up the order in my vain attempts to stop collapsing.

[ChodaBoy]

Mostly good barring:

Economy points
Points are awarded for economy rate as follows assuming at least 3 complete overs are bowled by the bowler.

Code: Select all
Econ rate: <2.6rpo | 2.6 - 4.59 | 4.6 - 6.59 | 6.6 - 8.59 | 8.6 - 10.59 | 10.6 - 12.59 | > 12.59
Points: 40 20 10 0 -10 -20 -40

This seems very strange. The intervals between amounts of points are far too large IMO.

2.7 rpo is stunning while 4.5 is decent, but both get the same points. Likewise, a decent 4.7 earns no more points than 6.4 which under most circumstances would be rubbish.

From there, the pitch type (and possibly bowler type thereon) surely has to be taken into account. I've had bowlers with spells at 6.3 rpo contribute to a win on a Flat, and some cost me a game with 5.1 rpo on a Sticky or Crumbler. It doesn't make sense to award the same economy rates the same points across all pitch types.

Bowler type may be complicating things too far, but might recognise the contributions that spinners sometimes make on a Green/Hard/Flat and ditto for seamers.

[Baggygreen]

What about teams who reverse the order, or who play their best batsmen at 4,5 and 6.

Surely a better method would be to (using the calculation to work out a batsman summary) - rank them by ability.

So a batsman who rates accomplished(64/100) could be the top, followed by accomplished (22/100) then reliable (98/100)

the (*/100) is just a numerical representation of how close they might be to the next summary - which assuming the summary is worked out by number - then visualised by a word - is the way it is calculated.

I agree with the rest though.

Agreed, and brought this up previsously. The rest is fine as it takes into account match conditions and what actually occurred, whereas batting line-up is no way always reflective of batting skill. It should be (IMO) based on the batsman's actual skill, although that was knocked back due to it then revealing that skill to the opponent. Batting average might be a better method though (if possible), with so many points for dismissing a batamsn with avg<10, avg<25, avg <40 and 40+.

[darkmatter]

I think looking at wages you could often work out the "best" batsmen anyway..

I still don't know why a pinch hitting AR or tailender should be rewarded more points than getting out a tough,stable 6 or 7...

[R0b1et]

What about teams who reverse the order, or who play their best batsmen at 4,5 and 6.

Surely a better method would be to (using the calculation to work out a batsman summary) - rank them by ability.

Can you see that on the scorecard?
Also I'll point out it is factored in... the points are weighted by the average score by batsmen in that position. So, you playing your bats in a "funny order" weighted down the points for high batting and up for lower batsmen.

[FTP-ashario]

I think looking at wages you could often work out the "best" batsmen anyway..

not if that batsman can bowl or keep

i'm dead against player skill levels and/or wages being some sort of multiplier used to award points. i think it raises more problems than it solves.

[ChodaBoy]

I agree, it would further encourage the already rampant development of primary whores.

[GKZhukov]

How come batsmen score points on runs/strike rate relative to the overall runs/strike rate in the game, but bowlers points don't take into account the average economy rate?

Also do fantasy points actually affect anything besides being a rather nice addition to the game/sort of generating MoM awards?

[R0b1et]

How come batsmen score points on runs/strike rate relative to the overall runs/strike rate in the game, but bowlers points don't take into account the average economy rate?

testing... this seemed significantly more reliable. Economy points are small in comparision to significant wickets... it will be rare to see a player gain MotM due to economy.