> For the complete documentation index, see [llms.txt](https://emibergo.gitbook.io/redischat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emibergo.gitbook.io/redischat/readme.md). # Introduction RedisChat is a cross-server chat plugin, designed to make communication between players on different servers seamless. The plugin is also **proxy-less**, meaning it doesn't require any additional proxy plugins RedisChat is based on the powerful **MiniMessage format**, which allows for full **RGB, clickable, hoverable messages**, making your chat experience more interactive and visually appealing RedisChat is also **built for scalability**, making it the **perfect choice for large and growing servers** that require a reliable and efficient chat system Whether you're running a small community server or an extensive network of servers, RedisChat has everything you need to take your chat experience to the next level. --- # 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://emibergo.gitbook.io/redischat/readme.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.