{{exclusive|java}}
{{cleanup}}
{{TOC|right}}
== Preface ==
[[Resource pack]]s allow users to include files that can modify or add custom textures, models, animations, music, sounds, user interfaces, and languages that change the way some things in ''Minecraft'' behave or look.

=== What NOT to do ===
There are some things that you should ''NOT'' do when creating a resource pack / texture packs, which includes but is not limited to:

*Anything that violates the ''Minecraft'' [https://www.minecraft.net/eula EULA].
*Release files that allow users to play a release of ''Minecraft'' without having purchased it from Mojang.
*Release the decompiled source code of ''Minecraft'' in any way.

In any case, you should always follow the [https://account.mojang.com/terms Terms and Conditions] on the [[Mojang Studios]] website.

==Getting started==
=== Making a resource pack===
''Minecraft'' has a unique mechanic that allows for text and media files to be added to the game files that allow for everything from custom block textures and models to custom credits and sound events. This tutorial is meant to help with setting up the file systems in order to implement them. Since the files are essentially code, there are technical rules for how to format files and certain things may change from version to version. As such, what is written in this tutorial may not apply to every situation, but in the case where the difference is significant and specific, it provides a framework on the changes needed for different versions.

''This tutorial is geared toward the latest release of ''Minecraft'', which is currently 1.21. It may be compatible with another version, but compatibility is not guaranteed.''

===Tools===
Creating custom files for ''Minecraft'', whether in the forms of resource/data packs or mods, is somewhat technical and can be difficult. There are many rules that must be followed in order for add-ons to work correctly, most notably how the files are formatted. There are many tools that can help mitigate these issues, some of which are listed here.

====File archiver====
To access the base assets of ''Minecraft'' to edit textures, models, or sounds, a file archiver is needed. [https://www.7-zip.org 7-Zip] or [https://www.rarlab.com/download.htm WinRAR] are suggested. MacOS has a built-in file archiver called "Archive Utility" that can be used, but if an alternative is wanted, [https://apps.apple.com/us/app/the-unarchiver/id425424353?mt=12 The Unarchiver] also works.

====Editor ====
Making a resource pack involves creating [[JSON]] text files, which can be tricky to use and format correctly, especially for people who have never had any contact with this format before, and are coming across it for the first time while trying to create resources for ''Minecraft''. Fortunately, for the user's convenience, many file editors assist with formatting these files and making sure proper syntax is used. Here are some suggestions:

* [https://notepad-plus-plus.org/ Notepad++] - A very lightweight and text editor for Windows, very easy to use
* [https://code.visualstudio.com Visual Studio Code] – More complex code editor better suited for those who have experience with working in such editors
* [https://jsonformatter.org/json-parser jsonformatter.org] – a web application for JSON formatting

====Audio editor====
In order to add sound files, you must put it in the proper format (.ogg). While this can be done using one of numerous sites online, an audio editor program is suggested to allow customizing or trimming of audio files. [https://www.audacityteam.org Audacity] is one of the most popular audio editors.

====Image editor/3D modeling tool====
To add textures or custom models, it is suggested to use a modeling program that allows for a visual-based editing system. Like with audio conversion websites, there are many online tools, though a common recommended program is [https://blockbench.net Blockbench]. Most image editors suffice to modify textures, but it is recommended to use an editor that supports [[transparency]] such as [https://www.getpaint.net/index.html paint.net] or https://pixlr.com/ so that you may add transparent pixels to textures.

==Creating a resource pack==
All the resources and instructions in a pack reside in the pack folder, which lives in the "resourcepacks" directory.

''In versions 1.11 and higher, all file names within a resource pack should use lowercase letters only.''

===Creating the folder===
<!-- TODO: REMOVE THIS SECTION -->

=== Folder structure ===
A resource pack needs to follow a specific folder structure. Every content in your resource pack has its own place.

<div class="treeview">
* {{File|archive}}/{{File|directory|<nowiki><resource pack name></nowiki>}}
** {{File|file|[[#Creating a pack.mcmeta file|pack.mcmeta]]}}: Metadata of the resource pack. This is the only mandatory file.
** {{File|file|[[#Pack icon|pack.png]]}}: The picture to display next to the resource pack in the resource pack selection screen in game.
** {{File|directory|[[#Structuring the assets folder|assets]]}}
*** {{File|directory|icons}}
*** {{File|directory|[[#Adding a namespace folder|<namespace>]]}}: Folder of the namespace to use. More than one directory for different namespaces may exist.
**** [[Resource pack#Folder structure|More directories&hellip;]]
</div>

=== Creating a pack.mcmeta file ===
[[File:FileExtensionsW11.png|thumb|Instructions on how to enable file extensions on Windows 11.]]

To create this file, right click within your resource pack folder and create a new text document. Name this file {{cd|[[pack.mcmeta]]}}.

'''Note:''' Make sure that the file extension is {{cd|.mcmeta}} and ''not'' {{cd|.txt}} when you rename it, as otherwise the resource pack will not be readable by ''Minecraft''! You may be warned that changing a file name extension could make the file unusable. However, this actually indicates that you have renamed the {{cd|pack.mcmeta}} file ''correctly''.

If you cannot see file extensions, you will have to turn them on. For Windows 11, you can turn them on by open the "View" dropdown menu, then hover over the "Show" option, then turn on the "File name extensions" option. For Windows 10, you can turn them on by going to the ''View'' menu of the file explorer and checking the check box for file name extensions. For Windows beneath Windows 10, you can uncheck "hide extensions" in folder settings. On almost all MacOS versions, you can right-click the file and click "Get info" to see the extension and also make it visible.

=== Formatting pack.mcmeta ===
Open {{cd|pack.mcmeta}} in the text editor of your choice and type or copy and paste the following:

<syntaxhighlight lang="json">
{
  "pack": {
    "description": "This is the description of your resource pack",
    "pack_format": 18,
    "supported_formats": [18, 34]
  }
}
</syntaxhighlight>

Be very careful not to forget any braces {{cd|<nowiki>{}</nowiki>}}, commas {{cd|,}}, colons {{cd|:}}, quotation marks {{cd|""}}, or square brackets {{cd|[]}}. Missing one of these can lead to your resource pack not being readable by ''Minecraft.''

==== Description ====
The text following {{cd|description}} is required and displayed in game under the pack title in the resource pack selection screen, and must be enclosed in quotation marks {{cd|""}}. If you wish to use special characters, you can enter the Unicode code for the character in the format {{cd|\u####}}, where {{cd|####}} is the Unicode hex code for the character. Say you want to use the letter ß, which has code {{cd|U+00DF}}. Inside the description you would type {{cd|\u00DF}}. Make sure that you are using the correct slash, or it may not work. A list of Unicode codes can be found [[wikipedia:List of Unicode characters|here]]. ''Note: Only the characters 0000–FFFF ({{w|Basic Multilingual Plane}}) are supported.''{{Citation needed}}

==== Pack format ====
The number next to {{cd|[[pack_format]]}} is required and tells ''Minecraft'' what release the resource pack is designed for. All valid resource pack formats with their corresponding {{edition|java}} versions that can be used for this {{cd|pack_format}} property are presented in the table below.

Starting with ''Minecraft'' 1.20.2, in addition to this property, a resource pack can also specify a range of pack formats it is compatible with. For more information on this topic, see the [[#Pack format range (optional)|"Pack format range" section]].

==== Pack format range (optional) ====
The {{cd|supported_formats}} property introduced in ''Minecraft'' 1.20.2 is optional and was designed to be used to specify a range of pack formats that the resource pack is compatible with, something that was not possible with the legacy {{cd|pack_format}} property. All valid resource pack formats with their corresponding {{edition|java}} versions that can be used for this {{cd|supported_formats}} property are presented in the table below.

This property can be represented in one of the following three forms:
* a single number (example: {{cd|18}})
* a list that contains two numbers, where the first one denotes the start of the range and the second one the end, both inclusive (example: {{cd|[18, 34]}})
* an object that contains two children — {{cd|min_inclusive}} and {{cd|max_inclusive}} — to specify the start and end of the range, similarly to the list above (example: {{cd|<nowiki>{&nbsp;"min_inclusive": 18, "max_inclusive": 34&nbsp;}</nowiki>}}).

'''Note:''' Even though this property somewhat replaces {{cd|pack_format}}, the latter is still required and has to be specified in order for the resource pack to be read correctly by ''Minecraft''. Also, if {{cd|supported_formats}} is present, it must contain the value declared in {{cd|pack_format}}.

{{Resource pack format}}

=== Pack icon ===
If an icon is not specified, a generic [[cobblestone]] icon appears next to the resource pack in the resource pack selection screen in game. If you would like to use your own pack icon instead, you need to name it {{cd|pack.png}} and place it inside your resource pack folder right next to the {{cd|pack.mcmeta}} file.

The file must be in the PNG format in any resolution and with a 1:1 aspect ratio (in other words, square-shaped), but a resolution of 128×128 px is recommended, as this is what [[Mojang Studios|Mojang]] itself uses in the default built-in resource and data packs.

===Testing your pack===
[[File:TestingJavaPack.png|thumb|432px|If your resource pack is formatted correctly, it should appear in the selection menu like this.]]
At this point, you can test if the pack is formatted correctly by putting it in the game! To do this you must place your resource pack folder in the ''Minecraft'' pack folder. You can access it by selecting "[[Options]]", then "Resource Packs", then "Open Pack Folder", or you can navigate to it from your file browser:

* For Windows, right click on the start button → run → type in %appdata% → .minecraft → resourcepacks
* For MacOS, go to Library → Application Support → minecraft → resourcepacks
*For Linux, go to ~/.minecraft/resourcepacks (/home/<username>/.minecraft/resourcepacks)
Once you have the folder open, you can drag your custom pack folder and drop it in.

If you have formatted the files correctly, you should see your resource pack appear in the menu.
====Troubleshooting====
If you don't see your pack in the list, make sure your {{cd|pack.mcmeta}} file is correct and saved in the folder. Look for any missing braces {{cd|<nowiki>{}</nowiki>}}, commas {{cd|,}}, colons {{cd|:}}, quotation marks {{cd|""}}, or square brackets {{cd|[]}}. Remember that for each open brace, quotation, or square bracket, you must have a closing brace, quotation, or square bracket.

==Adding content ==

===Structuring the assets folder ===
Now that you have your resource pack set up, you can start adding content to it. You add most files into a subfolder called <code>assets</code>. Simply create a new folder inside your resource pack folder named <code>assets</code>. This, <code>pack.mcmeta</code>, and <code>pack.png</code> should be the only files located directly in your parent resource pack folder. Any other resource files must be located somewhere in <code>assets</code> or they won't be read by ''Minecraft''.

====Adding a namespace folder====
Next, inside your assets folder are your namespace folders. These help separate the files in your resource pack so that there is no confusion between which files are located where. If you plan on modifying or replacing vanilla resources, those files would go into the <code>minecraft</code> namespace folder. Custom additions should go in your own namespace folder, which for this tutorial is named <code>custom</code>. In the future, you should use a significant or unique namespace so that there isn't a possibility of other resource packs confusing which files belong where when multiple packs are loaded.

===Accessing the vanilla resources ===
If you plan on editing multiple resources, or to help ease of access, you may want to save a copy of the vanilla resources in an accessible location in case some things rely on other files within the directory. To do this, you need to navigate to the vanilla resources file by opening the <code>versions</code> folder inside the <code>.minecraft</code> directory. You should see a list of numbered folders, which correspond to versions that you've loaded or used in the past. Open the folder corresponding to the version you want for your resource pack (in this tutorial it would be 1.20.6) and extract the JAR file located inside, which can be done by right clicking the file and selecting a file archiver from the "Open With" option. You may want to save this in an accessible location for future reference, as certain tasks such as modifying block models require textures in addition to the model files. If you do not have a program that can open .jar files simply change the extension from .jar to .zip.

=== Modifying an entity's texture===
This section goes through the process of modifying a texture, using the creeper texture as an example.

====Finding the vanilla texture====
First, you need the vanilla resource to get the texture you want to edit. This is located in the extracted version folder that was created in the previous section. In the extracted folder, navigate to <code>assets</code>→<code>minecraft</code>→<code>textures</code>→<code>entity</code>→<code>creeper</code> where you can find <code>creeper.png</code>. Save a duplicate of this file somewhere accessible or keep the folder window open during the next few steps.

[[File:CreeperTexture1.png|thumb|360px|The creeper texture loaded in paint.net.]]

Next you'll need to replicate the folder structure of the vanilla pack within your resource pack, which lets ''Minecraft'' know to use the texture. Since we are modifying a default texture, this is in the <code>minecraft</code> subfolder of our <code>assets</code> folder. Within the <code>minecraft</code> folder of ''your resource pack'', do the following:

#Inside {{cd|minecraft}}, create a folder called {{cd|textures}}.
#Inside {{cd|textures}}, create a folder called {{cd|entity}}.
#Inside {{cd|entity}}, create a folder called {{cd|creeper}}.
# Copy the creeper texture from the vanilla resource pack into your newly created <code>creeper</code> folder.

Now that you have the normal creeper texture placed in your resource pack, open it up in the image editor of your choice. It should look something like the image shown.

Since texture files are very small, you may need to zoom in.

;A quick note on textures

If you've never seen a texture before, the above image might surprise you. A lot of textures look this way and are "wrapped" around a model, like wrapping paper around a present.
[[File:LargerTextureLayoutMap.png|thumb|246px|Color-coded Texture. Sections of the same color always face the same direction.]]

Now it's time to be creative! Edit the texture however you want. For simplicity, this example adds a headband. Note where the changes are and compare it to the color-coded texture above.
[[File:Creeperheadband.png|thumb|202px|left|Creeper texture with a red headband.]]

Once you are happy with your texture, save the file as <code>creeper.png</code>. It is important that it is saved with the same name as the default asset or otherwise it cannot detect and load your texture.

Now you can load up ''Minecraft'' and spawn a creeper with your custom texture! If it doesn't show up, make sure that you've selected your resource pack. If it still doesn't work, make sure you've named the file properly and placed it in the correct folder.
[[File:ResourcePackNewCreeper.png|thumb|260px|Here's the creeper with the new texture as it appears in-game.]]

=====Pack hierarchy=====
If you are playing with multiple resource packs loaded, there may be some textures that are in your pack that aren't being shown. This is because of the way resource packs are loaded in ''Minecraft''. All selected resource pack files are loaded from the bottom up as they are shown in the selection menu, so if there is a resource pack that is loaded above yours, it may replace files that you've changed. This can cause various issues with using multiple themed resource packs that have differing textures, so make sure you have your resource pack at the top.

===Modeling blocks and items===
{{Main|Model}}
Sometimes you may want to change one of the ''Minecraft'' models. To do so you need a file archiver to get the default model and texture along with a 3D modeling tool to edit the model. Blockbench works well in this case since it can export directly to the <code>.json</code> format needed for models.

====Replacing a block====
Because the default [[ladder]] in ''Minecraft'' isn't 3D, you can replace it with your own model. First, get all the ladder's files into this resource pack:

#Open the ''Minecraft'' JAR file using a ZIP viewer of your choice.

*Navigate into the {{cd|assets/minecraft/blockstates}} folder, then extract {{cd|ladder.json}} to {{cd|Tutorial_Resource_Pack/assets/minecraft/blockstates}}
*Navigate into the {{cd|assets/minecraft/models/block}} folder, then extract {{cd|ladder.json}} to {{cd|Tutorial_Resource_Pack/assets/minecraft/models/block}}
*Navigate into the {{cd|assets/minecraft/models/item}} folder, then extract {{cd|ladder.json}} to {{cd|Tutorial_Resource_Pack/assets/minecraft/models/item}}
*Lastly, navigate into the {{cd|assets/minecraft/textures/block}} folder, then extract {{cd|ladder.png}} to {{cd|Tutorial_Resource_Pack/assets/minecraft/textures/block}}.

Now you can either edit the {{cd|ladder.png}} using your preferred image editor, or you can edit it in your preferred modeling editor.

Note: If you are doing a basic "Just Simple Nonanimated Textures" resource pack, the .json files are unnecessary. Otherwise, if you are doing special features to change what the texture looks like when certain parameters are true or false, then the .json files would be necessary. For example, if you created a resource pack that makes grass blocks smooth, the .json files would prevent you from having dirt lines everywhere in your world that already uses code. 

====Modeling the ladder - Blockbench====
In modeling the ladder, we use ''[https://blockbench.net/ Blockbench]''. Once you have opened the program, press {{cd|Ctrl+O}} to open the model selection menu. After the open dialog has appeared, go to the location where you saved <code>ladder.json</code> and select .

You then should be facing a ladder that is on the south side of the box.

*On the menu bar, go to ''"Edit -> Add Cube"'' to create a new block.
*Resize the model to a full-sized cube. Then, under ''Textures'' on the left panel right click {{cd|ladder.png}}, then click ''Apply to Untextured Faces.''
*In the top left, there is an image of the ladder, with a 1×1 highlighted region. Move this to change the texture to what you want it to be. Repeat until all sides of the block are as wanted.
*Go to ''"File -> Save Model"'' and save in {{cd|resourcepacks/Tutorial_Resource_Pack/assets/minecraft/models/block/ladder.json}} (Replace ''"block"'' with ''"blocks"'' for 1.12 and below).

Now we have created a new model for the ladder block in Blockbench.

====Texturing the ladder - paint.net====
Go to [https://getpaint.net/download.html getpaint.net] and download paint.net for free.

*Open paint.net.
*Do Ctrl+O and go to .minecraft/textures/block/ladder.png and double click.
*Edit the Ladder however you want.
*When you're done, press the X button in the top right of the window. It opens a dialog if you changed anything and ask if you want to save your work. Press Save then okay twice. You don't need to change anything in the menus.

====Finishing off====
When you have completed the 3D model of the ladder and saved it, launch ''Minecraft'', and test it out. Place a ladder on a wall, and you should see its replaced model.

===Changing existing sounds or music===
{{info needed section|Changing subtitles of sounds, adding subtitles to existing sounds without them}}
Just like modifying the default textures or models, you can substitute custom sounds in place of the default ones. This example shows how to change the boss music in the [[ender dragon]] fight.

=====Finding a sound's path=====
Similar to the custom texture and models, you'll first need to know the ''path'' of the sound you want to change.

#Inside your [[.minecraft]] folder, navigate to {{cd|assets/indexes}}, which contains a list of numbered <code>.json</code> files.
#Find the {{cd|.json}} file corresponding to your ''Minecraft'' version (e.g. {{cd|1.19.json}}<!-- 1.20+ index file names are just numbers (e.g. 5, 8, 12). How do we know which number is which version and how do we explain that here? -->), and open it with the text editor of your choice.
#In this file you can find all the sounds found in ''Minecraft''. Press {{key|CTRL+F}} to search for your sound.
#*For a list of filenames for music, you can check [[Music#List]]
#Your sound path should look something like this: {{cd|minecraft/sounds/music/game/end/boss.ogg}}

=====Modifying the sound=====

#'''Inside your resource pack folder''', navigate to {{cd|assets/minecraft}}.
# Create a new folder named {{cd|sounds}}.
#Now inside your {{cd|sounds}} folder, you need to create new folders depending on your sound's path. For example, if your path is {{cd|minecraft/sounds/music/game/end/boss.ogg}}, you need to create the folders {{cd|sounds/music/game/end}}.
# In the last folder (in this example, it's {{cd|end}}) you can put in your new sound file. Make sure you named the file to the file that you're replacing, or in this example, {{cd|boss.ogg}}.
#* Note that this file '''must''' be a {{cd|.ogg}} file. To convert your sound file to a {{cd|.ogg}} file, you can use the free website [https://audio.online-convert.com/convert-to-ogg Online-Convert.com]

=====Testing your sound =====
If everything went according to plan, you have now replaced a sound in ''Minecraft''. To test it:

#Make sure you have enabled your resource pack.
#*If you already had ''Minecraft'' open with your resource pack enabled, you can press {{key|F3+T}} to reload all resource packs.
#Use the {{cmd|playsound}} command to play your sound. In our example, type: {{cd|/playsound minecraft:music.dragon master @s}}

===Adding new sounds or music===
{{wip|section=1}}

In addition to modifying default sounds, you can add your own! In this example, a new player hurt sound can be added without replacing any of the current player hurt sounds.

===== Finding the sound path=====
In order to add a sound, you'll need to know where it should actually go by determining its ''path''. Unlike replacing sounds, you should go straight to your resource pack folder and search in there.

#Find and open your version's <code>.json</code> index file (e.g <code>1.19.json</code><!-- 1.20-1.20.4 index file names are just numbers (e.g. 5, 8, 12). How do we know which number is which version and how do we explain that here? -->) from <code>.minecraft/assets/indexes</code>.
#Press {{key|CTRL+F}} to search for your sound path.
#*In this case, the location for the player hurt sounds looks like this: {{cd|minecraft/sounds/damage/}}.

=====Adding the folders and sound in your resource pack=====

#Going to your resource pack folder, navigate to <code>Tutorial_Resource_Pack/assets/minecraft</code>.
#Inside the <code>minecraft</code> folder, create a folder named {{cd|sounds}}.
#*If you already have a <code>sounds</code> folder from replacing a default sound, open that folder.
#Within the <code>sounds</code> folder, create a folder that matches the directory of the sound you want to add. In this case, we are going to create a file called <code>damage</code>.
#Add your sound here.
#*The sound ''must'' be a {{cd|.ogg}} file. Like in the previous section, you may use the free website [https://audio.online-convert.com/convert-to-ogg Online-Convert.com] or use Audacity as mentioned at the top of the page.
#*Also note the already existing files seen in your {{cd|.json}} file from above. In this case, five other hurt sounds exist within the {{cd|minecraft/sounds/damage/}} folder, two for falling at different heights ({{cd|fallbig.ogg}} and {{cd|fallsmall.ogg}}) and the other three are when the player actually gets hurt ({{cd|hit1.ogg}}, {{cd|hit2.ogg}}, and {{cd|hit3.ogg}}) Since we want to ''add'' a fourth sound to the existing three hurt sounds, we cannot reuse those file names. For simplicity, name your sound {{cd|hit4.ogg}}.

===== Changing the sound event=====
Because we are adding a sound, we must change the associated sound event in {{cd|sounds.json}}.

#Go back to {{cd|assets/minecraft}} in your resource pack folder.
#Create a text file named {{cd|sounds.json}}. Do make sure that the file extension is indeed '''.json''' and nothing else.
#At your choice, paste the following template into {{cd|sounds.json}}:
<syntaxhighlight lang="json">
{
  "entity.player.hurt": {
    "sounds": [
      {
        "name": "damage/hit1"
      },
      {
        "name": "damage/hit2"
      },
      {
        "name": "damage/hit3"
      },
      {
        "name": "damage/hit4"
      }
    ],
    "subtitle": "Hurt"
  }
}
</syntaxhighlight>

*The above code only applies to this example, which adds a new damage sound. If you are changing a different sound event, replace {{cd|entity.player.hurt}} with the sound event listed in the vanilla {{cd|sounds.json}} file.
*You can find out the id used by ''Minecraft'' for each sound folder. By using {{cd|/playsound}} in-game, you can determine this id. In this case, using {{cd|/playsound minecraft:entity.player.hurt master @s}} confirms that the player's hurt sound is indeed classified as {{cd|entity.player.hurt}}.
*Make sure the name fields are in lowercase characters only. The names of your files should be in lowercase as well. Otherwise, the resource pack may fail to use your new sounds.
*The {{cd|subtitle}} field dictates the text to display when the sound is played. It can either be a string of text, or can use a field defined in a {{cd|lang}} file.{{needs testing|Can raw JSON text be used?}}
*In addition to these fields displayed, you may add more additional fields to the {{cd|sounds.json}} file to specify more parameters such as {{cd|volume}} and {{cd|pitch}}. A detailed list of additional {{cd|sounds.json}} fields can be found [[Sounds.json|here]].
*Correct {{cd|.json}} formatting is required! Any missing bracket, comma, etc. causes the resource pack to fail.

=====Testing your sound=====
If there is an error anywhere in your {{cd|sounds.json}} file, none of the sounds described in it appear in-game. If this happens, you should check the spelling and file paths.

If everything went according to plan, you have now added a sound to ''Minecraft''. To test it:

#Make sure you have enabled your resource pack.
#*If you already had ''Minecraft'' open with your resource pack enabled, you can press {{key|F3+T}} to reload all resource packs.
#Use the {{cmd|playsound}} command once again to play your sound. In our example, type: {{cd|/playsound minecraft:entity.player.hurt master @s}}. For this example, it likely requires multiple tries, as hurt sounds are chosen randomly.

===Adding languages===
{{Main|Resource pack#Language}}
You can add completely new languages to ''Minecraft'' using a resource pack. Assuming that your new language is {{cd|<lang>}}<ref>[[wikipedia:ISO 639|ISO 639]]</ref> and its country/region is {{cd|<country>}}<ref>[[wikipedia:ISO 3166-1#Current codes|ISO 3166-1]]</ref>, the {{cd|pack.mcmeta}} file will look like this:

<syntaxhighlight lang="json">
{
  "pack": {
    "description": "This is the description of your resource pack",
    "pack_format": 18,
    "supported_formats": [18, 34]
  },
  "language": {
    "<lang>_<country>": {
      "name": "Tutorial Language",
      "region": "<country>/<region name>",
      "bidirectional": false
    }
  }
}
</syntaxhighlight>

If you want your language to be right-to-left, set {{cd|bidirectional}} to {{cd|true}}.

Then, put {{cd|<lang>_<country>.json}} in {{cd|assets/minecraft/lang}} inside your resource pack. When you launch the game, choose your resource pack, open the [[Language]] selection screen, and your new language should be there.

;Notes

The {{cd|pack.mcmeta}} goes in the '''root folder of your resource pack, not in the {{cd|assets/minecraft/lang}} folder'''. Also note that '''the above {{cd|pack.mcmeta}} is the same file as the {{cd|pack.mcmeta}} file that you have created a while ago'''. As of [[Java Edition 1.7-pre|1.7-pre]], you can choose multiple resource packs at once. If you want to use your new language and resource pack for before 1.7, you need to combine them manually because multiple resource packs could not be selected before the version.

===Animation properties===
{{Main|Resource pack#Animation}}
An example of an animation file is this:

;stone.png.mcmeta
<syntaxhighlight lang="json">
{
  "animation": {
    "interpolate": true,
    "width": 1,
    "height": 7,
    "frametime": 1,
    "frames": [
      {
        "index": 0,
        "time": 0
      },
      1, 2, 3, 4, 5, 6, 4, 2
    ]
  }
}
</syntaxhighlight>

;Note

All you really need to make a texture animated is the following code. By default, it makes each frame last only one tick:

;stone.png.mcmeta
<syntaxhighlight lang="json">
{
  "animation": {}
}
</syntaxhighlight>

Save the file as the same name as the texture you want to be animated with an {{cd|.mcmeta}} in the same folder as your texture.

===Texture properties===
{{Main|Resource Pack#Textures}}
An example of a texture property is this:

;shadow.png.mcmeta
<syntaxhighlight lang="json">
{
  "texture": {
    "blur": false,
    "clamp": true
  }
}
</syntaxhighlight>

===Fonts===
{{Main|Resource pack#Fonts}}
Character sizes in fonts are determined by the last line of pixels that contains pixels that contain a non-zero alpha. This allows additional padding to be added around characters by adding a color with an alpha level of 1, which ''Minecraft'' considers as part of the character.

==Testing your resource pack==

*Launch the game
*Click on ''[[Options]]''
*Click on ''[[Resource Pack]]s''
*Find "''Tutorial_Resource_Pack''" (Or the name of the pack if you named it something else) in the list on the left and click the arrow next to it
* Click ''Done''

If you decide you want to make some changes to your resource pack, edit your resource pack, go to resource packs in options, remove your pack from the active list and exit, go back, and reapply it. Alternatively, saving the texture to the resource pack and pressing {{key|F3+T}} reloads the pack without the need to reload the default textures first.

==Packaging resource packs with worlds==
For use in singleplayer worlds, you can package your resource pack as a ZIP file named {{cd|resources.zip}} inside the world directory. This is then automatically used when playing the singleplayer world.

==Server resource packs==
If you are the owner of a server, you may set it as the resource pack of your server.

#Make sure your pack format is a .zip-folder.
#Upload the pack on a file hosting website, e.g. [https://mc-packs.net/ MCPacks].
#Copy the download link of your pack. IMPORTANT: If you are using your own server or some other host then you have to make sure that you are using a direct download link. You also need to make sure to use a SSL certificate that is compatible with the shipped Java version 8 u51. ([https://bugs.mojang.com/browse/MC-143768 MC-143768])
# Open the server.properties with the text editor of your choice.
#Search for the line {{cd|resource-pack{{=}}}}.
#Paste the download link after the equal sign.
#Optional: Set the {{cd|require-resource-pack}} property to {{cd|true}} to force people to use the resource pack.
#Save your changes to the server-properties and restart your server.
#Enjoy!

Servers can have an icon that appears in the Multiplayer list.

#Create a PNG image with a size of 64 by 64 pixels, transparency is supported.
#Save (or rename) it to {{cd|server-icon.png}}.
#Move it to the server's directory.
#Restart the server.
#Server icons should display next to the server name. If it does '''not''' show up properly, you may have the wrong file type. Go to '''Creating a pack.mcmeta file''' above.

== See also ==
* [[Data pack]]
* [[Tutorials/Creating a data pack]]
* [[Tutorials/Loading a resource pack]]

== References ==
{{Reflist}}

== Navigation ==
{{Navbox resource packs}}
{{Navbox tutorials|technical}}

[[Category:Resource packs]]
[[Category:Java Edition]]
[[Category:Tutorials]]

[[de:Anleitungen/Ressourcenpaket erstellen]]
[[ja:チュートリアル/リソースパックの作成]]
[[ko:튜토리얼/리소스 팩 만들기]]
[[pl:Poradniki/Tworzenie paczki zasobów]]
[[zh:Tutorial:制作资源包]]