mirror of
https://github.com/webbukkit/dynmap.git
synced 2024-09-27 13:22:34 +02:00
Updated Custom Block Definitions (markdown)
parent
1d275b4839
commit
948dd063b6
@ -4,7 +4,7 @@ Dynmap supports a data-driven method for defining support for new Minecraft Bloc
|
|||||||
|
|
||||||
The rendering of block in Dynmap is accomplished via a number of distinctive mechanisms, reflecting the needs of the different types of blocks defined by Minecraft and by its mods. In all cases, the rendering of a block consists of two core elements: a **model** defining the shape of the block to be rendered, and a set of **textures** used to apply color to the various surfaces of that shape. Thanks to the very 'blocky' nature of Minecraft, the majority of blocks are shaped like simple cubes: consequently, most blocks do not need a custom **model**, and can instead be assumed to be a simple solid cube.
|
The rendering of block in Dynmap is accomplished via a number of distinctive mechanisms, reflecting the needs of the different types of blocks defined by Minecraft and by its mods. In all cases, the rendering of a block consists of two core elements: a **model** defining the shape of the block to be rendered, and a set of **textures** used to apply color to the various surfaces of that shape. Thanks to the very 'blocky' nature of Minecraft, the majority of blocks are shaped like simple cubes: consequently, most blocks do not need a custom **model**, and can instead be assumed to be a simple solid cube.
|
||||||
|
|
||||||
Support files for custom blocks defined by add-on mods are provided through the definition of two files for each mod: one defining the texture mapping (following the naming convention '*-texture.txt', and placed in the 'renderdata' directory (or in a subdirectory under that directory)), and a second defining the models for blocks that are not simple cubes (following the naming convention '*-models.txt', and also placed in the 'renderdata' directory, or a subdirectory). For mods that have nothing but simple cubes, no *-models.txt file is required (as the model for any block without a model defined is assumed to be a simple cube).
|
Support files for custom blocks defined by add-on mods are provided through the definition of two files for each mod: one defining the texture mapping (following the naming convention '**-texture.txt', and placed in the 'renderdata' directory (or in a subdirectory under that directory)), and a second defining the models for blocks that are not simple cubes (following the naming convention '**-models.txt', and also placed in the 'renderdata' directory, or a subdirectory). For mods that have nothing but simple cubes, no **-models.txt file is required (as the model for any block without a model defined is assumed to be a simple cube).
|
||||||
|
|
||||||
## Creating Texture and Model Definition Files
|
## Creating Texture and Model Definition Files
|
||||||
* For features common to both texture and model definitions files, see [[Common Features for Texture and Model Definition Files]]
|
* For features common to both texture and model definitions files, see [[Common Features for Texture and Model Definition Files]]
|
||||||
|
Loading…
Reference in New Issue
Block a user