> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2022/2022.21.0-december-5-2022.md).

# 2022.21.0 - December 5, 2022

### Bugs/Cases

* DEV-569 Updated at/Updated by not correctly updating when specific things in an asset were changed
* DEV-561 Some models breaking the player on rotate
* DEV-668 Name option for configurators not displaying in AR
* DEV-681 Migration request not correctly throwing an error when it is unsuccessful
* DEV-717 Composite Layer Group Targets disappearing
* DEV-751 2D player being stuck in loading after initialization
* DEV-757 Items being able to be accessed even after being deleted
* DEV-760 Loading a Saved Configuration doesn't load the full configuration
* DEV-763 Translation/Localization is not translating some attribute values
* DEV-780 Unable to add rules to a composite asset
* DEV-784 Not redirecting automatically after signing in while launching AR Task


---

# 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://community.threekit.com/releases/2022/2022.21.0-december-5-2022.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.
