> For the complete documentation index, see [llms.txt](https://docs.monaverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monaverse.com/create/resources/asset-resources/3rd-party-assets.md).

# 3rd Party Assets

This page will go into the details of 3rd Party Assets in Unity...

Generally speaking, using 3rd Party Assets from the Unity store in your space is not recommended unless you know that the license allows the use of it and that the asset will work.

There are mainly two types of assets that you may purchase : assets that help you use Unity, and assets that you can populate your space with.

The area that makes these assets difficult is that some assets will be included with the Mintable File at the moment, which creates licensing issues. This applies to both Unity and Asset based assets, and is the main reason we do not recommend using them unless specifically allowed.

#### Compatible

* Amplify Shader Editor (Make sure to remove references to Amplify)

#### Semi - Compatible

* Bakery (Owner would need asset to utilise Mintable file)

#### Not Recommended

Some Assets do not work with the current Mintable Asset building process. The following have been found to be unuseable for the time being.

* L(ux) Water (Resets to default settings on importing asset with purchased asset)
* Bakery *Shaders* (the baking itself works great!)
* TirGames Assets (Shader issues, 'may' work if assets are purchased by owner or shaders are exchanged with Mona compatible ones)
* MTree -  Tree Creation (Shader dependency issues)


---

# 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.monaverse.com/create/resources/asset-resources/3rd-party-assets.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.