Upstream/dynmap
1
0
Fork 0
mirror of https://github.com/webbukkit/dynmap.git synced 2024-11-22 02:05:33 +01:00
Code Issues Projects Releases Wiki Activity

Updated Defining a Block using a Custom Block Renderer (markdown)

mikeprimm 2013-11-28 07:27:21 -08:00
parent e215779a97
commit ccf7aadef0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Defining-a-Block-using-a-Custom-Block-Renderer.md

@ -8,4 +8,4 @@ Next, the texture references need to be defined in order to supply the textures
block:id=128,data=*,patch0=0:sandstone_normal,patch1=0:sandstone_top,patch2=0:sandstone_bottom,transparency=SEMITRANSPARENT
Note: most custom renderers define blocks that are not full, opaque blocks, so the *transparency* attribute is generally required on the "block:" line.
Note: most custom renderers define blocks that are not full, opaque blocks, so the *transparency* attribute is generally required on the "block:" line. Use the TRANSPARENT setting for blocks that do not block light to other blocks, or SEMITRANSPARENT for blocks that do block light to other blocks (like slabs and stairs).