# ResourcePacks

This page is all about where files go.

If your models are missing, this is usually the page you want.

## The Important Paths

Default setup:

* pack source root is `config/dawncosmetics/cosmetics/assets`
* pack zip output is `config/dawncosmetics/assets/cosmetics.zip`
* item defs file is `config/dawncosmetics/cosmetics/assets/items.json`
* cmd map is `config/dawncosmetics/cmd-map.json`

## `pack.layout`

You can pick one of three layouts.

{% tabs %}
{% tab title="pack\_root" %}
Use this when `source_root` is the whole resource pack folder.

```
config/dawncosmetics/cosmetics/assets/
├─ assets/
│  └─ dawncosmetics/
│     ├─ models/
│     └─ textures/
├─ items.json
├─ bbmodels/
├─ pack.mcmeta
└─ pack.png
```

{% endtab %}

{% tab title="assets\_root" %}
Use this when `source_root` points straight at the `assets/` folder.

```
config/dawncosmetics/cosmetics/
├─ assets/
│  └─ dawncosmetics/
│     ├─ models/
│     └─ textures/
├─ items.json
├─ bbmodels/
├─ pack.mcmeta
└─ pack.png
```

{% endtab %}

{% tab title="namespace\_root" %}
Use this when `source_root` points straight at one namespace folder.

```
config/dawncosmetics/cosmetics/assets/assets/dawncosmetics/
├─ models/
└─ textures/
```

Pack level files stay two folders above that namespace folder.
{% endtab %}
{% endtabs %}

## Model And Texture Rules

Keep your paths matched.

If the model is here:

```
assets/dawncosmetics/models/item/backpacks/charizard_wings.json
```

the texture path inside that model should point to the matching texture folder path.

## What `items.json` Does

`assets/items.json` is the pack mapping file.

It tells DawnCosmetics which base item and `model_data` each cosmetic key should use.

Example:

```json
{
  "dawncosmetics:backpacks/charizard_wings": {
    "item": "minecraft:paper",
    "model_data": 90012
  }
}
```

## `pack.mode`

* `auto` uses DawnCosmetics generated pack flow
* `manual` also uses the DawnCosmetics pack flow, but expects you to be more direct with your setup
* `polymer` uses Polymer integration and Polymer item registration

## Commands

* `/cosmetics reload` refreshes config and visual state
* `/cosmetics reload pack` rebuilds the pack and helper files

## Quick Checks

If a cosmetic is missing, check these first:

{% stepper %}
{% step %}
The file is in the right folder for your chosen layout.
{% endstep %}

{% step %}
The model and texture paths match.
{% endstep %}

{% step %}
Your `item` or `icon.item` id is valid.
{% endstep %}

{% step %}
`items.json` has a mapping when you need one.
{% endstep %}

{% step %}
You ran the right reload command.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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://dawnshade.gitbook.io/dawnshade-docs/docs/dawn-cosmetics/summary/troubleshooting/resourcepacks.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.