From b9764512ef7252e7b82bc0f2b9b0342f3ce0bc7c Mon Sep 17 00:00:00 2001 From: mikeprimm Date: Sun, 19 Dec 2021 22:57:14 -0600 Subject: [PATCH] Updated Defining custom shaders (markdown) --- Defining-custom-shaders.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Defining-custom-shaders.md b/Defining-custom-shaders.md index 121ea27..b1be721 100644 --- a/Defining-custom-shaders.md +++ b/Defining-custom-shaders.md @@ -10,6 +10,10 @@ There are currently three basic classes of shaders, any of which can be used to - **org.dynmap.hdmap.TopoHDShader** - this shader colors the map to present a topographical map view, based on altitude of the blocks rendered. +- **org.dynmap.hdmap.ChunkStatusHDShader** - this is a diagnostic shader, that can be used to produce a map of the 'Status' of the various chunks in a world - see [Chunk Status Colors] for mapping of status values to colors. + +- **org.dynmap.hdmap.ChunkVersionHDShader** - this is a diagnostic shader, that can be used to produce a map of the 'DataVersion' of the various chunks in a world, which are mapped to colors based on the Minecraft version of the current encoding of a given chunk (worlds created using older versions of Minecraft are often not upgraded automatically until they are loaded by player activity after a server is upgraded) - see [Chunk Version Colors] for mapping of status values to colors. + ## Defining a custom DefaultHDShader shader The DefaultHDShader class supports the following configuration settings: