Upstream
/
dynmap
mirror of https://github.com/webbukkit/dynmap.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Texture Definition Files (markdown)

mikeprimm 2013-11-27 20:16:00 -08:00
parent 8be027e4ce
commit abfd9fafe8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Texture-Definition-Files.md

@ -109,6 +109,6 @@ Besides selecting the texture to be used, a texture reference can also specify o
The definition of textures for a specific block requires identifying which block ID is being used by the given block type. While built-in Minecraft standard blocks currently have fixed block ID values, the block IDs for all MinecraftForge mods are controlled through their configuration files. These IDs are loaded via the "cfgfile:" directive (see [[Common Features for Texture and Model Definition Files]] for details on this directive, and the mapping of settings from configuration files to usable symbol names). In all block definition directives, the block ID is specified via the 'id=' attribute. The values of the 'id=' attribute can be a number (a constant), a symbol name corresponding to a setting from the mod's configuration file, or a combination of a symbol name, a plus (\+), and a number. In all cases, if the value of the ID is zero or negative, the ID value will be ignored (allowing disabled blocks to be easily ignored).
## Defining Block Texture Mappings
To define a simple, solid cube block, see [[Defining a Simple Block]]
To define a block based on a custom block renderer, see [[Defining a Block using a Custom Block Renderer]]
* To define a simple, solid cube block, see [[Defining a Simple Block]]
* To define a block based on a custom block renderer, see [[Defining a Block using a Custom Block Renderer]]