> 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/hotspots.md). # Hotspots A Hotspot layer is an invisible, interactive area on the artboard. Hotspots have no visual content of their own; they exist purely to capture user input like taps, swipes, holds, or drags. Use Hotspots to create tap-to-continue zones, swipe areas, full-screen catch-all interactions, or buttons layered over an image or video. Anywhere you want a user to be able to interact with the playable without needing to draw a visible element on screen, a Hotspot is the right tool Hotspots are intentionally minimal. The Properties panel contains only three sections, all of which are shared across layer types: * **Transform** sets position, size, and alignment, just like any other layer. * **Timeline** controls when the Hotspot becomes active in the scene. * **Interactions** is where the layer earns its purpose. Add taps, swipes, holds, double-taps, or any other gesture, then connect them to actions like Start Next Scene, Launch URL, or Trigger Audio. There is no Animations section, since Hotspots are non-visual and have nothing to animate. #### Notes on Behavior * **Hotspots are invisible at runtime.** In the editor you'll see a dashed outline so you can find and select the layer, but in preview and exported playables the Hotspot itself never renders. Only its interactions take effect. * **Layer order matters.** When Hotspots overlap with other interactive layers, the one on top captures the input. If a Hotspot above a button isn't behaving as expected, check the layer stack. --- # 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/hotspots.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.