Model

All model and variant files are of the  format. Block models are used to depict all the blocks in the game, whereas item models are used to display the items in the players hand, on their head (helmets and hats), on the ground and in the inventory. Therefore even the icons used in the inventory are defined in these files.

Block states
There are several different variants of some blocks, hence each block has its own block state file, which lists all its existing variants and links them to their corresponding model. These files are stored in the following folder:. These files are used directly based on their filename, thus a block state file with a different name will not affect the block.


 * The root tag
 * Holds the names of all the variants of the block.
 * Name of a variant, which consists of the relevant BlockStates separated by commas. A block with just one variant uses   as a name for its variant. Each variant contains the properties of its model. If more than one model is used, these models must be specified in separate-tags, which are subsidiary to the variant tag.
 * Contains the properties of a model, if more than one model is used for the same variant. All specified models alternate in the game.
 * Specifies the path to the model file of the block, starting in.
 * Rotation of the model on the x-axis in increments of 90 degrees.
 * Rotation of the model on the y-axis in increments of 90 degrees.
 * Rotates the texture with the block, if  (default).
 * Probability of the model being used in the game. The default value is 1 (=100%).
 * Specifies the path to the model file of the block, starting in.
 * Rotation of the model on the x-axis in increments of 90 degrees.
 * Rotation of the model on the y-axis in increments of 90 degrees.
 * Rotates the texture with the block, if  (default).

Example: Torch
The torch has several variants: It can be placed on the ground or at a wall facing in four different directions. This example is taken from the file, which can be found at.

File: torch.json

{   "variants": { "facing=up": { "model": "normal_torch" }, "facing=east": { "model": "normal_torch_wall" }, "facing=south": { "model": "normal_torch_wall", "y": 90 }, "facing=west": { "model": "normal_torch_wall", "y": 180 }, "facing=north": { "model": "normal_torch_wall", "y": 270 } } }

is the variant of the torch standing on the ground and links to the corresponding model. A torch can be placed on all four sides of a block and therefore needs four different variants, one for each side. These are called,  ,   and. All four variants use  as their model, which is rotated by a multiple of 90 degrees around the   axis to align with the different sides of the block they are placed on.

Example: Grass Block
The grass block has two variants, whereby the first one holds four different models. This example is taken from the file, which can be found at.

File: grass.json

{   "variants": { "snowy=false": [ { "model": "grass_normal" }, { "model": "grass_normal", "y": 90 }, { "model": "grass_normal", "y": 180 }, { "model": "grass_normal", "y": 270 } ],       "snowy=true":  { "model": "grass_snowed" } } }

The non-snow-covered grass block holds four models, which all use the same block model, but each one is rotated by a multiple of 90 degrees. As there are four models and the -tag is not used for any of them, each one has a chance of 25% to be used every time a block is placed.

Block models
The folder  holds the model files for all the specified variants. The names of the files can be changed, but must always correspond with the names used in the variant files.


 * The root tag
 * Loads a different model from the given path, starting in.
 * Can be set to  to use a model that is created out of the specified icon. Note that only the first layer is supported, and rotation can only be achieved using block states files.
 * Whether to use ambient occlusion (  - default), or not.
 * Holds the textures of the model. Each texture starts in  or can be another texture variable.
 * What texture to load particles from. Note: All breaking particles from non-model blocks are hard-coded.
 * Defines a texture variable and assigns a texture.
 * Contains all the elements of the model. they can only have cubic forms.
 * Start point of a cube according to the scheme . Values must be between -16 and 32.
 * Stop point of a cube according to the scheme . Values must be between -16 and 32.
 * Defines the rotation of an element.
 * Sets the center of the rotation according to the scheme, defaults to.
 * Specifies the direction of rotation, can be,   or.
 * Specifies the angle of rotation. Can be 45 through -45 degrees in 22.5 degree increments. Defaults to 0.
 * Specifies whether or not to scale the faces across the whole block. Can be true or false. Defaults to false.
 * Defines if shadows are rendered ( - default), not.
 * Holds all the faces of the cube. If a face is left out, it will not be rendered.
 * Contains the properties of the specified face.
 * Defines the area of the texture to use according to the scheme . If unset, it defaults to values equal to xyz position of the element. The texture behavior will be inconsistent if UV extends below 0 or above 16. If the numbers of.
 * Specifies whether a face does not need to be rendered when there is a block touching it in the specified position. The position can be:,  ,  ,  ,  , or.
 * Rotates the texture in increments of 90 degrees.
 * Determines whether to tint the texture using a hardcoded tint index. The default is not using the tint, and any number causes it to use tint. Note that only certain blocks have a tint index, all others will be unaffected.
 * Determines whether to tint the texture using a hardcoded tint index. The default is not using the tint, and any number causes it to use tint. Note that only certain blocks have a tint index, all others will be unaffected.

