> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/other-integrations/roblox.md). # Roblox Integrating Convai character chatbot services in Roblox game. ## Overview Roblox is an online game platform and game creation system developed by Roblox Corporation that allows users to program games and play games created by other users. This provides a perfect platform to develop games with intelligent AI-based NPCs with which the player can interact and experience a new way of story progression or gameplay altogether.
## Constraints Roblox environment doesn't support many essential features required to enjoy the power of the character API endpoints to their full potential. {% hint style="warning" %} Roblox doesn't allow the creation of audio files {% endhint %} We cannot utilize the audio response from Convai as there is no easy way to create an audio file and play it within the game. {% hint style="info" %} Roblox doesn't allow microphone access {% endhint %} We cannot record audio from the user and pass that directly to the server for processing and generating a response. We are limited to sending only text data through the request body and receive and display only text-data from the response. --- # 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.convai.com/api-docs/plugins-and-integrations/other-integrations/roblox.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.