> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/features/release-notes/2023/06-6-june-update.md). # 06-6 June Update v0.5.4398 / 6 June 2023 ## ⏫ Minor Improvements * 📝 We've made the "is in list" and "is not in list" rule events case insensitive for a more user-friendly experience. * 🚫 We've removed userguiding to streamline the editing process. * 🎮 We've added a pitch range for 3D scenes to give you more control over your 3D environment. * 👾 We've made cosmetic changes to the AI character element to enhance its visual appeal. ## 🐛 Bug Fixes * 🐞 We've fixed the background clipping for the text element (without background) to ensure a seamless viewing experience. * 🔄 We've fixed the point to action while moving between different scene types for smoother transitions. * ✅ We've fixed the close button clickability for popups for better user interaction. * 🔒 We've fixed the access issue for the leaderboard page while logged out to ensure secure access. * 🔄 We've updated the Agora version for improved performance. * 🔄 We've updated project calls for both client and server for better synchronization. --- # 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.gmetri.com/features/release-notes/2023/06-6-june-update.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.