Anything that involves the artificial generation of maps, using them for dedicated displays, scoreboards, textures, or about anything else, that is not just some "enhanced markers" on the default vanilla map. There are a few aspects that make the API unnecessarily hard to use, limited, and – generally speaking – unfit for anything that is not based on the initial purpose of maps. The Problems with the Bukkit Map APIīukkit's API regarding maps is very shallow. So while maps initially look like an easy way to implement flexible textures and interactive displays within Minecraft, we sadly came to realize, that it won't be quite as easy, as it seems.
This means that maps can now be used as HUDs and overlays, which otherwise would not be possible. The Invisible tag does not only reduce the offset from the attached face of the block but also allows to let the block face look through in transparent areas of the map. The introduction of the Invisible entity tag and the use of transparency within the image lifted maps to a whole new level and made it almost mandatory to utilize them in some way or another. With Minecraft 1.16 they became even better. They offer a canvas of 128x128 pixels that can be flexibly drawn and changed as often as desired. One of the best ways to display a huge amount of data inside of Minecraft within very limited spaces is using maps.
Although they are static, there are still many advantages in using our map API for more control over how the content is rendered, when it is sent, and how it can be interacted with. 23 min read The "MISSING" posters on the hub server of JustChunks are one of the many use cases for our new map API.
0 kommentar(er)
