> 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/features/join-and-quit-messages.md). # Join and quit messages Customize join and quit messages #### You can customize join and quit messages inside the config.yml based on permissions {% code title="config.yml" %} ```yaml # Use RedisChat for join and quit messages # The quit message will be delayed because it might be an early reconnection to one of the servers using RedisChat enableQuitJoinMessages: true formats: - permission: redischat.default # The rest of the config section ... join_format: %player_name% joined the server quit_format: %player_name% is no longer online ``` {% endcode %} If you're using a communication system based on PluginMessages (not recommended) You will have problems with the quit message sending because of the limitation that PluginMessages have (they need at least a player online to work) If you want to hide join/quit messages from players set them to ```yaml formats: - permission: redischat.default # The rest of the config section ... join_format: "" quit_format: "" ``` ### Permission Use the permission redischat.joinquit ("true" by default) to show join and quit messages --- # 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/features/join-and-quit-messages.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.