Automate only what you can verify

Write the sequence before configuring the server

Decide the order, duration and purpose of every cue first. Aplain run sheet is deliberately software-neutral: it reveals whether the plan is too long and gives you a reference when playback behaves differently from the clock.

Then test the smallest useful automated path. One known pre-roll before one known feature is a better first test than a full stack of trivia, trailers, bumpers and lighting actions. Add one transition at a time and note which component owns it.

Plex documents a narrow, practical pre-roll path

Plex's official server Extras settings include a Movie pre-roll video field. The documentation explains how full local paths and two different separators affect one or more files. It also ties playback to Cinema Trailers settings on the server/library and player side. The exact label may vary by app, so thePlex guide keeps the official documentation next to the local test.

Kodi's cinema add-ons need a compatibility check

The official Kodi wiki preserves detailed pages for Cinema Experience and its stated replacement, CinemaVision. They are useful records of sequence ideas: trivia, trailers, bumpers, actions and feature handoffs. Their age is also a warning. A wiki page last edited years ago is not proof that an add-on works with today's Kodi release, skin and operating system.

Use the Kodi research guide to identify what to verify before installation. If the chain is fragile, keep the content as a normal local playlist and follow the manual cues. Reliability is the feature.

Name the owner of every handoff

A repeatable chain has several owners. The server supplies the file, the library or playlist determines order, the player starts playback, the display handles the video mode and the audio route establishes sound. A remote, keyboard or automation rule may be responsible for the next action. Write those responsibilities beside the cue sheet so a failure points to a component instead of to “the pre-show” as a whole.

Test one boundary at a time. First prove that the client can open the file. Then prove the handoff from that file to the feature. Only after both repeat should you add another block or an external action. This order makes troubleshooting slower at the beginning and much faster once the sequence has several parts.

Keep a manual recovery route

Automation should reduce the host's work, but it should not make the feature dependent on a fragile opening sequence. Keep the feature available as a normal library item and know how to start it directly. If a pre-roll, add-on or action stalls, stop the optional chain and use that direct route rather than debugging in front of the room.

Record the client, app version and settings that passed rehearsal. That note is a local baseline, not a claim that the same configuration works elsewhere. Recheck the smallest path after an app, operating-system or hardware change before restoring the complete sequence.