299
Welcome towards my in depth blog about some quirks you may encounter while making a pack. I experienced these things while I made my own pack.
The way of writing in this blog is formal where I try to be platform independent of Operating System or programs you're using. Besides I like to improving my formal (English) writing skills which is in need of improvement. This is the reason why it's written in this, potential boring, way.
Constructive feedback is highly appreciated and welcome!
The following aspects of making a pack will be handled.
1. The vision of the pack.
2. Setting up the base.
3. Setting up the workspace.
4. Resolution.
5. Transparency.
6. Version compatibility.
7. Uploading & rules of PMC
Mod support will not be handled in this tutorial. Nor do I, eagoy, take any responsibility for any damage coming forth out of this written piece.
1. Vision of the pack:
Before making a pack it's recommended to have an vision/idea for what kind of pack it's going to be. With that, you have a goal in mind that can help you with going further making the pack.
Answer the following questions for yourself. It helps starting up the pack making.
- What kind of vision or style does the upcoming pack have?
- Which resolution am I going to use?
- Which program am I going to use for this pack?
In short, think it through before you start.
2. Setting up the base of the pack:
The pack:
The pack needs to be structured as it is done in the default pack*. Besides it needs one important file more. The 'pack.mcmeta' file. With this file, Minecraft will recognize it as an actual pack. The 'pack.mcmeta' is located in the first folder of the pack: ~/'pack name'/pack.mcmeta.
'root directory'
|-'assets'-'Minecraft'-etc.
|-'pack.mcmeta'
|-'pack.png'
\_others, won't be used by Minecraft.
See also the official Minecraft wiki for more information about the base of a pack.
*The default pack is extractable from the 'Minecraft.jar'. The 'Minecraft.jar' is located in the following location: ~/.minecraft/versions/'Minecraft version x.x.x'/'x.x.x.jar'. Open it in a way you can browse through the stored files in the jar. Inside extract the following map: ~/assets. Inside the 'assets' folder are the default textures of Minecraft stored.
3. Setting up the Workspace:
The following type of programs are recommended to run while making a pack:
One of the following three or more:
A graphics editor program:
With this program you make the actual textures, see the 'transparency' chapter for some important
information.
A sound editor program:
With this program you can make the sounds and music needed for the pack.
3d modeling/coding program:
These kinds of programs allows the making of 3d models of blocks.
Two file systems:
Split the two file system programs, one on the left and one on the right side of the screen. Open in one file system the default pack* as reference for the file structure and names of all files. Open in the other file system the pack you're making.
It's useful to locate the pack you're making in the following location: ~/.Minecraft/resourcepacks/'your pack'. With this you only need to reload the pack in Minecraft itself to test out the latest version of your pack.
Minecraft:
As already said in the previous chapter, testing the pack. In Minecraft you actually see if the blocks work together or simply look the same as in the program you made. The difference come from the distance you're looking at. In Minecraft the blocks are smaller than in the preview window of the editor.
Web browser:
In case of inspirational needs, search possibilities on the web are useful. Be aware of detours.
4. Resolution:
Minecraft is not limited towards resolutions of 1x1, 2x2, 4x4, 8x8, 16x16, 32x32, or other magnitudes of two. Resolutions of 7x7, 6x6** and other are thus possible and already posted on PMC.
From Minecraft 1.5 and onwards, packs with different resulotions such as 8x8 mixed with 32x32 and others are possible.
In addition of textures with an equal width and height, textures where the height is an multiple of the width are possible and needed for animations. In order for Minecraft to handle animations a file 'block.png.mcmeta' file is needed.
See also the official Minecraft wiki for details on animated blocks and how to code them.
**These were the first packs found after a short search. More are findable on PMC.
5. Transparency:
The types of transparency in Minecraft:
Transparent : The pixel is invisible, thus the player can see through it without obstruction or blur.
Solid : The pixel is visible, thus the player cannot see through it.
Semi-transparent : Looking through the pixel results in seeing through it with a blur of the pixel color.
Minecraft in general can only process solid or transparent pixels. Semi-transparent pixels will become solid if the opacity is 50% or more and transparent if the opacity is below 50%.
Special blocks such as the colored glasses, water, ice and slimeblocks can handle semi transparency. In short, if the default texture doesn't have any semi-transparent pixels in it, it cannot handle the semi transparency in your texture.
The possibility of adding a separate code file for adding the semi transparency is not investigated.
See the following link for an relative outdated article that explains the transparency in Minecraft quite well.
Transparency in *.png files:
In order for *.png files to contain transparency, an alpha channel is needed besides the base, RGB, channels.
Some graphic editor programs do not support transparency or semi transparency although these can be used for the most of the textures. In the latter case, a second graphics editor program is needed for the textures that does support, semi transparency.
6. Version compatibility:
The fact that Minecraft changed several times the way it handles packs, 4 main periods stands out.
The underneath is not researched thoroughly and tested and thus may contain mistakes.
Pre Minecraft 1.5:
Before Minecraft 1.5 the textures are stitched together in one 'terrain.png' and others in similar way.
Minecraft 1.5:
The 'terrain.png' is unstitched for individual block files.
This is the last Minecraft version were the packs are called 'texturepacks'. In the Minecraft 1.6.1 and beyond these are replaced with 'resourcepacks'.
Minecraft 1.6.1 – 1.7.10:
Meta-data block period. Pack makers can take advantage of this feature to create alternatives on default blocks to create more possibilities for builders.
In Minecraft 1.7.2 the following file locations are updated:
~/yourpack/assets/Minecraft/music → ~/yourpack/assets/Minecraft/sounds/music
~/yourpack/assets/Minecraft/sound → ~/yourpack/assets/Minecraft/sounds
Minecraft 1.8:
Meta-data blocks are not possible anymore. 3D models are possible from on this version of Minecraft.
Supporting the Minecraft versions:
Theoretically seen, all versions could be done within one pack. This theory comes forth out of the fact that Minecraft ignores files that it cannot handle or doesn't know such as misspelled filenames.
7. Uploading & rules of PMC
Rules:
Standouts in the PMC rules:
- ''The rule of thumb for resource packs is that they must change at least 50% of all blocks or items, or all of the sounds or user interface elements, to be posted.''
- Placeholders are not allowed on PMC (7.7.4). This conflicts with the acceptance of the old texturepack format on PMC in which placeholders are needed when the
texture in question is not done yet (7.7.3). Given the fact that a resourcepack ''...must change at least 50% of all blocks…'' (7.7.2) is this thus a realistic conflict
scenario. Although there is a low chance of pack makers supporting pre Minecraft 1.5 versions.
Uploading on PMC:
The correct section for pack uploading on PMC is the 'pack' section.
PMC allows packs to be uploaded in *.zip format directly towards the PMC server given the size is not larger than 15 MB. This limit should be enough given the fact that the default pack is roughly 3,5 MB in size uncompressed.
The maximum amount of images to be displayed in the gallery is 15. This is 5 images lesser than a project submission uploaded in the correct section. If this amount is not enough, image hosting sites can be used to place additional images in the description of the submission.
Representing the pack:
This paragraph is focused on the image side rather than the description as each individual prefers a different way of setting it up.
To show of the created pack a pack previewer map, self made build or a terrain can be used.
In general a pack previewer map has all blocks and items in a relatively small area. In addition depending on the pack viewer map it shows of several builds representing biomes or standard Minecraft structures.
Self made builds or terrains can show of the pack specific style it is made for rather than a general previewer map.
Although using renders or shaders for the images to let the pack look better, it is recommended to use also default Minecraft (thus unmodded) screenshots as images as not everyone uses these modifications.
To find pack viewer maps this search results in some pack preview maps on PMC.
Thank you for reading this in depth tutorial about creating a pack. Once again I like to state the following:
Constructive feedback is highly appreciated and welcome!
The way of writing in this blog is formal where I try to be platform independent of Operating System or programs you're using. Besides I like to improving my formal (English) writing skills which is in need of improvement. This is the reason why it's written in this, potential boring, way.
Constructive feedback is highly appreciated and welcome!
The following aspects of making a pack will be handled.
1. The vision of the pack.
2. Setting up the base.
3. Setting up the workspace.
4. Resolution.
5. Transparency.
6. Version compatibility.
7. Uploading & rules of PMC
Mod support will not be handled in this tutorial. Nor do I, eagoy, take any responsibility for any damage coming forth out of this written piece.
1. Vision of the pack:
Before making a pack it's recommended to have an vision/idea for what kind of pack it's going to be. With that, you have a goal in mind that can help you with going further making the pack.
Answer the following questions for yourself. It helps starting up the pack making.
- What kind of vision or style does the upcoming pack have?
- Which resolution am I going to use?
- Which program am I going to use for this pack?
In short, think it through before you start.
2. Setting up the base of the pack:
The pack:
The pack needs to be structured as it is done in the default pack*. Besides it needs one important file more. The 'pack.mcmeta' file. With this file, Minecraft will recognize it as an actual pack. The 'pack.mcmeta' is located in the first folder of the pack: ~/'pack name'/pack.mcmeta.
'root directory'
|-'assets'-'Minecraft'-etc.
|-'pack.mcmeta'
|-'pack.png'
\_others, won't be used by Minecraft.
See also the official Minecraft wiki for more information about the base of a pack.
*The default pack is extractable from the 'Minecraft.jar'. The 'Minecraft.jar' is located in the following location: ~/.minecraft/versions/'Minecraft version x.x.x'/'x.x.x.jar'. Open it in a way you can browse through the stored files in the jar. Inside extract the following map: ~/assets. Inside the 'assets' folder are the default textures of Minecraft stored.
3. Setting up the Workspace:
The following type of programs are recommended to run while making a pack:
One of the following three or more:
A graphics editor program:
With this program you make the actual textures, see the 'transparency' chapter for some important
information.
A sound editor program:
With this program you can make the sounds and music needed for the pack.
3d modeling/coding program:
These kinds of programs allows the making of 3d models of blocks.
Two file systems:
Split the two file system programs, one on the left and one on the right side of the screen. Open in one file system the default pack* as reference for the file structure and names of all files. Open in the other file system the pack you're making.
It's useful to locate the pack you're making in the following location: ~/.Minecraft/resourcepacks/'your pack'. With this you only need to reload the pack in Minecraft itself to test out the latest version of your pack.
Minecraft:
As already said in the previous chapter, testing the pack. In Minecraft you actually see if the blocks work together or simply look the same as in the program you made. The difference come from the distance you're looking at. In Minecraft the blocks are smaller than in the preview window of the editor.
Web browser:
In case of inspirational needs, search possibilities on the web are useful. Be aware of detours.
4. Resolution:
Minecraft is not limited towards resolutions of 1x1, 2x2, 4x4, 8x8, 16x16, 32x32, or other magnitudes of two. Resolutions of 7x7, 6x6** and other are thus possible and already posted on PMC.
From Minecraft 1.5 and onwards, packs with different resulotions such as 8x8 mixed with 32x32 and others are possible.
In addition of textures with an equal width and height, textures where the height is an multiple of the width are possible and needed for animations. In order for Minecraft to handle animations a file 'block.png.mcmeta' file is needed.
See also the official Minecraft wiki for details on animated blocks and how to code them.
**These were the first packs found after a short search. More are findable on PMC.
5. Transparency:
The types of transparency in Minecraft:
Transparent : The pixel is invisible, thus the player can see through it without obstruction or blur.
Solid : The pixel is visible, thus the player cannot see through it.
Semi-transparent : Looking through the pixel results in seeing through it with a blur of the pixel color.
Minecraft in general can only process solid or transparent pixels. Semi-transparent pixels will become solid if the opacity is 50% or more and transparent if the opacity is below 50%.
Special blocks such as the colored glasses, water, ice and slimeblocks can handle semi transparency. In short, if the default texture doesn't have any semi-transparent pixels in it, it cannot handle the semi transparency in your texture.
The possibility of adding a separate code file for adding the semi transparency is not investigated.
See the following link for an relative outdated article that explains the transparency in Minecraft quite well.
Transparency in *.png files:
In order for *.png files to contain transparency, an alpha channel is needed besides the base, RGB, channels.
Some graphic editor programs do not support transparency or semi transparency although these can be used for the most of the textures. In the latter case, a second graphics editor program is needed for the textures that does support, semi transparency.
6. Version compatibility:
The fact that Minecraft changed several times the way it handles packs, 4 main periods stands out.
The underneath is not researched thoroughly and tested and thus may contain mistakes.
Pre Minecraft 1.5:
Before Minecraft 1.5 the textures are stitched together in one 'terrain.png' and others in similar way.
Minecraft 1.5:
The 'terrain.png' is unstitched for individual block files.
This is the last Minecraft version were the packs are called 'texturepacks'. In the Minecraft 1.6.1 and beyond these are replaced with 'resourcepacks'.
Minecraft 1.6.1 – 1.7.10:
Meta-data block period. Pack makers can take advantage of this feature to create alternatives on default blocks to create more possibilities for builders.
In Minecraft 1.7.2 the following file locations are updated:
~/yourpack/assets/Minecraft/music → ~/yourpack/assets/Minecraft/sounds/music
~/yourpack/assets/Minecraft/sound → ~/yourpack/assets/Minecraft/sounds
Minecraft 1.8:
Meta-data blocks are not possible anymore. 3D models are possible from on this version of Minecraft.
Supporting the Minecraft versions:
Theoretically seen, all versions could be done within one pack. This theory comes forth out of the fact that Minecraft ignores files that it cannot handle or doesn't know such as misspelled filenames.
7. Uploading & rules of PMC
Rules:
Directly quoted from the PMC rules on the 23rd of July 2015.
7.7Resource Packs
7.7.1What is a Resource Pack?
Resource Packs, called texture packs prior to Minecraft 1.6, are files that change the look and sound of Minecraft. These resource packs can change character and mob skins, block textures, item sprites, particles, sounds, and more.
7.7.2Resource Pack Minimum Requirements
Resource Packs that are submitted to Planet Minecraft must meet certain minimum guidelines or they will be disabled or removed. Generally speaking, a significant portion of one of the primary areas that a resource pack covers must be changed before you are allowed to submit the pack. These areas include blocks, items, sounds, and the user interface. The rule of thumb for resource packs is that they must change at least 50% of all blocks or items, or all of the sounds or user interface elements, to be posted. If you are unsure about whether your resource pack meets the allowed guidelines, please contact a Site Moderator.
7.7.3What about old Texture Packs?
The old Texture Pack format is still accepted on Planet Minecraft, however we recommend that any texture packs that were created prior to the resource pack format be converted if they are updated. Please note that Minecraft versions 1.6 and higher are not able to use the old Texture Pack formats at all. To unstitch and convert normal texture packs created prior to Minecraft 1.5, please use the official tool located here. For HD texture packs or those using old block animations through MCPatcher or Optifine, please use the officially sactioned alternative here. Once the texture pack has been unstitched, convert the textures to a resource pack using the Minecraft Texture Ender, which is located here.
7.7.4Placeholders
Resource packs that are posted to Planet Minecraft are not allowed to contain any 'placeholder' files. This is generally template files for item or block images, or sounds, usually from the base resources or another resource pack. With the current resource pack format, Minecraft will provide any resources that are not included in the pack using the default resources, which means that there is no reason to include placeholder files.
7.7.5Disallowed Resources
There are certain kinds of resource packs that are not allowed on Planet Minecraft. These resource packs include but are not limited to:
Transparent block textures or "X-Ray" textures for blocks that are not transparent
Sound files that are copywritten, such as discs playing popular music from outside sources
Multiple resource packs for different sizes of the same textures
Textures that are recolored/filtered versions of the default
Packs mostly containing textures that may be considered spam. This includes small, simple textures (such as a "1x1" pack) that make up the majority of the resource pack.
7.7.1What is a Resource Pack?
Resource Packs, called texture packs prior to Minecraft 1.6, are files that change the look and sound of Minecraft. These resource packs can change character and mob skins, block textures, item sprites, particles, sounds, and more.
7.7.2Resource Pack Minimum Requirements
Resource Packs that are submitted to Planet Minecraft must meet certain minimum guidelines or they will be disabled or removed. Generally speaking, a significant portion of one of the primary areas that a resource pack covers must be changed before you are allowed to submit the pack. These areas include blocks, items, sounds, and the user interface. The rule of thumb for resource packs is that they must change at least 50% of all blocks or items, or all of the sounds or user interface elements, to be posted. If you are unsure about whether your resource pack meets the allowed guidelines, please contact a Site Moderator.
7.7.3What about old Texture Packs?
The old Texture Pack format is still accepted on Planet Minecraft, however we recommend that any texture packs that were created prior to the resource pack format be converted if they are updated. Please note that Minecraft versions 1.6 and higher are not able to use the old Texture Pack formats at all. To unstitch and convert normal texture packs created prior to Minecraft 1.5, please use the official tool located here. For HD texture packs or those using old block animations through MCPatcher or Optifine, please use the officially sactioned alternative here. Once the texture pack has been unstitched, convert the textures to a resource pack using the Minecraft Texture Ender, which is located here.
7.7.4Placeholders
Resource packs that are posted to Planet Minecraft are not allowed to contain any 'placeholder' files. This is generally template files for item or block images, or sounds, usually from the base resources or another resource pack. With the current resource pack format, Minecraft will provide any resources that are not included in the pack using the default resources, which means that there is no reason to include placeholder files.
7.7.5Disallowed Resources
There are certain kinds of resource packs that are not allowed on Planet Minecraft. These resource packs include but are not limited to:
Transparent block textures or "X-Ray" textures for blocks that are not transparent
Sound files that are copywritten, such as discs playing popular music from outside sources
Multiple resource packs for different sizes of the same textures
Textures that are recolored/filtered versions of the default
Packs mostly containing textures that may be considered spam. This includes small, simple textures (such as a "1x1" pack) that make up the majority of the resource pack.
Standouts in the PMC rules:
- ''The rule of thumb for resource packs is that they must change at least 50% of all blocks or items, or all of the sounds or user interface elements, to be posted.''
- Placeholders are not allowed on PMC (7.7.4). This conflicts with the acceptance of the old texturepack format on PMC in which placeholders are needed when the
texture in question is not done yet (7.7.3). Given the fact that a resourcepack ''...must change at least 50% of all blocks…'' (7.7.2) is this thus a realistic conflict
scenario. Although there is a low chance of pack makers supporting pre Minecraft 1.5 versions.
Uploading on PMC:
The correct section for pack uploading on PMC is the 'pack' section.
PMC allows packs to be uploaded in *.zip format directly towards the PMC server given the size is not larger than 15 MB. This limit should be enough given the fact that the default pack is roughly 3,5 MB in size uncompressed.
The maximum amount of images to be displayed in the gallery is 15. This is 5 images lesser than a project submission uploaded in the correct section. If this amount is not enough, image hosting sites can be used to place additional images in the description of the submission.
Representing the pack:
This paragraph is focused on the image side rather than the description as each individual prefers a different way of setting it up.
To show of the created pack a pack previewer map, self made build or a terrain can be used.
In general a pack previewer map has all blocks and items in a relatively small area. In addition depending on the pack viewer map it shows of several builds representing biomes or standard Minecraft structures.
Self made builds or terrains can show of the pack specific style it is made for rather than a general previewer map.
Although using renders or shaders for the images to let the pack look better, it is recommended to use also default Minecraft (thus unmodded) screenshots as images as not everyone uses these modifications.
To find pack viewer maps this search results in some pack preview maps on PMC.
Thank you for reading this in depth tutorial about creating a pack. Once again I like to state the following:
Constructive feedback is highly appreciated and welcome!
| Credit | PMC rules & Minecraft wiki |
| Tags |
tools/tracking
3410301
6
textureresource-pack-creation---an-indepth-tutorial
Silabear
ScotsMiser
sniffercraft34
PythPale
ConcreteMan
ItzOrangey
Anime Gril
WYHA-Storm
Create an account or sign in to comment.
Thanks for the constructive feedback and diamond :-)
I look at it a later date in hope for more constructive feedback, thanks :-)