Skip to content

Version 1.2.0.0

Choose a tag to compare

View all tags
@davewalker5 davewalker5 released this 28 Jul 16:07
1.2.0.0
aad53ce
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release expands Cricket Tracker beyond The Hundred with first-class support for Twenty20 and One Day cricket.

Competitions can now use distinct match formats and configurable rulesets while retaining compatibility with existing Hundred data.

Highlights

  • Added built-in match formats for The Hundred, T20 and ODI cricket
  • Added format-aware innings limits and cricket-over displays
  • Added automatic result calculation for standard limited-overs matches
  • Added support for revised allocations, externally supplied targets and DLS-labelled results
  • Added ruleset-driven points and net run rate
  • Extended CSV import and export for limited-overs data
  • Added complete T20 and ODI sample datasets

Match Formats and Rulesets

Match format and competition rules are now modelled separately.

A match format defines the structure of a match, including:

  • Default balls per innings
  • Balls per over or scoring unit
  • Wickets available per innings
  • The way delivery progress is displayed

Competition rulesets continue to define competition-specific behaviour, including:

  • Points for wins, ties, losses, abandonments and no results
  • Whether standings and net run rate are enabled
  • Table sorting order
  • Whether tied results may stand
  • Whether tie-break winners are allowed
  • Whether revised targets may be recorded

This allows different competitions to share a format such as T20 while retaining their own points and standings rules.

Match and Innings Recording

Matches can now record:

  • A scheduled delivery allocation
  • A reduced or revised allocation
  • An original target
  • An externally supplied revised target
  • A result method such as DLS
  • A manual result override and its reason

Innings records now include a completion status, such as:

  • Innings limit reached
  • All out
  • Target reached
  • Declared complete
  • Abandoned
  • Incomplete

Input validation prevents negative scores and wickets, excessive wicket counts, and delivery totals beyond the applicable innings allocation.

Legal deliveries continue to be stored as whole ball counts. T20 and ODI progress is displayed using conventional cricket-over notation, while Hundred matches retain their existing ball-based display.

Automatic Results

Cricket Tracker can derive standard match results from completed innings, including:

  • Wins by runs
  • Wins by wickets
  • Ties
  • No results
  • Abandoned matches
  • Matches decided using an externally supplied revised target

The application records a result method such as DLS but does not calculate DLS targets itself.

Manual result overrides remain available for exceptional cases and are clearly identified in the interface.

Standings and Net Run Rate

League standings now use the selected competition ruleset when awarding points.

Net run rate is calculated from completed innings summaries when enabled. All-out innings use the applicable full delivery allocation.

Matches involving revised allocations or revised targets are excluded from net run rate because their competition-specific treatment cannot be derived reliably from innings summaries alone.

Import and Export

Match CSV files now support these optional fields:

  • scheduled_balls
  • revised_balls
  • target_runs
  • revised_target_runs
  • result_method

Innings CSV files now support:

  • innings_status

Existing Hundred CSV files remain compatible. When allocation fields are omitted, Cricket Tracker uses the default defined by the selected match format.

Self-contained T20 and ODI examples are included under data/samples.

User Interface Improvements

  • Competition, match and innings editors are format-aware
  • Match and innings views show the relevant format and delivery allocation
  • Scores use the appropriate balls or overs presentation
  • Filters support the newly added match formats

Compatibility

Existing Cricket Tracker databases are upgraded automatically when the application starts.

Existing Hundred competitions, matches, innings, imports and standings remain supported. Legacy records are associated with The Hundred format during migration where appropriate.

Supported Scope

Cricket Tracker now supports one-innings limited-overs competitions using:

  • The Hundred
  • Twenty20
  • One Day cricket

The application does not currently support:

  • Test or first-class cricket
  • Matches with multiple innings per team
  • Ball-by-ball scoring
  • Automatic DLS calculation
  • Competition-specific tie-break simulations such as Super Overs
Assets 2
Loading