There's probably a similar issue in that Davey is being over-rewarded for taking McPeake's wicket in the 2nd innings. The irony being McPeake was Wellington's top scorer, but still.
- not sure I can think of a way around this issue using the current scoring model.
The issue here is the different points for Batsmen 1-5, 6-7 and 8-11 but excluding night-watchmen.
I did think that I could use the 1st innings as the default batting line up, but there's still a chance of a night-watchman there.
Then, from one game to the next, someone like McPeake (who is at best a reasonable #9) could end up being #7 due to a combination of electoral lunacy and the selection of players like Snedden, McComb etc. So, from one game to the next, McPeake could go from being worth 12 to 21 points.
This is the sort of non-logical, human-led thing where Excel sucks. Two alternatives would be:
1. Create a data table listing whether each player is top order, middle order, tail ender. In this case, regardless of place in the batting order, McPeake would always count as tail ender. The downside is having to add new players to the database and the lack of clarity over some players' roles (e.g. Georgeson could be opening, could be down at #7/8)
2. Use FC batting averages as a proxy. Say, if you have an average <15 at the start of the season, you're a tail ender. <30 & >15 then 'middle order' and >30 top order. Problems here are small sample sizes for some players, new players having no average at all but would recognise a wicket's value based on a (somewhat flawed) measure of a batsman's quality.
Obviously changing to either of these mid-season isn't workable, but something to think about in the future.
For now, it probably means an extra manual adjustment for the scorer. At least it should only be 3 adjustments
1. Blunter's Bonus
2. Spinner's Parsimony Bonus
3. Adjust value of wickets taken when batting line-up used a night-watchman
Any other suggestion as an alternative to 1 or 2 above is welcome!