# Beginning

## Namespace

The namespaces are what the resourcepack is made of, as an example path is this one

```json
📦resource_pack.zip
  └── 📁assets
      └── 📁<namespace>
```

a more concrete example that we can find in minecraft itself is

```json
📦resource_pack.zip
  └── 📁assets
       └── 📁minecraft
           ├── 📁textures
           │    └── 📁entities
           │    └── 📁block
           └── 📁models
                └── 📁item
```

these are used to define spaces, and must always be specified when choosing the path to a model, for example `minecraft:item/diamond` which will reference `assets/minecraft/models/item/diamond.json`

## pack.mcmeta

What is this, this is to define the version and the description in which the resourcepack will work, which is located in the main path of the resourcepack

{% tabs %}
{% tab title="-1.21.9" %}

```yaml
{
    "pack": {
        "pack_format": 46,
        "supported_formats": [
            43,
            54
        ],
        "description": "Beautiful Masky Tweaks"
    }
}
```

{% endtab %}

{% tab title="+1.21.9" %}

```yaml
{
    "pack": {
        "pack_format": 69,
        "min_format": 69,
        "max_format": 70,
        "description": "Beautiful Masky Tweaks"
    }
}
```

{% endtab %}
{% endtabs %}

{% hint style="success" %}
You can put colors on desc, [click here](https://minecraft.wiki/w/Formatting_codes#Color_codes)!
{% endhint %}

where you can find all the mcmeta by versions is [here](https://minecraft.wiki/w/Pack_format) in "List of resource pack formats", and this is located in

```
📦resource_pack.zip
  ├── 📁assets
  └── 📝pack.mcmeta
```

### overlays

these are used to apply textures and anything else to a given version of minecraft, it is used to add compatibility to multiple versions without breaking

```json
📦resource_pack.zip
  ├── 📁assets
  │    └── 📁<namespace>
  ├── 📁overlay_1_21_4 //overlay name
  │    └── 📁<namespace>
  └── 📝pack.mcmeta
```

And these need to be specified in the pack.mcmeta to work.

{% tabs %}
{% tab title="-1.21.9" %}

```yaml
{
    "pack": {
        "pack_format": 42,
        "supported_formats": {
            "min_inclusive": 34,
            "max_inclusive": 42
        },
        "description": "Beautiful Masky Tweaks"
    },
    "overlays": {
        "entries": [
            {
                "formats": {
                    "min_inclusive": 43,
                    "max_inclusive": 46
                },
                "directory": "overlay_1_21_4" // overlay folder name
            }
        ]
    }
}
```

{% endtab %}

{% tab title="+1.21.9" %}

```yaml
{
    "pack": {
        "pack_format": 42,
        "min_format": 43,
        "max_format": 70,
        "description": "Beautiful Masky Tweaks"
    },
    "overlays": {
        "entries": [
            {
                "min_format": 43,
                "max_format": 46,
                "directory": "overlay_1_21_4" // overlay folder name
            }
        ]
    }
}
```

{% endtab %}
{% endtabs %}

You can use both formats to support old and current versions, example:

```yaml
{
    "pack": {
        "pack_format": 46,
        "supported_formats": {
            "min_inclusive": 46,
            "max_inclusive": 69
        },
        "min_format": 46,
        "max_format": 69,
        "description": "MaskyTweaks"
    }
}
```

## pack.png

This is to define the image that will be seen when selecting the resourcepack, generally it is 64x64.

```
📦resource_pack.zip
  ├── 📁assets
  ├── 📝pack.mcmeta
  └── 🎨pack.png
```


---

# 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://guide.elitefantasy.net/resourcepack-guide/beginning.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.