> For the complete documentation index, see [llms.txt](https://docs.msquared.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.msquared.io/apis-and-tooling/dashboard/assets/assets-versions.md).

# Assets Versions

An `Assets Version` is a snapshots of Unreal Engine content that users are able to download and use, once published (see [Assets Types](/apis-and-tooling/dashboard/assets.md#assets-types)).

Assets Versions contain the following editable information:

<table><thead><tr><th width="216">Field Name (*Required)</th><th>Description</th></tr></thead><tbody><tr><td>Description</td><td>An internal description for the Assets Version.<br><br>This should be used to help the author track what the purpose of the Assets Version. Users will see the published release notes rather than this information.</td></tr><tr><td>Release</td><td>Assigning an associated release to an Assets Version will auto-fill the Compatible Releases list when publishing. Additional compatible releases may still be selected.</td></tr><tr><td>Dependencies</td><td>Authors may select other Assets that this Assets Version requires to function.</td></tr></tbody></table>

{% hint style="warning" %} <mark style="color:orange;">Assets Version dependencies are not enforced by the launcher yet.</mark>
{% endhint %}

## Publishing Assets Versions

{% hint style="warning" %} <mark style="color:orange;">Publishing assets is only currently valid for Project Plugins. Engine plugins and Templates can be published but this serves no purpose.</mark>
{% endhint %}

{% hint style="info" %} <mark style="color:blue;">For an Assets Versions to be downloadable for users in the</mark> [<mark style="color:blue;">Plugins page of the Launcher</mark>](/apis-and-tooling/launcher/msquared-launcher/plugins.md)<mark style="color:blue;">, it must first be published.</mark>
{% endhint %}

Assets Versions have the following editable publish information:

<table><thead><tr><th width="215">Field Name (*Required)</th><th>Description</th></tr></thead><tbody><tr><td>Semantic version*</td><td>This must be a valid and increasing <a href="https://semver.org/">Semantic version</a>.<br><br><strong>Once published, this information cannot be edited.</strong></td></tr><tr><td>Compatible Releases</td><td>A list of <a href="/pages/WaKTSMwdgkPXM917LS0D">Releases</a> that this version is compatible with.</td></tr><tr><td>Experimental</td><td>A flag to show this Assets Version may be unstable</td></tr><tr><td>Release Notes</td><td>A <code>markdown</code> description for this Assets Version.<br><br>As this is markdown, the author may wish to embed media to better show what fixes, changes or additions have arrived in the new Assets Version.</td></tr><tr><td>Breaking Changes</td><td>A <code>markdown</code> description for anything that may have broken in user projects due to this Assets Version.</td></tr></tbody></table>

{% hint style="warning" %} <mark style="color:orange;">It is the responsibility of the Assets author to ensure the</mark> <mark style="color:orange;">`Compatible Releases`</mark> <mark style="color:orange;">field of every Assets Version is up-to-date with the current releases.</mark>

<mark style="color:orange;">Likewise, when a new release is created, it is the responsibility of the author to check their Assets Versions against the new release and either:</mark>

* <mark style="color:orange;">Create a new Assets Version with fixes if anything has broken.</mark>
* <mark style="color:orange;">Add the new release to the Assets Versions</mark> <mark style="color:orange;">`Compatible Releases`</mark> <mark style="color:orange;">if everything still works as expected.</mark>
  {% endhint %}

## Limitations

* We do now allow Assets Versions to be deleted if they have been published

## Guides

<details>

<summary>Upload new Assets Version</summary>

Uploading a new Assets Version will depend on the [Assets Type](/apis-and-tooling/dashboard/assets.md#assets-types).

* [Upload a new Engine Plugin Assets Version](/apis-and-tooling/dashboard/assets/engine-plugins.md#uploade-a-new-engine-plugin-assets-version)
* [Upload a new Project Plugin Assets Version](/apis-and-tooling/dashboard/assets/project-plugins.md#uploade-a-new-project-plugin-assets-version)
* [Upload a new Template Assets Version](/apis-and-tooling/dashboard/assets/templates.md#uploade-a-new-template-assets-version)

</details>

<details>

<summary>Edit an Assets Version</summary>

{% hint style="info" %} <mark style="color:blue;">Editing an Assets Version is the same process for all Assets Types</mark>
{% endhint %}

1. Navigate to the Assets where the Assets Version exists.
2. Find the Assets Version you want to edit and press the edit button.\
   \
   ![](/files/tCpWF3zJxCLDnWDx09pB)\\
3. Perform edits in the opened modal.\
   \
   \\
4. Click `Save`.

</details>

<details>

<summary>Publish an Assets Version</summary>

{% hint style="info" %} <mark style="color:blue;">Publishing an Assets Version is the same process for all Assets Types</mark>
{% endhint %}

1. Navigate to the Assets where the Assets Version you want to publish exists.
2. Find the Assets Version you want to publish and click the `Publish` button.\
   \
   ![](/files/QNP4IpdJUCij0btxC8a1)\\
3. Enter publish information into the publish modal that opens.
4. Click `Publish`.\
   \
   ![](/files/rr5HBdfFIo6eWt8ivVhA)

</details>

<details>

<summary>Delete an Assets Version</summary>

{% hint style="info" %} <mark style="color:blue;">The process for deleting an Assets is the same for all Assets Types.</mark>
{% endhint %}

1. Navigate to the Assets Version you want to delete.\
   \
   ![](/files/nXBmHbhvKvmfaoJQkQl5)\\
2. Click the delete button.
3. Confirm deletion of the Assets Version by clicking `Delete`.\
   \
   ![](/files/Gho3GxcbJwD2QV8j1qNk)

</details>