Example: Standing Torch
For simplicity, this example only describes the standing torch, which is defined in the files  and   stored in the folder.

File: torch.json

{   "ambientocclusion": false, "textures": { "particle": "#torch" },   "elements": [ {  "from": [ 7, 0, 7 ], "to": [ 9, 10, 9 ], "shade": false, "faces": { "down": { "uv": [ 7, 13, 9, 15 ], "texture": "#torch" }, "up":  { "uv": [ 7,  6, 9,  8 ], "texture": "#torch" } }       },        {   "from": [ 7, 0, 0 ], "to": [ 9, 16, 16 ], "shade": false, "faces": { "west": { "uv": [ 0, 0, 16, 16 ], "texture": "#torch" }, "east": { "uv": [ 0, 0, 16, 16 ], "texture": "#torch" } }       },        {   "from": [ 0, 0, 7 ], "to": [ 16, 16, 9 ], "shade": false, "faces": { "north": { "uv": [ 0, 0, 16, 16 ], "texture": "#torch" }, "south": { "uv": [ 0, 0, 16, 16 ], "texture": "#torch" } }       }    ] }

This file is used to create the model of the torch, which is used for the normal and the redstone torch. Therefore the -tag is used to create three elements or cubes. Only two faces of each cube are rendered, as only two faces of each one have been specified. is used to determine the area where the texture is used. The texture variable  is used for the particles and the cubes and has not yet been defined.

File: normal_torch.json

{   "parent": "block/torch", "textures": { "torch": "blocks/torch_on" } }

This file represents the model of the normal standing torch. It loads the model of previously defined standing torch with the help of  and inherits all the properties of the file. As this file is only used for the normal torch, the texture can now be specified. The texture is now assigned to the texture variable    (without  ) and will therefore be used for the previously loaded model and its particles, as specified in the other file.

Example: Any Block
This example describes the fundamental structure of most normal blocks in Minecraft. All these blocks use the same basic model and only apply their texture to it, as already described in the example above. This model is defined in the file  which can be found in the folder. File: cube.json

{   "elements": [ {  "from": [ 0, 0, 0 ], "to": [ 16, 16, 16 ], "faces": { "down": { "texture": "#down", "cullface": "down" }, "up":   { "texture": "#up", "cullface": "up" }, "north": { "texture": "#north", "cullface": "north" }, "south": { "texture": "#south", "cullface": "south" }, "west": { "texture": "#west", "cullface": "west" }, "east": { "texture": "#east", "cullface": "east" } }       }    ] }

Features, that have already been described above will not be mentioned again. The use of  prevents the bottom face of the block from being rendered, if there is another adjacent block underneath it. The same applies to all the other faces of the block.

Example: Sapling
This example describes the fundamental structure used by all saplings, without assigning a specific texture. The model is specified in, the texture would e.g. be assigned in. Both files are stored in the folder.

File: cross.json

{   "ambientocclusion": false, "textures": { "particle": "#cross" },   "elements": [ {  "from": [ 0.8, 0, 8 ], "to": [ 15.2, 16, 8 ], "rotation": { "origin": [ 8, 8, 8 ], "axis": "y", "angle": 45, "rescale": true }, "shade": false, "faces": { "north": { "uv": [ 0, 0, 16, 16 ], "texture": "#cross" }, "south": { "uv": [ 0, 0, 16, 16 ], "texture": "#cross" } }       },        {   "from": [ 8, 0, 0.8 ], "to": [ 8, 16, 15.2 ], "rotation": { "origin": [ 8, 8, 8 ], "axis": "y", "angle": 45, "rescale": true }, "shade": false, "faces": { "west": { "uv": [ 0, 0, 16, 16 ], "texture": "#cross" }, "east": { "uv": [ 0, 0, 16, 16 ], "texture": "#cross" } }       }    ] }

