> 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/preview-and-share/pathview.md). # Pathview See every route through your playable as a map of scenes, and jump to any scene while you preview. **Pathview** maps your playable as a flow of scenes, so you can see every route a user can take from the first scene to the end card. It sits beside [Preview](/play/preview-and-share/preview.md), and follows along as the playable runs. Pathview opens with Preview. Click **Hide Pathview** in the header to close it, or **Show Pathview** to bring it back. *** ### Reading the Map Each scene appears as a card with a thumbnail, arranged from left to right in the order users can reach them. Drag the background to pan, and scroll to zoom. Lines connect scenes wherever one can lead to another. Pathview draws a line for: * **Start Scene** and **Start Random Scene** actions on interactions * Each branch of a **Conditional** * A scene's **On Finish** action and scene events * **On Finish** actions on videos, sequences, and games Hover a card to see the scene's name. The scene that's playing in Preview has an orange outline. #### Labels * **Restarts Scene:** the scene can start itself again. * **Restart Ad:** the scene can lead back to the first scene. * **End Cards:** scenes with no way out are grouped in a dashed box, numbered in order. The same number appears under each scene that leads to that end card. * **Isolated Scenes:** scenes no route can reach are shown in a strip at the top. Check these for missing connections. If your project has a [Global Timer](/play/settings/global-timer.md), its progress is shown at the bottom of the panel. *** ### Jumping to a Scene Click any scene card to jump to that scene in Preview. It plays from the start, so you can test a late scene or an end card without playing through the whole playable. * **Your progress carries over.** Progression variables, the global timer, and whether global layers are shown or hidden stay as they were, so the scene plays the way it would at that point. * **Click the current scene** to start it again. {% hint style="info" %} Pathview reflects how your scenes are connected right now. If a scene shows up as isolated or a line is missing, check the actions that should lead to it. Layers hidden in the editor that no action shows don't add lines. {% endhint %} --- # 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/preview-and-share/pathview.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.