A Theme Instance is a customer-level configuration of a Theme, assigned at the Competition overlay level. Because a Competition can have multiple overlays, each with its own Theme Instance and Game Plan, you can produce different graphic outputs (for example, a full broadcast feed and a scoreboard-only feed) from the same Competition.

​

Themes are platform-level and built by the LIGR team. Once a Theme has been made available to your organisation, you create a Theme Instance to configure how that Theme behaves for a specific Competition overlay.

​

Key distinction:

​

• Theme: the overall look, feel, and graphic package. Built and maintained by the LIGR team.

​

• Theme Instance: your saved configuration of a Theme, assigned to a Competition overlay, with its own settings and linked Game Plan.

​

A single Competition can have multiple overlays, and each overlay has its own Theme Instance and Game Plan. This is what makes it possible to output more than one graphic package from the same Competition at the same time, for example:

​

• A full media stream with on-screen graphics, lower thirds, and full-screen content

​

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

​

• A sponsor-focused version configured for a specific broadcast partner

​

Make sure you have:

​

• A Competition already created in the Assets tab

​

• A Theme assigned to your organisation and available to select

​

• A clear idea of which graphics and Game Plan you want each overlay to use

​

[ Image placeholder: The Assets tab showing the Competitions section with a Competition selected ]

​

1. Go to the Assets tab.

​

2. Select Competitions.

​

3. Click into the Competition you want to configure.

​

1. Go to Settings within the Competition.

​

2. Open Streams and Overlays, then Overlay Settings.

​

3. You will see any overlays already configured for this Competition, each with its assigned Theme Instance.

​

[ Image placeholder: The Overlay Settings page within a Competition showing existing overlays and their Theme Instances ]

​

1. Add a new overlay, or edit an existing one.

​

2. Give it a clear name that describes its purpose, for example "Main Broadcast" or "Scoreboard Only".

​

3. Select the Theme you want this Theme Instance to be based on.

​

4. Save the overlay to create the Theme Instance.

​

Once created, configure the Theme Instance with:

​

• The default graphics and configuration options exposed by the Theme

​

• A Game Plan or Automated Game Plan linked to this overlay

​

• Playlists that fire on match events for this overlay

​

• Any configuration values the Theme exposes for customisation

​

Because the Game Plan is attached at the overlay level, each Theme Instance within the same Competition can have its own playlists, priorities, and event-triggered behaviour.

​

[ Image placeholder: Configuration view of a Theme Instance showing default options and linked Game Plan ]

​

When a Match is created under this Competition, each configured overlay produces its own output using its assigned Theme Instance and Game Plan. This lets you run multiple outputs from the same Match, each with a different graphic package.

​

• Name your overlays and Theme Instances clearly so they are easy to identify.

​

• When setting up secondary outputs like a scoreboard-only feed, start from the configuration of your primary Theme Instance and reduce graphics from there.

​

• If you produce for multiple broadcasters or destinations, create a dedicated overlay and Theme Instance for each so sponsor content and graphic choices remain separate.

​

• Confirm each Theme Instance outputs correctly before going live.

​

• Graphics appear on the wrong output: check that each overlay has its own Theme Instance, default graphics, and Game Plan configured, rather than sharing them.

​

• Theme Instance not available on a Match: confirm the overlay is configured under the correct Competition.

​

• Changes not showing: refresh the output after editing the Theme Instance, as cached configuration may need to reload.

​

• Only one output is updating: verify that each output is pointed at the correct overlay, not the same one.