Event slots: a step-by-step setup guide

Before you touch the settings

1. Open Events, filter to the intended service/account and refresh its catalogue.
2. Confirm the account sees the intended competition and can play one currently available event. Check its assigned region/proxy if required.
3. Set the operational time zone in Settings → App; keep server time synchronized.
4. Decide whether you want one feed per match, multiple team/network feeds, or dedicated team channels. Begin with a small pool.

1. Open the right modal

1. Go to Content → Services and find the service.
2. Click its Service Outputs action.
3. Under Event Slots, enable Enable stable event slots. Do not recreate a working set just to rename its channels.
4. Review existing assignments before changing the slot count, rules or output token.

2. Start with eight numbered event channels

1. For each row leave Rule on Auto daily slot and Feed preference on Automatic / any.
2. Choose the desired Source account policy; use one known working account for the first test.
3. Save. Reopen the modal and inspect the assigned event, source account and any scan diagnostics.
4. Copy the generated Event M3U URL from the output section. It is a playlist; open it in a compatible player.

3. Understand every slot-row field

Comma/newline terms are separate search terms. Avoid broad overlapping rules until you have inspected their matches. Regex is for experienced operators and does not create missing provider metadata.

4. One M3U with NHL and NFL groups

1. Choose a total pool size suitable for the peak simultaneous games/feeds, for example 16 slots split into two pools of eight.
2. Name slots 1–8 NHL 01…NHL 08. Set Rule to Competition, Rule value to the actual NHL competition name, and Playlist group to NHL on all eight.
3. Name slots 9–16 NFL 01…NFL 08 and use the actual NFL competition and group NFL.
4. Keep the rules, account policy, feed policy and priorities identical inside each pool unless you deliberately need different behavior.
5. Leave duplicate rule matches off. Save and confirm NHL rows contain only NHL candidates and NFL rows only NFL candidates.
6. Use the generated service events M3U: compatible players show the groups in one list.

For separate subscriber playlists, create separate collections/packages granting the intended slot pools and use their generated Access Line details. Do not invent an undocumented league filter on the operator playlist URL. Collections organize permissions; Playlist group only organizes labels.

5. Automatically map home, away and national feeds

1. Set Broadcast mapping to Primary team & network TV feeds for ordinary identified team/network productions.
2. Leave per-slot Feed preference at Automatic / any. You do not have to create a Home and Away rule for each match.
3. Allocate enough slots for the distinct feeds you want. Eight simultaneous games can need sixteen outputs for home plus away, with capacity for any additional wanted national feeds.
4. Use All available TV feeds only when you also want discovered special presentations. Use a strict per-row role only when a channel must wait for that exact role.
5. Review pending feed discovery, unclassified games and unassigned broadcasts. A provider Automatic entry can remain a fallback until specific feed IDs are known.

6. Choose account pins or balancing

Account copies of one identified broadcast are not extra games. Distinct Home/Away/network feeds can still be separate assignments. Leave deliberate duplicates disabled for unique numbered pools. Balancing concerns event assignments, not proxy bandwidth, all saved channels or an inferred provider quota. Each account still needs the appropriate content rights.

7. Optional same-event account recovery

Enable Same-event account failover only on slots where you want conservative cross-account recovery. It is off by default. The primary pin/balancing policy remains the policy for the next game.

• Requires fresh, repeated confirmed authentication/account/entitlement failure; a healthy current output wins over an old error.
• Requires another active permitted account with an equivalent live provider event, verified feed and language identity, and compatible output tracks.
• Does not treat a generic CDN 401/403, rate limit, timeout, DRM failure or missing catalogue entry as sufficient account-failure evidence.
• Runs from normal catalogue refresh/recovery observations, not instant or gapless switching. Some players must reconnect.
• Preserves the stable slot URL and has no automatic mid-game failback. It does not migrate independent UDP/RTMP/SRT outputs.
• Excludes on-demand runtimes, manual stops and unarmed empty slots. Review the current assigned account and last recovery attempt in the row.

8. Make eligible events start automatically

1. Turn on Auto-start eligible upcoming events by default in Service Outputs and save.
2. Enable Server Auto-Start on the Events page.
3. Inspect the event’s armed state and slot assignment. With slots enabled, defaults arm assigned events—not every live item in the provider catalogue.
4. Confirm the processing host, source routing, rights and capacity are ready. Start one available event and verify its generated slot URL.
5. Check Logs and scheduler diagnostics for a missing automatic start; do not change every account or disable retry protections blindly.

On-demand startup and proactive auto-start serve different purposes. The default auto-start switch turns off conflicting on-demand mode. Explicitly armed individual events remain independent of slot-default arming.

9. Choose Rolling or week locking for recording

1. Enable Include assigned events in subscriber XMLTV.
2. Grant the desired slots and Events/XMLTV outputs through the subscriber’s collection/package.
3. Copy the Access Line’s generated XMLTV URL into the recording client and refresh it.
4. Verify the exact slot tvg-id, programme start/end and client time zone before scheduling.
5. Keep the guide refreshed. Missing/estimated times or unpublished feed IDs cannot provide a trustworthy advance recording reservation.

Enabling XMLTV or multiple feeds does not force Rolling mode to lock. A static channel name also does not freeze which game owns that slot.

10. Verify and protect the outputs

Use generated links from the modal or Access Line. Do not share operator tokens publicly or replace them with captured provider manifests. Regenerate URLs invalidates older service links and can break downstream clients. A stable URL is not a zero-interruption guarantee.

When the result is not what you expected