Understanding Why Averages Aren't Updating Correctly

Understanding Why Averages Aren't Updating Correctly
If your league requires bowlers to use their book (or entering) average for a certain number of games, you might notice that even after they've completed those games, the average shown still reflects their book average rather than their current performance. This could be due to a setting called the "pin-drop rule."

What Are the Two Rules That Might Affect Averages?

  1. Minimum Average Rule:
    • This rule ensures that a bowler's average doesn’t drop below a certain number. For example, if you don’t want any bowler’s average to go below 140, you set this rule to 140.
  2. Pin-Drop Rule:
    • This rule limits how much a bowler’s average can drop from their initial book average. For example, if your league rules say a bowler’s average can’t drop more than 10 pins from their book average, you set this to 10.

Common Issue: Setting the Pin-Drop Rule to Zero

Sometimes, a league might set the pin-drop rule to zero, thinking this prevents the average from dropping at all. But in reality, it means the bowler’s average can't drop even one pin from their book average, so it stays stuck on that book average.

The Fix

If you don't need this strict limit, it's best to set the pin-drop rule to 99. This way, the bowler’s average can naturally adjust based on their current performance after they've completed the required games.