> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/layers/scenes/scene-events.md). # Scene Events Scene Events let you trigger actions at specific moments during a scene's timeline. They work like time-based triggers: set a start time, pick an action, and PLAY fires it automatically when the scene's playhead hits that time. Use events to pause a scene mid-playback, trigger audio, update a progression value, launch a CTA, fire a tracker, or run any other standard action at an exact moment during a scene. *** #### Adding an Event In the Scene Properties panel, scroll to the Events section and click the **+** button. A new event module appears with: * A tune icon on the left that opens the Event Properties popup. * A time label and action label in the middle that reflect the event's current settings. * A minus icon on the right for removing the event. The Event Properties popup opens automatically when you add a new event so you can configure it right away. *** #### Event Properties The Event Properties popup has two fields. **Start Time** Sets when the event fires, measured in seconds from the beginning of the scene. The default is 0, which fires the event immediately when the scene starts. The maximum value is the current Scene Duration, so you can't schedule an event past the end of the scene. **Action** Choose which action fires when the event triggers. The dropdown lists all of PLAY's standard actions, including Pause Scene, Start Next Scene, Launch URL, Fire Tracker, Trigger Audio, Update Progression, and more. *Learn more about Actions* [*here*](/play/general/actions.md)*.* *** #### Removing an Event Click the minus icon on any event module to delete it. The event stops triggering immediately, and removed events do not fire again on subsequent playthroughs. *** #### Tips and Best Practices * **Use events for scene-wide logic.** If something needs to happen to the whole scene at a specific time (pausing, launching a CTA, firing a tracker), an event is the right tool. Layer-specific timing still belongs in the layer's animation settings. * **Chain events together to choreograph a scene.** A scene might trigger audio at 2s, pause at 4s, and launch the CTA at 10s. Stack as many events as you need. * **Keep Start Times within the Scene Duration.** If you shorten the Scene Duration below an event's Start Time, the event will never fire. Double-check your event timings if you adjust duration later. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.craftsmanplus.com/play/layers/scenes/scene-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.