Upstream/dynmap
1
0
Fork 0
mirror of https://github.com/webbukkit/dynmap.git synced 2024-11-21 17:55:22 +01:00
Code Issues Projects Releases Wiki Activity
Page: Defining a Block using a Volumetric Model
Pages
. AWS S3 Storage Addons Advanced Map Configuration Base Plugin Settings Boosting areas on Dynmap BoxRenderer Class Chunk Status Colors Chunk Version Colors Color Schemes Commands Common Features for Texture and Model Definition Files Component Configuration Configuration Configuration.txt Configuring Maps and Worlds using dmap Credits Custom Block Definitions Defining a Block using a Custom Block Renderer Defining a Block using a Volumetric Model Defining a Cuboid Block Defining a Simple Block Defining cuboid models Defining custom lightings Defining custom perspectives Defining custom shaders Defining volumetric models Dmarker Dynmap API Dynmap On Xenon Hosting Service, courtesy of mavbear Dynmap With IIS Using URL Rewrite and applicationrequestrouting thanks to kekec852 Dynmap with Apache httpd on Arch Linux Dynmap with IIS Dynmap with Nginx server on Centos Dynmap with Nginx Dynmap with apache2 on Debian Dynmap with lighttpd on Arch Linux Earthmc maps Example configurations and demo website Exporting World Data in Wavefront OBJ Format External Webserver Basics External Webserver on Linux External Webserver on Windows External Webserver on hosting providers FAQ Features FenceWallBlockRenderer Class File System Storage Forwarding Dynmap port through cloudflare Full list of predefined perspectives Guides HD Map Configuration Home How to compile Dynmap Incompatible mods Installation Setup of Dynmap on Linux Installation Internal Webserver with Caddy as a Reverse Proxy (Linux) Internal Webserver Lighttpd and SQLite on a Raspberry Pi 4 with DietPi Model Definition Files MySQL MariaDB Storage Nginx as a Reverse Proxy OCI; Oracle Cloud Instance; Quick how to enable DynMap PaneRenderer Class Permissions PostgreSQL Storage RedstoneWireRenderer Class Resources SQLite Storage Setting up Dynamic Map with apache2 under Debian Setting up Dynmap through hosting services Setting up the Dynamic Map plugin under Windows Setting up without the Internal Web Server SkullRenderer Class Special texture file types StairBlockRenderer Class Storage Setup Support for Minecraft Servers other than CraftBukkit Support for MinecraftForge based mods Support for Tekkit Texture Definition Files Textures of Dynmap Use dynmap via Pterodactyl Using Markers Using custom block renderers Web Setup Web UI Parameters Web ui login support and permissions World and template settings [Tutorial] Setting up a standalone web server with MySQL SQLite limiting render area
3 Defining a Block using a Volumetric Model
FedUpWith-Tech edited this page 2021-09-24 15:02:43 -04:00

Blocks based on volumetric models can have relatively complex shapes, while still using the same texture definition scheme as used for simple, solid blocks or cuboid blocks. The application of textures to the volumetric models follow the same pattern as is done for simple cubes and for cubiod models - the texture for each of the 6 faces is applied to the corresponding side of any of the subblocks within the model, with the texture scaled to the full size of the cube face. Consequently, the texture definitions in the Texture Definition Files are defined in the same way as for simple solid blocks and for cubiod models.

A volumetric model is defined by first cutting the full cube into a number of subblocks, based on a provided scale attribute - resulting in the block being represented by scale x scale x scale subblocks. Then, each of the subblocks that are occupied, or filled, by the shape of the model is marked, allowing any arrangement of the subblocks to be created. For details, see Defining Volumetric Models. An example of a block representable by a volumetric model is the Hopper block;

 block:id=154,data=*,scale=16
 layer:0,1,2,3
 ----------------
 ----------------
 ----------------
 ----------------
 ----------------
 ----------------
 ------****------
 ------****------
 ------****------
 ------****------
 ----------------
 ----------------
 ----------------
 ----------------
 ----------------
 ----------------
 layer:4,5,6,7,8,9
 ----------------
 ----------------
 ----------------
 ----------------
 ----********----
 ----********----
 ----********----
 ----********----
 ----********----
 ----********----
 ----********----
 ----********----
 ----------------
 ----------------
 ----------------
 ----------------
 layer:10
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 ****************
 layer:11,12,13,14,15
 ****************
 ****************
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 **------------**
 ****************
 ****************

One the model is defined, the texture references are supplied in the same way as a simple, solid block - see Defining a Simple Block for details. For the Hopper block, the definition is:

 block:id=154,data=*,allsides=0:hopper_outside,top=0:hopper_inside,bottom=0:hopper_outside,stdrot=true

Contents

Setup

Advanced Configuration

Mod Support

Developers