Theme Instances let you run different graphic output configurations from a single Competition, so you can deliver multiple versions of your broadcast (for example, a full-graphics stream and a scoreboard-only stream) from the same match without duplicating your automation work.

​

A Theme Instance is a customer-level configuration of a Theme. Theme Instances are assigned at the Competition overlay level under Competition, Settings, Streams and Overlays, Overlay Settings. A Competition can have multiple overlays, each with its own Theme Instance and its own Game Plan.

​

Common use cases include:

​

• A full-graphics overlay for your main media stream (persistent score graphics, lower thirds, sponsor loops, lineups)

​

• A scoreboard-only overlay for radar, IMG, or secondary distribution

​

• Separate overlays for different broadcast partners who require different branding

​

[ Image placeholder: Overlay settings panel within a Competition showing multiple configured Theme Instances ]

​

Before you begin, make sure you have:

​

• A Competition with a Theme assigned by the LIGR team

​

• A Game Plan built for the overlay you are configuring

​

• A clear plan for which graphics should appear on each output

​

1. Navigate to the Competition in LIGR Live.

​

2. Go to Settings, then Streams and Overlays, then Overlay Settings.

​

3. Review the overlays already configured, or add a new overlay for the output you want to produce.

​

1. On the overlay, select the Theme Instance you want to use.

​

2. Give the overlay a clear name that describes its purpose (for example, "Media Stream" or "Scoreboard Only") so it is easy to identify.

​

3. Save the overlay configuration.

​

[ Image placeholder: Overlay configuration with Theme Instance selection and name field ]

​

Each overlay runs its own Game Plan. The Game Plan holds the Pre-Game, Live gameplay, and Post-Game sections that drive automation for that output.

​

1. Assign the Game Plan you want this overlay to use.

​

2. For a scoreboard-only overlay, choose or build a Game Plan that contains only the playlists relevant to that output.

​

3. For a full-graphics overlay, assign the Game Plan that contains your complete set of playlists.

​

Playlists sit inside one of three sections:

​

• Pre-Game playlists run before kick-off and typically cover lineups, matchup graphics, and sponsor content.

​

• Live gameplay playlists run during the match and include event-triggered content as well as time-based or manually started sequences.

​

• Post-Game playlists run after the final whistle and typically cover final score, player of the match, and wrap graphics.

​

Event-triggered playlists fire automatically when a Match Fact is recorded. The standard triggers are:

​

• Goals (and goal-related facts such as assists)

​

• Cards (yellow, red, and any other card types defined for the sport)

​

• Substitutions

​

• Period changes (start and end of halves, quarters, or periods)

​

Each playlist has a priority value set within its Game Plan. When two playlists could fire at the same time, the higher priority playlist wins. If two playlists share the same priority, the one that was built first fires.

​

Event-triggered playlists often display information about a specific player (for example, the scorer on a goal graphic or the player being substituted). If that player data is missing or incomplete in the Match Fact, a graphic can render with blank fields.

​

To prevent this, build guard logic into the playlist so it only plays when the required data is present. Typical guards include:

​

• Only play the scorer graphic if a scorer is assigned to the goal

​

• Only play the card graphic if a player is attached to the card

​

• Only play the substitution graphic if both the player on and player off are set

​

• Fall back to a simpler graphic (such as a team-only goal notification) when player data is missing

​

This keeps your automated output clean when operators or data feeds do not provide full detail on every Match Fact.

​

1. Open a test Match for the Competition.

​

2. Check the output for each overlay independently using its Monitoring Link.

​

3. Record sample events (such as a goal with a scorer, a goal without a scorer, a card, a substitution, and a period change) to confirm the right graphics appear on the right overlay and that guards behave as expected.

​

• Name your overlays and Theme Instances clearly so the purpose of each output is obvious.

​

• Keep a scoreboard-only overlay's Game Plan minimal: typically just the persistent score graphic plus any cards, stoppage, and substitution indicators it needs to reflect.

​

• Use separate Monitoring Links for each overlay to verify outputs independently before going live.

​

• Review playlist priorities whenever you add a new event-triggered playlist, so a new addition does not unintentionally override an existing one.

​

• Always add guards to event-triggered playlists that depend on player names or numbers.

​

A graphic appears on the wrong output Each overlay runs its own Game Plan. If a graphic is playing on the wrong output, confirm it exists only in the Game Plan attached to the intended overlay.

​

A scoreboard-only overlay is showing full graphics Check that the Game Plan attached to the scoreboard-only overlay contains only the playlists you want on that output. Playlists from the media Game Plan should not be duplicated into it.

​

An event-triggered graphic renders with blank player fields Add a guard to the playlist so it only fires when the required player data is attached to the Match Fact, or route to a fallback playlist that does not depend on player detail.

​

Two playlists fire at the same time and one is unexpected Review the priority of each playlist within the Game Plan. Remember that when two playlists share the same priority, the one built first wins, so adjust priorities explicitly rather than relying on build order.

​

An overlay has no output Confirm the overlay has a Theme Instance assigned, a Game Plan attached, and that the Monitoring Link or Production Link you are checking points to that specific overlay.