In LIGR Live, a Game Plan defines which graphics and playlists are available during a match and how they behave. An Automated Game Plan runs those rules automatically based on match events captured in the LiveScore App, so graphics respond to the game without each one being triggered by hand.
This article explains the difference between the two, how playlists and triggers work, and how to structure them for a reliable broadcast.
What is a Game Plan?
A Game Plan is the structured set of playlists that runs alongside a match. It sits on top of an overlay within your Competition, using the Theme Instance assigned to that overlay to determine which graphics are available.
A Game Plan is organised into three sections:
• Pre-Game, for lineups, countdowns, sponsor reads, and match previews
• Live gameplay, for in-match graphics such as goal animations, cards, substitutions, and period transitions
• Post-Game, for final results, player of the match, and summaries
Game Plans can also include ad placements. The way ads are configured depends on the theme type: organisations using inbuilt themes use Ad Allocation at the Competition, Club, or Team level, while organisations using Rive themes configure ads directly inside Automated Game Plan playlists.
[ Image placeholder: Game Plan structure showing Pre-Game, Live gameplay, and Post-Game sections ]
What is an Automated Game Plan?
An Automated Game Plan is a Game Plan whose playlists fire automatically based on Match Facts recorded in the LiveScore App. Instead of an operator cueing each graphic, the system listens for events and plays the correct playlist at the correct moment.
For example, when a goal is recorded in the LiveScore App, an Automated Game Plan can:
1. Play the goal animation playlist
2. Update the on-screen score
3. Return to the standard in-match state
Playlists and Sections
A Game Plan is made up of playlists grouped into the three sections.
Pre-Game playlists
Pre-Game playlists run before kick-off. They are typically time-based or manually started, and are used for:
• Coming-up-next and countdown sequences
• Starting lineups and formations
• Head-to-head stats and match previews
• Sponsor and broadcast intros
Because Pre-Game playlists often reference player data (lineups, starting XI, captains), they should only be built to run once that data is confirmed in the LiveScore App. If the lineup is incomplete, a lineup playlist may render with missing names or empty slots, so use a playlist guard to check that the required data is present before the playlist is allowed to fire.
Live gameplay playlists
Live gameplay playlists run during the match itself and are driven by event triggers on Match Facts. Common triggers include:
• Goals
• Yellow cards and red cards
• Substitutions
• Period changes (start of half, half-time, full-time, extra time)
• Milestone events
Each Live gameplay playlist is tied to a specific event type. When the Live Scorer records that event, the matching playlist is queued to play.
Post-Game playlists
Post-Game playlists run after the final whistle and cover:
• Final score and result graphics
• Player of the match
• Top scorers and match stats
• Sponsor outros and wrap-ups
Like Pre-Game playlists, Post-Game content often relies on player and stat data being recorded correctly during the match, so guards are again important.
Event Triggers and Match Facts
Event triggers are the link between the LiveScore App and your Automated Game Plan. When a Live Scorer records a Match Fact, the Game Plan checks for playlists that listen to that event and fires the highest-priority match.
Typical triggers and their uses:
• Goal: goal animation, updated score graphic, scorer and assist callout
• Yellow card or red card: card graphic with player name and reason
• Substitution: player-on and player-off graphic
• Period change: start-of-period, half-time, and full-time playlists
• Milestone: celebratory graphic for first goal, hat-trick, debut, etc.
Priority and Playlist Guards
Priority
Every playlist in a Game Plan has a priority value. Priority is used to decide which playlist wins when more than one could play at the same time, for example a substitution and a goal arriving close together.
Key points:
• Higher priority playlists take precedence over lower priority ones
• Within a Game Plan, when two playlists share the same priority, the first one built fires
• Set priorities deliberately in Live gameplay so critical moments (goals, red cards) are not blocked by lower-impact graphics
Playlist guards
A playlist guard is a condition on a playlist that prevents it from firing when required data is missing or invalid. Guards are important because Match Facts can be recorded before all the supporting data (player name, number, photo, team affiliation) is complete.
Use guards when:
• A playlist displays a player name, number, or photo that may not yet be filled in
• A lineup or starting XI playlist depends on a full squad list
• A stat or milestone graphic depends on historical data that may not be available
• A card or substitution graphic needs both the player-off and player-on details
Without guards, a playlist may fire with blank fields or placeholder values. With guards in place, the playlist waits until the data is valid or is skipped safely.
Manual vs Automated Operation
A Game Plan can be operated manually or automatically.
Manual operation
Graphics are triggered by hand. This suits productions where:
• A Live Scorer is not capturing Match Facts
• The sport or event type does not use automated triggers
• The producer wants full control over each graphic
Automated operation
Playlists fire from Match Facts captured in the LiveScore App. This suits productions where:
• A Live Scorer is actively capturing events
• You want consistent output across many matches
• You want Pre-Game and Post-Game playlists to run on a timed schedule
• You want to reduce operator workload during fast-paced play
Both approaches can be combined. An Automated Game Plan handles the bulk of the broadcast while an operator steps in for special moments.
Choosing the Right Approach
• Use an Automated Game Plan when Match Facts are being captured live and you want graphics to respond to the game automatically.
• Use manual operation when no Live Scorer is present, or when the production needs full human control.
• Use both together for automated coverage with room for human intervention on special moments.
Tips
• Confirm the Theme Instance on your Competition overlay before building the Game Plan, as it determines which graphics are available.
• Assign priorities in the Live gameplay section so the most important events (goals, red cards) always win over lower-impact events.
• Remember that when two playlists share a priority, the first built fires. Order your builds intentionally.
• Add guards to any playlist that relies on player data, lineups, or stats that may not be present at trigger time.
• Test your Automated Game Plan with a practice match before going live.
Common Issues
Graphics are not triggering automatically Confirm a Live Scorer is actively recording Match Facts in the LiveScore App and that the Game Plan has playlists assigned to the relevant event triggers.
Two graphics are playing at the same time or in the wrong order Review the priority values on the competing playlists. If they share a priority, remember the first built wins, so rebuild or reorder as needed.
A playlist fires with missing player names or blank fields Add a playlist guard so the playlist only fires when the required data (player name, number, lineup entry) is present.
Automation is firing the wrong graphic Check that each playlist is tied to the correct event trigger and that the Theme Instance on the overlay includes the expected graphics.