> For the complete documentation index, see [llms.txt](https://help.diarkis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.diarkis.io/en/diarkis-client/samples.md). # Samples **Diarkis Samples** provide a collection of reference implementations demonstrating how to integrate and utilize various Diarkis modules within real-time applications. These examples cover key features such as **matchmaking, session management, room communication, object synchronization, P2P connectivity**, and more. Each sample is designed to showcase **best practices**, offer **step-by-step guidance**, and accelerate development by providing **ready-to-use code** in supported languages like **C++, C#. The samples are provided in both Unity, and Unreal Engine**. Ideal for developers seeking to quickly understand and implement Diarkis' capabilities in real-world scenarios. --- # 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.diarkis.io/en/diarkis-client/samples.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.