To create the usual shape of the saplings, both elements are being rotated by 45 degrees. Therefor the origin and the axis of rotation are set to the specified values, the angle is set to 45 degrees and  is set to. The latter causes the model to be scaled on the axes it has not been rotated on, so that it takes up the same space as it did before rotating it (see comparison images).

Item models
As items do not have different variants, there is no need to specify them. The folder  contains all the model files. The names of the files are hardcoded and should not be changed.


 * The root tag
 * Loads a different model from the given path, starting in.
 * Can be set to  to use a model that is created out of the specified icon.
 * Can be set to  to load a model from an entity file. As you can not specify the entity, this does not work for all items (only for chests, ender chests, mob heads and banners).
 * Needs to be set to  or   for the compass and the clock.
 * Holds the textures of the model. Each texture starts in  or can be another texture variable.
 * Only used to specify the icon of the item used in the inventory. There can be more than just one layer (e.g. for spawn eggs), but the amount of possible layers is hardcoded for each item. Only works in combination with.
 * What texture to load particles from. Used to determine the "crumb" particles generated by food items, as well as to determine the barrier particle but not for the block itself, which otherwise will use "layer0".
 * Defines a texture variable and assigns it a texture.
 * Contains all the elements of the model. They can only have cubic forms.
 * Start point of a cube according to the scheme . Values must be between -16 and 32.
 * Stop point of a cube according to the scheme . Values must be between -16 and 32.
 * Defines the rotation of an element.
 * Sets the center of the rotation according to the scheme, defaults to.
 * Specifies the direction of rotation, can be,   or.
 * Specifies the angle of rotation. Can be 45 through -45 degrees in 22.5 degree increments. Defaults to 0.
 * Holds all the faces of the cube. If a face is left out, it will not be rendered.
 * Contains the properties of the specified face.
 * Defines the area of the texture to use according to the scheme . If unset, it defaults to values equal to xyz position of the element. The texture behavior will be inconsistent if UV extends below 0 or above 16. If the numbers of.
 * Specifies whether non-visible elements should be rendered, or not.
 * Rotates the texture in increments of 90 degrees.
 * Determines whether to tint the texture using a hardcoded tint index. The default is not using the tint, and any number causes it to use tint. Note that only certain items or certain layers of items (e.g. potions) have a tint index, all others will be unaffected.
 * Holds the different places where item models are displayed.
 * Place where an item model is displayed. Holds its rotation, translation and scale for the specified situation. fixed refers to item frames, while the rest are as their name states.
 * Specifies the rotation of the model according to the scheme.
 * Specifies the translation of the model according to the scheme . If the value is greater than 24, it is displayed as 24. If the value is less then -24, it is displayed as -24.
 * Specifies the scale of the model according to the scheme . If the value is greater than 4, it is displayed as 4.
 * Specifies the scale of the model according to the scheme . If the value is greater than 4, it is displayed as 4.

Example: Torch
This example describes the torch as an item. The model can be found in the, which is stored in the folder.

File: torch.json

{   "parent": "builtin/generated", "textures": { "layer0": "blocks/torch_on" }   "display": { "thirdperson": { "rotation": [ -90, 0, 0 ], "translation": [ 0, 1, -3 ], "scale": [ 0.55, 0.55, 0.55 ] },       "firstperson": { "rotation": [ 0, -135, 25 ], "translation": [ 0, 4, 2 ], "scale": [ 1.7, 1.7, 1.7 ] }   } }

The -tag uses , so that  game uses the standard model of the torch, which has been generated out of the 2D graphic used for the item icon. The icon is specified with the -tag and the texture, that has already been used for the block model, is used for the icon as well. As there is just one layer hard coded for the torch, there cannot be any more layers added. Furthermore, the display properties for the torch are specified, so that it will be displayed correctly in every possible situation. The torch cannot be placed on a players head and uses the specified icon in the inventory, so there is no need to adjust the model for these situations. To line the model up with the players hand in first and third person view, the model needs to be rotated, moved and scaled, which is done for each of the two situation separately.

History
Modèles Modele bloków 方块模型