> For the complete documentation index, see [llms.txt](https://sebun1.gitbook.io/skins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sebun1.gitbook.io/skins/packaging/thunderstore.md).

# Thunderstore

## Export from Editor

The process is completely the same as [Thunderstore](/skins/packaging/thunderstore.md), except during export, use the <kbd>Export Thunderstore .zip Package</kbd> button.

<figure><img src="/files/47K441AwPEqAUjYrXhJK" alt="" width="368"><figcaption></figcaption></figure>

Now, save the zip file and either upload it to Thunderstore or send it to someone as a regular mod.

## Manual <mark style="color:$warning;">(Legacy)</mark>

If you are unfamiliar with what should be packaged for distribution, check out [General Distribution](/skins/packaging/general-distribution.md#legacy-documentation).

***

If you are not yet familiar with the requirements for packages distributed on Thunderstore, check out their documentation:

{% embed url="<https://wiki.thunderstore.io/mods/creating-a-package>" %}

If you are familiar with this, you are half way there.

### Manifest

Since Skin Groups don't work unless the plugin is installed, include the plugin as a dependency.

{% embed url="<https://thunderstore.io/c/gtfo/p/food/Skins/>" %}

You should use the dependency string with the latest version, though this is not future proof since the this plugin might update.

{% hint style="info" %}
Some mod managers don't respect the version number anyways. e.g. r2modman
{% endhint %}

Here's the Tron skin pack's `manifest.json` as an example. There are no other requirements for the manifest with respect to Skins.

<pre class="language-json" data-title="manifest.json" data-line-numbers><code class="lang-json">{
  "name": "Tron",
  "version_number": "1.1.0",
  "website_url": "",
  "description": "A bunch of skins inspired by Tron",
<strong>  "dependencies": [
</strong><strong>    "food-Skins-0.6.0"
</strong><strong>  ]
</strong>}
</code></pre>

### Asset Folder

After setting up the required structure for a Thunderstore package, simply create the directories for `Assets/Skins/` within the archive.

{% hint style="warning" icon="input-text" %}
As a reminder. Please use sufficiently unique and meaningful GUIDs for your Skin Groups!
{% endhint %}

After which, copy all the Skin Group folders (must be the folders themselves) into the Skins folder here.

This works because once the package is installed, the contents inside `Assets/` will be copied to `<BepInEx>/Assets` which is the per-profile skins folder.

***

As an example, the following is the package structure for the [Tron skin pack on Thunderstore](https://thunderstore.io/c/gtfo/p/food/Tron/).

<figure><img src="/files/zcuS93VxIHlc7VP0Lfxf" alt="" width="373"><figcaption></figcaption></figure>


---

# 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:

```
GET https://sebun1.gitbook.io/skins/packaging/thunderstore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.