> 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/2024/04-05-apr-update.md).

# 04-05 Apr Update

v0.5.5728 / 05 Apr 2024

## ⏫ Improvements

* **Streamlined Avatar System**: Simplified the avatar system to include only three options: Ready Player Me, Custom, and None. Removed the outdated "Basic" avatar system that used conical avatars for a more streamlined experience.
* **Introduction of "Basic" Brain Type**: Added a new "Basic" brain type, allowing users to set the AI prompt directly on the right bar, eliminating the need to select a specific brain.

## 🔐 S**ecurity Enhancements**

* **Enhanced Preview Link Generation**: Revised the method for generating preview links to bolster security measures.
* **Improved Data Encryption**: Updated the encryption process for enhanced data security.

## 🐞 Bug Fixes

* **Mobile - Walking Straight**: Resolved the issue of walking straight on mobile devices using the third-person joystick, ensuring smoother navigation.
* **Character Element Audio Issue**: Fixed an issue related to the Character element audio for improved functionality.
* **3D Asset Loading Bugs**: Addressed several bugs in the loading process of 3D assets utilizing KTX compression, ensuring proper loading and display.


---

# 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/2024/04-05-apr-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.