Incidents: Cricket

Owned by Former user (Deleted)
Last updated: 23.09.2024 by Wojciech Augustyn
4 min read

As STATSCORE, we distinguish several types of incidents that our Scouts use in the process of providing coverge for a given sport event. Each of these incidents is briefly described and included in the relevant table.

 

  1. Event incidents - their use directly influences the change in match statuses or triggers specific parts of the match. Match statuses are described in a separate section - “Statuses: Cricket”.

 Id

Incident name

Is important for trader

Affect on statuses

Affect on results/statistics

Note

 Id

Incident name

Is important for trader

Affect on statuses

Affect on results/statistics

Note

1701

1st innings home started

yes

set “1st innings home” status

Result = 0

Regular time = 0

First inning runs = 0

First inning wickets = 0

 

1702

1st innings away started

yes

set “1st innings away” status

Result = 0

Regular time = 0

First inning runs = 0

First inning wickets = 0

 

1705

Super Over home started

yes

set “2nd innings home” status

Super Over runs = 0

Super Over wickets = 0

Super Over Overs = 0

 

1706

Super Over away started

yes

set “2nd innings away” status

Super Over runs = 0

Super Over wickets = 0

Super Over Overs = 0

 

1708

Innings break

yes

no

no

 

1713

Super Over Innings break

yes

set “Super Over Break” status

no

 

803

Cancelled

yes

set “Cancelled” status

no

 

805

Postponed

yes

set “Postponed” status

no

 

802

Interrupted

yes

set “Interrupted” status

no

 

807

Abandoned

yes

set “Abandoned” status

no

 

1715

Finished

yes

set “Finished” status

no

 

1716

Finished after Super Over

yes

set “Finished after Super Over”

no

 

818

Live

no

set “Live” status

no

Not used in the ScoutsFeed product

819

After day 1

no

set “After day 1” status

no

Not used in the ScoutsFeed product

820

After day 2

no

set “After day 2” status

no

Not used in the ScoutsFeed product

821

After day 3

no

set “After day 3” status

no

Not used in the ScoutsFeed product

822

After day 4

no

set “After day 4” status

no

Not used in the ScoutsFeed product

 

  1. Team Incidents: Incidents whose use directly impacts on results and team/player statistics. Results and statistics are described in a separate sections - “Results: Cricket” and “Statistics: Cricket”

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

1756

Bowler running in

no

 

 

 

 

1767

Possible Boundary

yes

 

 

 

 

1770

Possible wicket

yes

 

 

 

 

1717

Retired hurt

no

 

 

 

 

1773

Dead ball

no

 

 

 

 

1774

Free hit

yes

 

 

 

 

1775

One short

no

 

 

 

 

1781

Extras - Penalty runs

yes

 

  • 1

  • 2

  • 3

  • 4

  • 5

 

 

1784

Batsman coming in

no

 

 

 

 

1785

Bowler change

no

 

 

 

 

1786

Batsman retired

no

 

 

 

 

1788

Duckworth-Lewis method

yes

 

 

 

 

1792

Start of over

yes

 

 

 

 

1791

End of over

yes

 

 

 

 

2744

Dismissal - LBW

yes

 

 

 

 

2745

Dismissal - Caught

yes

 

 

 

 

2746

Dismissal - Bowled

yes

 

 

 

 

2747

Dismissal - Run out

yes

 

 

 

 

2748

Dismissal - Stumped

yes

 

 

 

 

2749

Dismissal - Hit wicket

yes

 

 

 

 

2750

Dismissal - Handled the ball

yes

 

 

 

 

2751

Dismissal - Obstructing the Field

yes

 

 

 

 

2752

Dismissal - Hit the ball twice

yes

 

 

 

 

2754

Out

yes

 

 

 

 

2755

Legal ball

yes

 

  • Runs

  • Boundary 4

  • Boundary 6

  • Byes

  • Leg Byes

  • Wicket

  • 0

  • 1

  • 2

  • 3

  • 4

  • 5

  • 6

  • 7

  • 8

  • 9

 

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

2756

Illegal ball

yes

 

  • Wides

  • No ball

  • No ball + Bat

  • Wicket

  • 0

  • 1

  • 2

  • 3

  • 4

  • 5

  • 6

  • 7

  • 8

  • 9

 

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

2757

Timed out

yes

 

 

 

 

2758

Penalty

yes

 

  • Player returning without permission

  • Fielding the ball illegally

  • Ball in play hitting helmet

  • Match ball changing condition unfairly

  • Deliberate distraction of batsman

  • Deliberate attempt to distract striker

  • Time wasting by fielding side

  • Fielder causing damage to pitch

  • Failing to bowl overs in give time

  • Batsman stealing a run

  • Deliberate short run

  • Batsman wasting time

  • Batsman causing damage to pitch

 

 

 

  1. Informing incidents - incidents that can pertain to the entire match or a specific team but do not affect any statistics.

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

806

Start Delayed

yes

 

 

 

 

2739

Match about to start

yes

 

 

 

 

2759

Toss won

yes

 

 

 

 

2760

Batting team

yes

 

 

 

 

1001

Match resumed

yes

 

 

 

 

830

To finish

yes

 

 

 

 

2761

Break in play

yes

 

  • Rain

  • Injury

  • Bad light

  • Drinks

  • Tactical timeout

  • Other

 

 

 

 

 

 

 

 

 

 

  1. Incidents related to managing match markets - incidents where their use causes specific match markets to be closed or opened.

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

 Id

 

Incident name

Is important for trader

Participant

Add info possible values

Add info format

Note

1000

Betstart

yes

 

 

 

Betstart indicates that betting markets can be activated

1010

Betstop

yes

 

 

 

Betstop indicates that all betting markets are closed due to strong possibility of runs, wickets, etc.

1783

Decision review

yes

 

  • Retained

  • Lost

 

 

1200

Technical problems

yes

 

 

 

Indicates technical issues during the providing of the coverage and automatically closes all match markets