LIGR Studio goes live in --d --:--:--→LIGR Studio is liveStart free trial →

GamePlan Automation/Automation · Event triggers

When a goal goes in, the graphics already know

An operator watching for a goal and reaching for a graphic is a person being paid to have good reflexes. An event trigger removes the reflex from the chain: the fact is logged, the sequence fires, the scoreline comes back updated, and nobody was quick.

Game plan › in game. A goal fires the goal playlist: the goal graphic, a sponsor clip with audio and the replay.

Inside the live gameplay section

Event triggers are configured in the live gameplay section of an automated Game Plan, alongside the time-based content. Each one names an event type and the playlist of graphics that should play when it happens.

The events themselves come from the match data: a fact logged in the LiveScore App, or a feed from a data provider. The automation does not watch the pitch, it watches the record.

Game plan, in game (live). The goal playlist with its trigger, and the sequence it fires.

The sequence everyone judges you on

01

The celebration fires

A goal animation, typically three to five seconds. It goes first because it plays while the crowd is still reacting, and being late with it is worse than not having one.

02

The scoreline returns

The scoreline graphic follows with its goal display enabled, carrying the updated score and the scorer. How long it holds is yours to set.

03

It takes priority

Goal-triggered content outranks time-based content, so a sponsor rotation mid-play does not get to sit on top of a goal. The whole sequence typically runs eight to fifteen seconds.

Game Plan preview: a goal fires the celebration, then the scoreline comes back updated. Demo data.

Cards, subs and milestones

Cards

Separate graphics for yellow, red and a second yellow, each firing when the card is logged. Keep them to five to eight seconds so they clear before the next thing happens.

Substitutions

Outgoing and incoming player, number and team, on screen for a configurable duration. The most common graphic in a match and the one nobody wants to call manually.

Milestones

Fire on the third card or the fifth substitution rather than on every one. Good for a summary graphic that would be noise if it played each time, and for sponsor content tied to a recurring beat.

Milestones sit in the middle of the priority order by convention: below goals, above time-based advertising. Configure two overlapping patterns on the same event type and only one fires, so a third-card and a sixth-card rule do not both land on the sixth.

The same preview with a yellow card: its own graphic, its own hold time. Demo data.

Two things happen at the same time

Sport does not queue politely. A substitution goes in while a card is being shown, a goal follows a corner by four seconds, and without a rule for it the graphics pile on top of each other.

Every event type carries a priority level, and a higher-priority event interrupts lower-priority content rather than waiting behind it. Goals sit at the top by convention. A routine substitution waits.

This is the part worth testing rather than assuming. The simulation mode in a Game Plan fires sample events so you can watch the ordering behave, and simultaneous events are exactly where an untested priority setting shows up: on air, once, in front of everyone.

Questions

The match record. A fact logged in the LiveScore App or arriving from a data feed is what fires the trigger. The automation reads the record rather than watching the video.

Put your next match on air

Tell us about your competition and we’ll show you how it looks with LIGR.