Upstream
/
dynmap
mirror of https://github.com/webbukkit/dynmap.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Page: Special texture file types
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.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 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
1 Special texture file types
mikeprimm edited this page 2013-11-25 21:15:34 -08:00

Besides the default format (a grid of xcount by ycount textures), a number of other special texture file formats are supported by Dynmap. The currently defined types include the following:

  • GRID - this is the default format, corresponding to an array of square textures <xcount> wide and <ycount> high. Each texture needs to be an even power of 2 pixels across. The index of the textures is ordered from the top left (index=0) moving to the right across the first row (ending with index=<xcount>-1), before advancing to the left edge of the next row (index=<xcount>), and so forth.

  • CHEST - this is the format corresponding to the texture layout for small chests. The index values are:

    • 0 : Chest top
    • 1 : Chest left side
    • 2 : Chest right side
    • 3 : Chest front side
    • 4 : Chest back side
    • 5 : Chest bottom

  • BIGCHEST - this is the format corresponding to the texture layout for large chests. The index values are:

    • 0 : Chest top - left side
    • 1 : Chest top - right side
    • 2 : Chest front - left side
    • 3 : Chest front - right side
    • 4 : Chest left side
    • 5 : Chest right side
    • 6 : Chest back - left side
    • 7 : Chest back - right side
    • 8 : Chest bottom - left side
    • 9 : Chest bottom - right side

  • SIGN - this is the format corresponding to the texture layout for signposts. The index values are:

    • 0 : Sign front side
    • 1 : Sign back side
    • 2 : Sign top
    • 3 : Sign bottom
    • 4 : Sign left side
    • 5 : Sign right side
    • 6 : Post front side
    • 7 : Post back side
    • 8 : Post left side
    • 9 : Post right side

  • SKIN - this is the format corresponding to the texture for a player (or other human shaped skin). The index values are:

    • 0 : Face front side
    • 1 : Face left side
    • 2 : Face right side
    • 3 : Face back side
    • 4 : Face top
    • 5 : Face bottom

  • CUSTOM - this is the more flexible format, allowing extraction of arbitrary rectangular textures as indexed textures. The <xcount> and <ycount> values are used to detect the scale of the texture image (working on the assumption that the nominal size of the texture is 16 * <xcount> by 16 * <ycount> pixels). The attributes of the 'texturefile:' definition need to include one 'tile<N>=" attribute for each texture index (where N = 0, 1, 2, etc). The value of the field corresponds to:

    tile=:/:

or, optionally:

 tile<N>=<source-offset-X>:<source-offset-Y>/<dimension-X>:<dimension-Y>/<dest-offset-X>:<dest-offset-Y>

Where:

  • <source-offset-X> is the X coordinate of the top left corner of the texture within the texture file, in scaled pixels
  • <source-offset-Y> is the Y coordinate of the top left corner of the texture within the texture file, in scaled pixels
  • <dimension-X> is the horizontal texture within the texture file, in scaled pixels
  • <dimension-Y> is the vertical texture within the texture file, in scaled pixels
  • <dest-offset-X> is the X coordinate of the top left corner of the texture in the destination texture (default is 0), in scaled pixels
  • <dest-offset-Y> is the Y coordinate of the top left corner of the texture in the destination texture (default is 0), in scaled pixels

Contents

Setup

Advanced Configuration

Mod Support

Developers