> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/apis-and-tooling/dashboard/assets/engine-plugins.md).
# Engine Plugins
Engine plugins are a core concept in Releases. When a Release is created, it must define an Engine Plugin to be bundled with an MSquared editor. The Engine Plugin is then installed directly into the engine when a new Release is installed or upgraded.
## Guides
Create a new Engine Plugin Assets
Engine plugins are uploaded as part of the [Template upload process](/platform-documentation/apis-and-tooling/dashboard/assets/templates.md#create-a-new-template-assets) when they are detected as dependencies of the templates.
To create a new Engine Plugin, follow the template upload process and place engine content within a project plugin of your uproject.
{% hint style="info" %} This guide will follow the template upload process and outline the additional steps required to upload an engine plugin.
{% endhint %}
1. Follow the [Template upload process](/platform-documentation/apis-and-tooling/dashboard/assets/templates.md#create-a-new-template-assets) until you reach step 4.
2. Create a new M2 Library (content-only plugin).\
\
\
\
\\
3. Transfer some of the content from your Template folder into the new Engine plugin content folder.
4. Resume Step 4 from the [Template upload process](/platform-documentation/apis-and-tooling/dashboard/assets/templates.md#create-a-new-template-assets).
5. You will now see both a Template Assets and an Engine Plugin Assets in the dashboard.\
\
\
\
Upload a new Engine Plugin Assets Version
To upload a new Engine Plugin Assets Version, follow the same process used to Create a new Engine Pluign Assets.
Consume an Engine Plugin Assets
Engine Plugins are consumed via the Releases page
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.otherside.xyz/platform-documentation/apis-and-tooling/dashboard/assets/engine-plugins.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.