> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/developer/player-control/player-control.md). # Player Control Xibo Players receive their instructions for what to play from the CMS, they download everything they need and then run through the instructions rendering output to the screen. A lot can be achieved using this standard functionality, particularly when combined with the more advanced embedded/HTML package Widgets. However, in this mode of operation screens are limited when it comes to interacting with their local environment. Xibo has several tools available to connect displays to their environment and to each other. ## Interactivity Starting in Xibo v3, an interactive control component has been introduced to allow a screen to fully interact with its environment through: * **Touch**: physical interaction with the screen, usually via a touch screen or mouse * **Web hooks**: software interaction with the screen via `http` request, usually from another device or service Interactive control also allows for more advanced usage of the embedded/HTML package options through the “interactive control” JavaScript library. This library provides method for getting player information and controlling the duration of Widgets. ## Real time data Starting in Xibo v4.1, a Data Connector component has been introduced to allow a player to connect to a data source, serial/network device or sensor, and display data from that source in real time. ## Schedule Criteria Starting in Xibo 4.1, players can be made aware of their environment via metrics such as “weather: current temperature” and have their schedule adapt in real time based on these metrics. Schedule Criteria can also be set via a Data Connector and/or API call enabling the player to be fed local, real time conditions. --- # 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://docs.xibosignage.com/developer/player-control/player-control.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.