first commit

config/bluemap/maps/new_world_the_end.conf

@@ -0,0 +1,126 @@
+##                          ##
+##         BlueMap          ##
+##        Map-Config        ##
+##                          ##
+
+# The path to the save-folder of the world to render.
+#  (If this is not defined (commented out or removed), the map will be only registered to the web-server and the web-app
+#   but not rendered or loaded by BlueMap. This can be used to display a map that has been rendered somewhere else.)
+world: "saves/New World"
+
+# The dimension of the world. Can be "minecraft:overworld", "minecraft:the_nether", "minecraft:the_end"
+# or any dimension-key introduced by a mod or datapack.
+dimension: "minecraft:the_end"
+
+# The display-name of this map -> how this map will be named on the webapp.
+# You can change this at any time.
+# Default is the id of this map
+name: "New World (the_end)"
+
+# A lower value makes the map sorted first (in lists and menus), a higher value makes it sorted later.
+# The value needs to be an integer but it can be negative.
+# You can change this at any time.
+# Default is 0
+sorting: 200
+
+# The position on the world where the map will be centered if you open it.
+# You can change this at any time.
+# This defaults to the world-spawn if you don't set it.
+#start-pos: {x:500, z:-820}
+
+# The color of the sky as a hex-color
+# You can change this at any time.
+# Default is "#7dabff"
+sky-color: "#080010"
+
+# The color of the void as a hex-color
+# You can change this at any time.
+# Default is "#000000"
+void-color: "#080010"
+
+# Defines the ambient light-strength that every block is receiving, regardless of the sunlight/blocklight.
+# 0 is no ambient light, 1 is fully lighted.
+# You can change this at any time.
+# Default is 0
+ambient-light: 0.6
+
+# BlueMap tries to omit all blocks that are below this Y-level and are not visible from above-ground.
+# More specific: Block-Faces that have a sunlight/skylight value of 0 are removed.
+# This improves the performance of the map on slower devices by a lot, but might cause some blocks to disappear that should normally be visible.
+# Changing this value requires a re-render of the map.
+# Set to a very high value to remove caves everywhere (e.g. 10000)
+# Set to a very low value to remove nothing and render all caves (e.g. -10000)
+# Default is 55 (slightly below water-level)
+remove-caves-below-y: -10000
+
+# This is the amount of blocks relative to the "ocean-floor" heightmap that the cave-detection will start at.
+# Everything above that (heightmap-relative) y-level will not be removed.
+# Comment or set to a very high value to disable using the ocean-floor heightmap for cave-detection.
+# Changing this value requires a re-render of the map.
+# Defaults to 10000 (disabled)
+cave-detection-ocean-floor: -5
+
+# With this value set to true, BlueMap also uses the block-light value (additionally to the sky-light) to "detect caves".
+# (See: remove-caves-below-y)
+# Changing this value requires a re-render of the map.
+# Default is false
+cave-detection-uses-block-light: false
+
+# With the below values you can limit the map-render.
+# This can be used to ignore the nethers ceiling or render only a certain part of a world.
+# If you change these values, bluemap automatically tries to update the map,
+# including deleting map-tiles which are outside the new limits.
+# Default is no min or max value (= infinite bounds)
+#min-x: -4000
+#max-x: 4000
+#min-z: -4000
+#max-z: 4000
+#min-y: 50
+#max-y: 100
+
+# The minimum "inhabitedTime" value that a chunk must have to be rendered.
+# If you set this to a value greater than 0, bluemap will only render chunks that players have visited already.
+# Default is 0
+min-inhabited-time: 0
+
+# Using this, BlueMap pretends that every Block out of the defined render-bounds is AIR,
+# this means you can see the blocks where the world is cut (instead of having a see-through/xray view).
+# This has only an effect if you set some render-bounds above.
+# Changing this value requires a re-render of the map.
+# Default is true
+render-edges: true
+
+# Whether the hires-layer will be saved to the storage.
+# Disabling this will speed up rendering and reduce the size of the map-files a lot.
+# But you will not be able to see the full 3d-models if you zoom in on the map.
+# Changing this to false will not remove any existing tiles, existing tiles just won't get updated anymore.
+# Changing this to true will require a re-render of the map.
+# Default is true
+save-hires-layer: true
+
+# This defines the storage-config that will be used to save this map.
+# You can find your storage configs next to this config file in the 'storages'-folder.
+# Changing this value requires a re-render of the map. The map in the old storage will not be deleted.
+# Default is "file"
+storage: "file"
+
+# Normally BlueMap detects if a chunk has not yet generated it's light-data and omits rendering those chunks.
+# If this is set to true BlueMap will render Chunks even if there is no light-data!
+# This can be useful for example if some mod prevents light-data from being saved correctly.
+# However, this also has a few drawbacks:
+# - For those chunks, every block will always be fully lit
+# - Night-mode might not work correctly
+# - Caves will always be rendered (ignoring the 'renderCaves' setting)
+# Default is false
+ignore-missing-light-data: false
+
+# Here you can define any static marker-sets with markers that should be displayed on the map.
+# You can change this at any time.
+# If you need dynamic markers, you can use any plugin that integrates with BlueMap's API.
+# Here is a list: https://bluemap.bluecolored.de/community/3rdPartySupport.html
+marker-sets: {
+
+  # Please check out the wiki for information on how to configure this:
+  # https://bluemap.bluecolored.de/wiki/customization/Markers.html
+
+}