> 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/07-23-july-update.md).

# 07-23 July Update

v0.5.4656 / 23 July 2023

## ✨ Improvements

* ⚡ Slight performance improvement in the editor.
* 🔄 Rules can now be rearranged.
* 🛠️ Minor UI fixes in Rules top-bar.
* 🎯 Dragging and dropping in the “Structure” tree is now much smoother.
* 📈 Slight improvement in project size. Initial load times should be slightly faster.
* ⏱️ Precision of video, audio, and timer duration rules is now 250 milliseconds.
* 🤫 Ability to mute all users as the host using a single click.

## 🐛 Bug Fixes

* 💾 Editor changes now consistently get saved, with more efficient diffs generation.
* 🎯 Multiple rules with the same "when" conditions now get triggered as expected.
* 📱 Action bar no longer covers the joystick and caller options on mobile.
* 📋 Duplicate and ghost entries in the "Structure" tab no longer form.
* 📝 Copying and pasting a scene and an element now includes the element in the current scene as expected.


---

# 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/07-23-july-update.md?ask=<question>&goal=<user_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.