From c21fd0c7eadb8ead26a2d65ede991a78b57cda1c Mon Sep 17 00:00:00 2001 From: Kappeh Date: Wed, 7 May 2025 14:22:05 +0000 Subject: [PATCH] Add Bluemap --- .env.example | 1 + .gitignore | 17 ++ bluemap/config/core.conf | 48 ++++++ bluemap/config/maps/creative.conf | 126 +++++++++++++++ bluemap/config/maps/redstoner_bigplots.conf | 126 +++++++++++++++ bluemap/config/maps/redstoner_creative.conf | 126 +++++++++++++++ bluemap/config/maps/redstoner_trusted.conf | 126 +++++++++++++++ bluemap/config/maps/survival_1.conf | 126 +++++++++++++++ bluemap/config/maps/survival_1_nether.conf | 126 +++++++++++++++ bluemap/config/maps/survival_1_the_end.conf | 126 +++++++++++++++ bluemap/config/maps/synergy_plots_1.conf | 126 +++++++++++++++ bluemap/config/storages/file.conf | 22 +++ bluemap/config/webapp.conf | 71 +++++++++ bluemap/config/webserver.conf | 45 ++++++ bluemap/data/.keep | 0 bluemap/maps/.keep | 0 docker-compose.yml | 29 ++++ fabric/config/bluemap/core.conf | 48 ++++++ fabric/config/bluemap/maps/creative.conf | 147 ++++++++++++++++++ fabric/config/bluemap/plugin.conf | 72 +++++++++ fabric/config/bluemap/storages/file.conf | 22 +++ fabric/config/bluemap/webapp.conf | 75 +++++++++ fabric/config/bluemap/webserver.conf | 45 ++++++ fabric/data/bluemap/web/maps/.keep | 0 paper/data/bluemap/web/maps/.keep | 0 paper/data/bukkit.yml | 3 + paper/plugins/BlueMap/core.conf | 48 ++++++ .../BlueMap/maps/redstoner_bigplots.conf | 126 +++++++++++++++ .../BlueMap/maps/redstoner_creative.conf | 126 +++++++++++++++ .../BlueMap/maps/redstoner_trusted.conf | 126 +++++++++++++++ paper/plugins/BlueMap/maps/survival_1.conf | 126 +++++++++++++++ .../BlueMap/maps/survival_1_nether.conf | 126 +++++++++++++++ .../BlueMap/maps/survival_1_the_end.conf | 126 +++++++++++++++ .../plugins/BlueMap/maps/synergy_plots_1.conf | 147 ++++++++++++++++++ paper/plugins/BlueMap/plugin.conf | 72 +++++++++ paper/plugins/BlueMap/storages/file.conf | 22 +++ paper/plugins/BlueMap/webapp.conf | 75 +++++++++ paper/plugins/BlueMap/webserver.conf | 45 ++++++ 38 files changed, 2818 insertions(+) create mode 100755 bluemap/config/core.conf create mode 100755 bluemap/config/maps/creative.conf create mode 100755 bluemap/config/maps/redstoner_bigplots.conf create mode 100755 bluemap/config/maps/redstoner_creative.conf create mode 100755 bluemap/config/maps/redstoner_trusted.conf create mode 100755 bluemap/config/maps/survival_1.conf create mode 100755 bluemap/config/maps/survival_1_nether.conf create mode 100755 bluemap/config/maps/survival_1_the_end.conf create mode 100755 bluemap/config/maps/synergy_plots_1.conf create mode 100755 bluemap/config/storages/file.conf create mode 100755 bluemap/config/webapp.conf create mode 100755 bluemap/config/webserver.conf create mode 100755 bluemap/data/.keep create mode 100755 bluemap/maps/.keep create mode 100755 fabric/config/bluemap/core.conf create mode 100755 fabric/config/bluemap/maps/creative.conf create mode 100755 fabric/config/bluemap/plugin.conf create mode 100755 fabric/config/bluemap/storages/file.conf create mode 100755 fabric/config/bluemap/webapp.conf create mode 100755 fabric/config/bluemap/webserver.conf create mode 100755 fabric/data/bluemap/web/maps/.keep create mode 100755 paper/data/bluemap/web/maps/.keep create mode 100755 paper/plugins/BlueMap/core.conf create mode 100755 paper/plugins/BlueMap/maps/redstoner_bigplots.conf create mode 100755 paper/plugins/BlueMap/maps/redstoner_creative.conf create mode 100755 paper/plugins/BlueMap/maps/redstoner_trusted.conf create mode 100755 paper/plugins/BlueMap/maps/survival_1.conf create mode 100755 paper/plugins/BlueMap/maps/survival_1_nether.conf create mode 100755 paper/plugins/BlueMap/maps/survival_1_the_end.conf create mode 100755 paper/plugins/BlueMap/maps/synergy_plots_1.conf create mode 100755 paper/plugins/BlueMap/plugin.conf create mode 100755 paper/plugins/BlueMap/storages/file.conf create mode 100755 paper/plugins/BlueMap/webapp.conf create mode 100755 paper/plugins/BlueMap/webserver.conf diff --git a/.env.example b/.env.example index 91732e8..8213584 100755 --- a/.env.example +++ b/.env.example @@ -2,6 +2,7 @@ PUID=1000 PGID=1000 VELOCITY_PORT=25565 +MAP_PORT=8100 RCON_PASSWORD=ChangeMe diff --git a/.gitignore b/.gitignore index 21e17ec..de9bf9e 100755 --- a/.gitignore +++ b/.gitignore @@ -21,12 +21,29 @@ !/paper/data/plugins/WorldEdit !/paper/data/plugins/WorldEdit/schematics/ !/paper/data/plugins/WorldEdit/schematics/.keep +!/paper/data/bluemap +!/paper/data/bluemap/web +!/paper/data/bluemap/web/maps +!/paper/data/bluemap/web/maps/.keep /fabric/data/** !/fabric/data/config !/fabric/data/config/worldedit !/fabric/data/config/worldedit/schematics !/fabric/data/config/worldedit/schematics/.keep +!/fabric/data/bluemap +!/fabric/data/bluemap/web +!/fabric/data/bluemap/web/maps +!/fabric/data/bluemap/web/maps/.keep + +/bluemap/data/** +!/bluemap/data/.keep + +/bluemap/maps/** +!/bluemap/maps/.keep + +/bluemap/web/** +!/bluemap/web/.keep # Backups /backups/** diff --git a/bluemap/config/core.conf b/bluemap/config/core.conf new file mode 100755 index 0000000..1b1e70d --- /dev/null +++ b/bluemap/config/core.conf @@ -0,0 +1,48 @@ +## ## +## BlueMap ## +## Core-Config ## +## ## + +# By changing the setting (accept-download) below to TRUE you are indicating that you have accepted mojang's EULA (https://account.mojang.com/documents/minecraft_eula), +# you confirm that you own a license to Minecraft (Java Edition) +# and you agree that BlueMap will download and use a minecraft-client file (depending on the minecraft-version) from mojangs servers (https://piston-meta.mojang.com/) for you. +# This file contains resources that belong to mojang and you must not redistribute it or do anything else that is not compliant with mojang's EULA. +# BlueMap uses resources in this file to generate the 3D-Models used for the map and texture them. (BlueMap will not work without those resources.) +# 2025-04-25T09:16:33 +accept-download: true + +# The folder where bluemap saves data-files it needs during runtime or to save e.g. the render-progress to resume it later. +# Default is "bluemap" +data: "data" + +# This changes the amount of threads that BlueMap will use to render the maps. +# A higher value can improve render-speed but could impact performance on the host machine. +# This should be always below or equal to the number of available processor-cores. +# Zero or a negative value means the amount of available processor-cores subtracted by the value. +# (So a value of -2 with 6 cores results in 4 render-processes) +# Default is 1 +render-thread-count: 1 + +# Controls whether BlueMap should try to find and load mod-resources and datapacks from the server/world-directories. +# Default is true +scan-for-mod-resources: true + +# If this is true, BlueMap might send really basic metrics reports containing only the implementation-type and the version that is being used to https://metrics.bluecolored.de/bluemap/ +# This allows me to track the basic usage of BlueMap and helps me stay motivated to further develop this tool! Please leave it on :) +# An example report looks like this: {"implementation":"bukkit","version":"5.4","mcVersion":"?"} +# Default is true +metrics: false + +# Config-section for debug-logging +log: { + # The file where the debug-log will be written to. + # Comment out to disable debug-logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "data/logs/debug.log" + # file: "data/logs/debug_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false +} diff --git a/bluemap/config/maps/creative.conf b/bluemap/config/maps/creative.conf new file mode 100755 index 0000000..e017023 --- /dev/null +++ b/bluemap/config/maps/creative.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: "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:overworld" + +# 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: "Creative" + +# 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: 0 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/maps/redstoner_bigplots.conf b/bluemap/config/maps/redstoner_bigplots.conf new file mode 100755 index 0000000..3776996 --- /dev/null +++ b/bluemap/config/maps/redstoner_bigplots.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: "redstoner_bigplots" + +# 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:overworld" + +# 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: "Redstoner | Big Plots" + +# 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: 500 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/maps/redstoner_creative.conf b/bluemap/config/maps/redstoner_creative.conf new file mode 100755 index 0000000..3d2c22f --- /dev/null +++ b/bluemap/config/maps/redstoner_creative.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: "redstoner_creative" + +# 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:overworld" + +# 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: "Redstoner | Creative" + +# 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: 400 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/maps/redstoner_trusted.conf b/bluemap/config/maps/redstoner_trusted.conf new file mode 100755 index 0000000..44773bc --- /dev/null +++ b/bluemap/config/maps/redstoner_trusted.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: "redstoner_trusted" + +# 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:overworld" + +# 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: "Redstoner | Trusted" + +# 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: 600 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/maps/survival_1.conf b/bluemap/config/maps/survival_1.conf new file mode 100755 index 0000000..2646853 --- /dev/null +++ b/bluemap/config/maps/survival_1.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: "survival" + +# 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:overworld" + +# 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: "Survival 1 | Overworld" + +# 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: 100 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/maps/survival_1_nether.conf b/bluemap/config/maps/survival_1_nether.conf new file mode 100755 index 0000000..2afb835 --- /dev/null +++ b/bluemap/config/maps/survival_1_nether.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: "survival_nether" + +# 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:overworld" + +# 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: "Survival 1 | Nether" + +# 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: "#290000" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#150000" + +# 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: 90 + +# 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 + +} diff --git a/bluemap/config/maps/survival_1_the_end.conf b/bluemap/config/maps/survival_1_the_end.conf new file mode 100755 index 0000000..43c47b2 --- /dev/null +++ b/bluemap/config/maps/survival_1_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: "survival_the_end" + +# 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:overworld" + +# 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: "Survival 1 | 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: 300 + +# 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 + +} diff --git a/bluemap/config/maps/synergy_plots_1.conf b/bluemap/config/maps/synergy_plots_1.conf new file mode 100755 index 0000000..b125a73 --- /dev/null +++ b/bluemap/config/maps/synergy_plots_1.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: "synergy_plots_1" + +# 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:overworld" + +# 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: "Synergy | Plots 1" + +# 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: 700 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/bluemap/config/storages/file.conf b/bluemap/config/storages/file.conf new file mode 100755 index 0000000..f33dbb8 --- /dev/null +++ b/bluemap/config/storages/file.conf @@ -0,0 +1,22 @@ +## ## +## BlueMap ## +## Storage-Config ## +## ## + +# The storage-type of this storage. +# Depending on this setting, different config-entries are allowed/expected in this config file. +# Don't change this value! (If you want a different storage-type, check out the other example-configs) +storage-type: file + +# The path to the folder on your file-system where bluemap will save the rendered map +# The default is: "bluemap/web/maps" +root: "web/maps" + +# The compression-type that bluemap will use to compress generated map-data. +# Available compression-types are: +# - gzip +# - zstd +# - deflate +# - none +# The default is: gzip +compression: gzip diff --git a/bluemap/config/webapp.conf b/bluemap/config/webapp.conf new file mode 100755 index 0000000..60f0e51 --- /dev/null +++ b/bluemap/config/webapp.conf @@ -0,0 +1,71 @@ +## ## +## BlueMap ## +## Webapp-Config ## +## ## + +# With this setting you can disable the creation and updating of all web-app related files +# Default is true +enabled: true + +# The webroot where the web-application files will be created. +# Usually this should be set to the same directory like in the webserver.conf! +# Default is "bluemap/web" +webroot: "web" + +# Whether the settings.json of the webapp should be updated/synchronized with the current bluemap settings. +# If this is set to "false", bluemap will only add maps to the settings.json but never remove unknown ones or update other settings. +# Disabling this is for example useful if you are running multiple bluemap instances on the same webroot and don't want them to overwrite each others maps. +# Default is true +update-settings-file: true + +# If the web-application should use cookies to save the configurations of a user. +# Default is true +use-cookies: true + +# If the free-flight-mode in the web-application is enabled or not. +# Default is true +enable-free-flight: true + +# If the webapp will default to flat-view instead of perspective-view. +# Default is false +default-to-flat-view: true + +# The default map and camera-location where a user will start after opening the webapp. +# This is in form of the url-anchor: Open your map in a browser and look at the url, everything after the '#' is the value for this setting. +# Default is "no anchor" -> The camera will start with the topmost map and at that map's starting point. +#start-location: "world:0:16:-32:390:0.1:0.19:0:0:perspective" + +# The minimum (closest) and maximum (furthest) distance (in blocks) that the camera can be from the ground +min-zoom-distance: 1 +max-zoom-distance: 100000 + +# The default value of the resolution (settings-menu) +# Possible values are: 0.5, 1, 2 +# Default is 1 +resolution-default: 1 + +# The min, max and default values of the hires render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:500 default:100 and min:0 +hires-slider-max: 2000 +hires-slider-default: 500 +hires-slider-min: 100 + +# The min, max and default values of the lowres render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:7000 default:2000 and min:500 +lowres-slider-max: 7000 +lowres-slider-default: 2000 +lowres-slider-min: 500 + +# Here you can add URLs to custom scripts (js) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +scripts: [ + #"js/my-custom-script.js" +] + +# Here you can add URLs to custom styles (css) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +styles: [ + #"css/my-custom-style.css" +] diff --git a/bluemap/config/webserver.conf b/bluemap/config/webserver.conf new file mode 100755 index 0000000..2ac70a5 --- /dev/null +++ b/bluemap/config/webserver.conf @@ -0,0 +1,45 @@ +## ## +## BlueMap ## +## Webserver-Config ## +## ## + +# With this setting you can disable the integrated web-server. +# This is useful if you want to only render the map-data for later use, or if you setup your own webserver. +# Default is enabled +enabled: true + +# The webroot that the server will host to the web. +# Usually this should be set to the same directory like in the webapp.conf! +# Default is "bluemap/web" +webroot: "web" + +# The port that the webserver listens to. +# Default is 8100 +port: 8100 + +# Config-section for webserver-activity logging +log: { + # The file where all the webserver-activity will be logged to. + # Comment out to disable the logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "data/logs/webserver.log" + #file: "data/logs/webserver_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false + + # The format of the webserver-acivity logs. + # The syntax is the java String formatting, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Possible Arguments: + # 1 - the source address (ignoring any xff headers) + # 2 - the source address (using the (leftmost) xff header if provided) + # 3 - the http-method of the request + # 4 - the full request-address + # 5 - the protocol version of the request + # 6 - the status-code of the response + # 7 - the status-message of the response + # Default is "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" + format: "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" +} diff --git a/bluemap/data/.keep b/bluemap/data/.keep new file mode 100755 index 0000000..e69de29 diff --git a/bluemap/maps/.keep b/bluemap/maps/.keep new file mode 100755 index 0000000..e69de29 diff --git a/docker-compose.yml b/docker-compose.yml index af5a2fd..153ff7b 100755 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -61,6 +61,30 @@ services: signedvelocity:Jp1p9BHR velocitab:TTtLPunq + bluemap: + image: ghcr.io/bluemap-minecraft/bluemap:v5.7 + container_name: illegal_crime_bluemap + user: "${PUID}:${PGID}" + restart: unless-stopped + depends_on: + fabric: + condition: service_healthy + restart: true + paper: + condition: service_healthy + restart: true + command: -g -w + networks: + illegal_crime_mc_network: + ipv4_address: "10.100.1.6" + ports: + - "${MAP_PORT}:8100/tcp" + volumes: + - ./bluemap/data:/app/data:rw + - ./bluemap/web:/app/web:rw + - ./bluemap/config:/app/config:rw + - ./bluemap/maps:/app/web/maps:ro + paper: image: itzg/minecraft-server:2025.3.0-java23 container_name: illegal_crime_paper @@ -81,6 +105,7 @@ services: - ./paper/config:/config:ro - ./paper/plugins:/plugins:ro - ./schematics:/data/plugins/WorldEdit/schematics:rw + - ./bluemap/maps:/data/bluemap/web/maps:rw environment: UID: "${PUID}" GID: "${PGID}" @@ -137,6 +162,8 @@ services: https://github.com/EssentialsX/Essentials/releases/download/2.20.1/EssentialsX-2.20.1.jar MODRINTH_PROJECTS: | + bluemap:NeDjOeW8 + chunky:SmZRkQyR freedomchat:NdbpBqOZ luckperms:cfNN7sys multiverse-core:jbQopAkk @@ -166,6 +193,7 @@ services: - ./fabric/data:/data:rw - ./fabric/config:/config:ro - ./schematics:/data/config/worldedit/schematics:rw + - ./bluemap/maps:/data/bluemap/web/maps:rw environment: UID: "${PUID}" GID: "${PGID}" @@ -220,6 +248,7 @@ services: MODRINTH_PROJECTS: | badpackets:hjhT2sMz block-event-separator:R7hmJOUs + bluemap:Dr2hvJBc carpet-extra:WDB4578I carpet-tis-addition:znBCTqSr cloth-config:FgXq8Sfo diff --git a/fabric/config/bluemap/core.conf b/fabric/config/bluemap/core.conf new file mode 100755 index 0000000..bf2ae06 --- /dev/null +++ b/fabric/config/bluemap/core.conf @@ -0,0 +1,48 @@ +## ## +## BlueMap ## +## Core-Config ## +## ## + +# By changing the setting (accept-download) below to TRUE you are indicating that you have accepted mojang's EULA (https://account.mojang.com/documents/minecraft_eula), +# you confirm that you own a license to Minecraft (Java Edition) +# and you agree that BlueMap will download and use a minecraft-client file (depending on the minecraft-version) from mojangs servers (https://piston-meta.mojang.com/) for you. +# This file contains resources that belong to mojang and you must not redistribute it or do anything else that is not compliant with mojang's EULA. +# BlueMap uses resources in this file to generate the 3D-Models used for the map and texture them. (BlueMap will not work without those resources.) +# 2025-04-25T16:10:09 +accept-download: true + +# The folder where bluemap saves data-files it needs during runtime or to save e.g. the render-progress to resume it later. +# Default is "bluemap" +data: "bluemap" + +# This changes the amount of threads that BlueMap will use to render the maps. +# A higher value can improve render-speed but could impact performance on the host machine. +# This should be always below or equal to the number of available processor-cores. +# Zero or a negative value means the amount of available processor-cores subtracted by the value. +# (So a value of -2 with 6 cores results in 4 render-processes) +# Default is 1 +render-thread-count: 1 + +# Controls whether BlueMap should try to find and load mod-resources and datapacks from the server/world-directories. +# Default is true +scan-for-mod-resources: true + +# If this is true, BlueMap might send really basic metrics reports containing only the implementation-type and the version that is being used to https://metrics.bluecolored.de/bluemap/ +# This allows me to track the basic usage of BlueMap and helps me stay motivated to further develop this tool! Please leave it on :) +# An example report looks like this: {"implementation":"bukkit","version":"5.7","mcVersion":"?"} +# Default is true +metrics: false + +# Config-section for debug-logging +log: { + # The file where the debug-log will be written to. + # Comment out to disable debug-logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "bluemap/logs/debug.log" + # file: "bluemap/logs/debug_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false +} diff --git a/fabric/config/bluemap/maps/creative.conf b/fabric/config/bluemap/maps/creative.conf new file mode 100755 index 0000000..4b13633 --- /dev/null +++ b/fabric/config/bluemap/maps/creative.conf @@ -0,0 +1,147 @@ +## ## +## 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: "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:overworld" + +# 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: "Creative" + +# 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: 0 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# Defines the initial sky-light-strength the map will be set to when it is opened. +# 0 is no sky-light, 1 is fully lighted. +# You can change this at any time. +# Default is 1 +sky-light: 1 + +# 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.1 + +# 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: 55 + +# 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 perspective view will be enabled for this map. +# Changing this to true requires a re-render of the map, only if the hires-layer is enabled and free-flight view is disabled. +# Default is true +enable-perspective-view: true + +# Whether the flat (isometric, top-down) view will be enabled for this map. +# Having only flat-view enabled while disabling free-flight and perspective will speed up the render and reduce the maps storage-size. +# Default is true +enable-flat-view: true + +# Whether the free-flight view will be enabled for this map. +# Changing this to true requires a re-render of the map, only if the hires-layer is enabled and perspective view is disabled. +# Default is true +enable-free-flight-view: true + +# Whether the hires-layer will be enabled. +# 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 +enable-hires: 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 + +} diff --git a/fabric/config/bluemap/plugin.conf b/fabric/config/bluemap/plugin.conf new file mode 100755 index 0000000..0fc5b38 --- /dev/null +++ b/fabric/config/bluemap/plugin.conf @@ -0,0 +1,72 @@ +## ## +## BlueMap ## +## Plugin-Config ## +## ## + +# If the server should send player-positions to the webapp. +# This only works if the integrated webserver is enabled. +# Default is true +live-player-markers: true + +# A list of gamemodes that will prevent a player from appearing on the map. +# Possible values are: survival, creative, spectator, adventure +hidden-game-modes: [ + "spectator" +] + +# If this is true, players that are vanished (by a plugin) will be hidden on the map. +# (This only works with Spigot and Sponge based vanish-plugins) +# Default is true +hide-vanished: true + +# If this is true, players that have an invisibility (potion-)effect will be hidden on the map. +# Default is true +hide-invisible: true + +# If this is true, players that are sneaking will be hidden on the map. +# Default is false +hide-sneaking: false + +# Hides the player if they are in a sky or block-light level below the given number. +# BOTH values have to be below the threshold for the player to be hidden! +# E.g. if you set both to 1, then the player will be hidden on the map if they are in absolute darkness +# Or, if you want players only be visible on the surface you set the sky-threshold to something between 1 and 15 +# and the block-threshold to 16 +# Default is 0 (don't hide the player) +hide-below-sky-light: 0 +hide-below-block-light: 0 + +# If this is true, players that are on a different world than the viewed map will not appear on the player-list. +# Default is false +hide-different-world: false + +# The interval in seconds that the markers will be written to the map-storage. +# This is useful if you can't create a live-connection between the server and the webapp +# and the markers can only be updated via the map-storage. +# 0 or lower means that the markers will never be written to the map-storage. +# Default is 0 +write-markers-interval: 10 + +# The interval in seconds that the players will be written to the map-storage. +# This is useful if you can't create a live-connection between the server and the webapp +# and the players can only be updated via the map-storage. +# 0 or lower means that the players will never be written to the map-storage. +# Default is 0 +write-players-interval: 3 + +# Download the skin from mojang-servers when a player joins your server, so it can be used for the player-markers. +# Default is true +skin-download: true + +# The amount of players that is needed to pause BlueMap's render-threads. +# -> If this amount of players or more is online, bluemap will stop rendering map-updates until enough players +# have logged off again +# Setting this to 0 or -1 will disable this feature -> bluemap will not pause rendering +# Default is -1 +player-render-limit: -1 + +# The interval in minutes in which a full map-update will be triggered. +# This is ADDITIONALLY to the normal map-update process (in case that fails to detect any file-changes). +# ! This DOESN'T re-render the entire map each time, it only checks if there are some changes that have not been rendered yet! +# Default is 1440 (24 hours) +full-update-interval: 1440 diff --git a/fabric/config/bluemap/storages/file.conf b/fabric/config/bluemap/storages/file.conf new file mode 100755 index 0000000..1a54413 --- /dev/null +++ b/fabric/config/bluemap/storages/file.conf @@ -0,0 +1,22 @@ +## ## +## BlueMap ## +## Storage-Config ## +## ## + +# The storage-type of this storage. +# Depending on this setting, different config-entries are allowed/expected in this config file. +# Don't change this value! (If you want a different storage-type, check out the other example-configs) +storage-type: file + +# The path to the folder on your file-system where bluemap will save the rendered map +# The default is: "bluemap/web/maps" +root: "bluemap/web/maps" + +# The compression-type that bluemap will use to compress generated map-data. +# Available compression-types are: +# - gzip +# - zstd +# - deflate +# - none +# The default is: gzip +compression: gzip diff --git a/fabric/config/bluemap/webapp.conf b/fabric/config/bluemap/webapp.conf new file mode 100755 index 0000000..a43d5ee --- /dev/null +++ b/fabric/config/bluemap/webapp.conf @@ -0,0 +1,75 @@ +## ## +## BlueMap ## +## Webapp-Config ## +## ## + +# With this setting you can disable the creation and updating of all web-app related files +# Default is true +enabled: false + +# The webroot where the web-application files will be created. +# Usually this should be set to the same directory like in the webserver.conf! +# Default is "bluemap/web" +webroot: "bluemap/web" + +# Whether the settings.json of the webapp should be updated/synchronized with the current bluemap settings. +# If this is set to "false", bluemap will only add maps to the settings.json but never remove unknown ones or update other settings. +# Disabling this is for example useful if you are running multiple bluemap instances on the same webroot and don't want them to overwrite each others maps. +# Default is true +update-settings-file: true + +# If the web-application should use cookies to save the configurations of a user. +# Default is true +use-cookies: true + +# If the webapp will default to flat-view instead of perspective-view. +# Default is false +default-to-flat-view: false + +# The default map and camera-location where a user will start after opening the webapp. +# This is in form of the url-anchor: Open your map in a browser and look at the url, everything after the '#' is the value for this setting. +# Default is "no anchor" -> The camera will start with the topmost map and at that map's starting point. +#start-location: "world:0:16:-32:390:0.1:0.19:0:0:perspective" + +# The minimum (closest) and maximum (furthest) distance (in blocks) that the camera can be from the ground +min-zoom-distance: 5 +max-zoom-distance: 100000 + +# The default value of the resolution (settings-menu) +# Possible values are: 0.5, 1, 2 +# Default is 1 +resolution-default: 1 + +# The min, max and default values of the hires render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:500 default:100 and min:0 +hires-slider-max: 500 +hires-slider-default: 100 +hires-slider-min: 0 + +# The min, max and default values of the lowres render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:7000 default:2000 and min:500 +lowres-slider-max: 7000 +lowres-slider-default: 2000 +lowres-slider-min: 500 + +# Here you can specify an alternative base url from where all map data is loaded. +# Default is "maps" +#map-data-root: "https://cdn.my-domain.com/mapdata" + +# Here you can specify an alternative base url from where all live data is loaded. +# Default is "maps" +#live-data-root: "https://cdn.my-domain.com/livedata" + +# Here you can add URLs to custom scripts (js) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +scripts: [ + #"js/my-custom-script.js" +] + +# Here you can add URLs to custom styles (css) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +styles: [ + #"css/my-custom-style.css" +] diff --git a/fabric/config/bluemap/webserver.conf b/fabric/config/bluemap/webserver.conf new file mode 100755 index 0000000..da85a5e --- /dev/null +++ b/fabric/config/bluemap/webserver.conf @@ -0,0 +1,45 @@ +## ## +## BlueMap ## +## Webserver-Config ## +## ## + +# With this setting you can disable the integrated web-server. +# This is useful if you want to only render the map-data for later use, or if you setup your own webserver. +# Default is enabled +enabled: false + +# The webroot that the server will host to the web. +# Usually this should be set to the same directory like in the webapp.conf! +# Default is "bluemap/web" +webroot: "bluemap/web" + +# The port that the webserver listens to. +# Default is 8100 +port: 8100 + +# Config-section for webserver-activity logging +log: { + # The file where all the webserver-activity will be logged to. + # Comment out to disable the logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "bluemap/logs/webserver.log" + # file: "bluemap/logs/webserver_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false + + # The format of the webserver-acivity logs. + # The syntax is the java String formatting, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Possible Arguments: + # 1 - the source address (ignoring any xff headers) + # 2 - the source address (using the (leftmost) xff header if provided) + # 3 - the http-method of the request + # 4 - the full request-address + # 5 - the protocol version of the request + # 6 - the status-code of the response + # 7 - the status-message of the response + # Default is "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" + format: "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" +} diff --git a/fabric/data/bluemap/web/maps/.keep b/fabric/data/bluemap/web/maps/.keep new file mode 100755 index 0000000..e69de29 diff --git a/paper/data/bluemap/web/maps/.keep b/paper/data/bluemap/web/maps/.keep new file mode 100755 index 0000000..e69de29 diff --git a/paper/data/bukkit.yml b/paper/data/bukkit.yml index 7693721..8df9c63 100755 --- a/paper/data/bukkit.yml +++ b/paper/data/bukkit.yml @@ -30,3 +30,6 @@ ticks-per: ambient-spawns: 1 autosave: 6000 aliases: now-in-commands.yml +worlds: + redstoner_creative: + generator: PlotSquared diff --git a/paper/plugins/BlueMap/core.conf b/paper/plugins/BlueMap/core.conf new file mode 100755 index 0000000..5cbe2dc --- /dev/null +++ b/paper/plugins/BlueMap/core.conf @@ -0,0 +1,48 @@ +## ## +## BlueMap ## +## Core-Config ## +## ## + +# By changing the setting (accept-download) below to TRUE you are indicating that you have accepted mojang's EULA (https://account.mojang.com/documents/minecraft_eula), +# you confirm that you own a license to Minecraft (Java Edition) +# and you agree that BlueMap will download and use a minecraft-client file (depending on the minecraft-version) from mojangs servers (https://piston-meta.mojang.com/) for you. +# This file contains resources that belong to mojang and you must not redistribute it or do anything else that is not compliant with mojang's EULA. +# BlueMap uses resources in this file to generate the 3D-Models used for the map and texture them. (BlueMap will not work without those resources.) +# 2025-04-23T11:57:56 +accept-download: true + +# The folder where bluemap saves data-files it needs during runtime or to save e.g. the render-progress to resume it later. +# Default is "bluemap" +data: "bluemap" + +# This changes the amount of threads that BlueMap will use to render the maps. +# A higher value can improve render-speed but could impact performance on the host machine. +# This should be always below or equal to the number of available processor-cores. +# Zero or a negative value means the amount of available processor-cores subtracted by the value. +# (So a value of -2 with 6 cores results in 4 render-processes) +# Default is 1 +render-thread-count: 1 + +# Controls whether BlueMap should try to find and load mod-resources and datapacks from the server/world-directories. +# Default is true +scan-for-mod-resources: true + +# If this is true, BlueMap might send really basic metrics reports containing only the implementation-type and the version that is being used to https://metrics.bluecolored.de/bluemap/ +# This allows me to track the basic usage of BlueMap and helps me stay motivated to further develop this tool! Please leave it on :) +# An example report looks like this: {"implementation":"bukkit","version":"5.7","mcVersion":"?"} +# Default is true +metrics: false + +# Config-section for debug-logging +log: { + # The file where the debug-log will be written to. + # Comment out to disable debug-logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "bluemap/logs/debug.log" + # file: "bluemap/logs/debug_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false +} diff --git a/paper/plugins/BlueMap/maps/redstoner_bigplots.conf b/paper/plugins/BlueMap/maps/redstoner_bigplots.conf new file mode 100755 index 0000000..3776996 --- /dev/null +++ b/paper/plugins/BlueMap/maps/redstoner_bigplots.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: "redstoner_bigplots" + +# 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:overworld" + +# 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: "Redstoner | Big Plots" + +# 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: 500 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/redstoner_creative.conf b/paper/plugins/BlueMap/maps/redstoner_creative.conf new file mode 100755 index 0000000..3d2c22f --- /dev/null +++ b/paper/plugins/BlueMap/maps/redstoner_creative.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: "redstoner_creative" + +# 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:overworld" + +# 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: "Redstoner | Creative" + +# 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: 400 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/redstoner_trusted.conf b/paper/plugins/BlueMap/maps/redstoner_trusted.conf new file mode 100755 index 0000000..44773bc --- /dev/null +++ b/paper/plugins/BlueMap/maps/redstoner_trusted.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: "redstoner_trusted" + +# 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:overworld" + +# 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: "Redstoner | Trusted" + +# 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: 600 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/survival_1.conf b/paper/plugins/BlueMap/maps/survival_1.conf new file mode 100755 index 0000000..2646853 --- /dev/null +++ b/paper/plugins/BlueMap/maps/survival_1.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: "survival" + +# 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:overworld" + +# 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: "Survival 1 | Overworld" + +# 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: 100 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# 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.1 + +# 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: 55 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/survival_1_nether.conf b/paper/plugins/BlueMap/maps/survival_1_nether.conf new file mode 100755 index 0000000..2afb835 --- /dev/null +++ b/paper/plugins/BlueMap/maps/survival_1_nether.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: "survival_nether" + +# 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:overworld" + +# 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: "Survival 1 | Nether" + +# 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: "#290000" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#150000" + +# 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: 90 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/survival_1_the_end.conf b/paper/plugins/BlueMap/maps/survival_1_the_end.conf new file mode 100755 index 0000000..43c47b2 --- /dev/null +++ b/paper/plugins/BlueMap/maps/survival_1_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: "survival_the_end" + +# 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:overworld" + +# 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: "Survival 1 | 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: 300 + +# 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 + +} diff --git a/paper/plugins/BlueMap/maps/synergy_plots_1.conf b/paper/plugins/BlueMap/maps/synergy_plots_1.conf new file mode 100755 index 0000000..ed04050 --- /dev/null +++ b/paper/plugins/BlueMap/maps/synergy_plots_1.conf @@ -0,0 +1,147 @@ +## ## +## 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: "synergy_plots_1" + +# 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:overworld" + +# 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: "Synergy | Plots 1" + +# 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: 700 + +# 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: "#7dabff" + +# The color of the void as a hex-color +# You can change this at any time. +# Default is "#000000" +void-color: "#000000" + +# Defines the initial sky-light-strength the map will be set to when it is opened. +# 0 is no sky-light, 1 is fully lighted. +# You can change this at any time. +# Default is 1 +sky-light: 1 + +# 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.1 + +# 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: 55 + +# 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 perspective view will be enabled for this map. +# Changing this to true requires a re-render of the map, only if the hires-layer is enabled and free-flight view is disabled. +# Default is true +enable-perspective-view: true + +# Whether the flat (isometric, top-down) view will be enabled for this map. +# Having only flat-view enabled while disabling free-flight and perspective will speed up the render and reduce the maps storage-size. +# Default is true +enable-flat-view: true + +# Whether the free-flight view will be enabled for this map. +# Changing this to true requires a re-render of the map, only if the hires-layer is enabled and perspective view is disabled. +# Default is true +enable-free-flight-view: true + +# Whether the hires-layer will be enabled. +# 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 +enable-hires: 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 + +} diff --git a/paper/plugins/BlueMap/plugin.conf b/paper/plugins/BlueMap/plugin.conf new file mode 100755 index 0000000..0fc5b38 --- /dev/null +++ b/paper/plugins/BlueMap/plugin.conf @@ -0,0 +1,72 @@ +## ## +## BlueMap ## +## Plugin-Config ## +## ## + +# If the server should send player-positions to the webapp. +# This only works if the integrated webserver is enabled. +# Default is true +live-player-markers: true + +# A list of gamemodes that will prevent a player from appearing on the map. +# Possible values are: survival, creative, spectator, adventure +hidden-game-modes: [ + "spectator" +] + +# If this is true, players that are vanished (by a plugin) will be hidden on the map. +# (This only works with Spigot and Sponge based vanish-plugins) +# Default is true +hide-vanished: true + +# If this is true, players that have an invisibility (potion-)effect will be hidden on the map. +# Default is true +hide-invisible: true + +# If this is true, players that are sneaking will be hidden on the map. +# Default is false +hide-sneaking: false + +# Hides the player if they are in a sky or block-light level below the given number. +# BOTH values have to be below the threshold for the player to be hidden! +# E.g. if you set both to 1, then the player will be hidden on the map if they are in absolute darkness +# Or, if you want players only be visible on the surface you set the sky-threshold to something between 1 and 15 +# and the block-threshold to 16 +# Default is 0 (don't hide the player) +hide-below-sky-light: 0 +hide-below-block-light: 0 + +# If this is true, players that are on a different world than the viewed map will not appear on the player-list. +# Default is false +hide-different-world: false + +# The interval in seconds that the markers will be written to the map-storage. +# This is useful if you can't create a live-connection between the server and the webapp +# and the markers can only be updated via the map-storage. +# 0 or lower means that the markers will never be written to the map-storage. +# Default is 0 +write-markers-interval: 10 + +# The interval in seconds that the players will be written to the map-storage. +# This is useful if you can't create a live-connection between the server and the webapp +# and the players can only be updated via the map-storage. +# 0 or lower means that the players will never be written to the map-storage. +# Default is 0 +write-players-interval: 3 + +# Download the skin from mojang-servers when a player joins your server, so it can be used for the player-markers. +# Default is true +skin-download: true + +# The amount of players that is needed to pause BlueMap's render-threads. +# -> If this amount of players or more is online, bluemap will stop rendering map-updates until enough players +# have logged off again +# Setting this to 0 or -1 will disable this feature -> bluemap will not pause rendering +# Default is -1 +player-render-limit: -1 + +# The interval in minutes in which a full map-update will be triggered. +# This is ADDITIONALLY to the normal map-update process (in case that fails to detect any file-changes). +# ! This DOESN'T re-render the entire map each time, it only checks if there are some changes that have not been rendered yet! +# Default is 1440 (24 hours) +full-update-interval: 1440 diff --git a/paper/plugins/BlueMap/storages/file.conf b/paper/plugins/BlueMap/storages/file.conf new file mode 100755 index 0000000..1a54413 --- /dev/null +++ b/paper/plugins/BlueMap/storages/file.conf @@ -0,0 +1,22 @@ +## ## +## BlueMap ## +## Storage-Config ## +## ## + +# The storage-type of this storage. +# Depending on this setting, different config-entries are allowed/expected in this config file. +# Don't change this value! (If you want a different storage-type, check out the other example-configs) +storage-type: file + +# The path to the folder on your file-system where bluemap will save the rendered map +# The default is: "bluemap/web/maps" +root: "bluemap/web/maps" + +# The compression-type that bluemap will use to compress generated map-data. +# Available compression-types are: +# - gzip +# - zstd +# - deflate +# - none +# The default is: gzip +compression: gzip diff --git a/paper/plugins/BlueMap/webapp.conf b/paper/plugins/BlueMap/webapp.conf new file mode 100755 index 0000000..c47e194 --- /dev/null +++ b/paper/plugins/BlueMap/webapp.conf @@ -0,0 +1,75 @@ +## ## +## BlueMap ## +## Webapp-Config ## +## ## + +# With this setting you can disable the creation and updating of all web-app related files +# Default is true +enabled: false + +# The webroot where the web-application files will be created. +# Usually this should be set to the same directory like in the webserver.conf! +# Default is "bluemap/web" +webroot: "bluemap/web" + +# Whether the settings.json of the webapp should be updated/synchronized with the current bluemap settings. +# If this is set to "false", bluemap will only add maps to the settings.json but never remove unknown ones or update other settings. +# Disabling this is for example useful if you are running multiple bluemap instances on the same webroot and don't want them to overwrite each others maps. +# Default is true +update-settings-file: true + +# If the web-application should use cookies to save the configurations of a user. +# Default is true +use-cookies: true + +# If the webapp will default to flat-view instead of perspective-view. +# Default is false +default-to-flat-view: true + +# The default map and camera-location where a user will start after opening the webapp. +# This is in form of the url-anchor: Open your map in a browser and look at the url, everything after the '#' is the value for this setting. +# Default is "no anchor" -> The camera will start with the topmost map and at that map's starting point. +#start-location: "world:0:16:-32:390:0.1:0.19:0:0:perspective" + +# The minimum (closest) and maximum (furthest) distance (in blocks) that the camera can be from the ground +min-zoom-distance: 1 +max-zoom-distance: 100000 + +# The default value of the resolution (settings-menu) +# Possible values are: 0.5, 1, 2 +# Default is 1 +resolution-default: 1 + +# The min, max and default values of the hires render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:500 default:100 and min:0 +hires-slider-max: 2000 +hires-slider-default: 500 +hires-slider-min: 100 + +# The min, max and default values of the lowres render-distance slider (settings-menu) +# The values are in blocks. +# Default is max:7000 default:2000 and min:500 +lowres-slider-max: 7000 +lowres-slider-default: 2000 +lowres-slider-min: 500 + +# Here you can specify an alternative base url from where all map data is loaded. +# Default is "maps" +#map-data-root: "https://cdn.my-domain.com/mapdata" + +# Here you can specify an alternative base url from where all live data is loaded. +# Default is "maps" +#live-data-root: "https://cdn.my-domain.com/livedata" + +# Here you can add URLs to custom scripts (js) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +scripts: [ + #"js/my-custom-script.js" +] + +# Here you can add URLs to custom styles (css) so they will be loaded by the webapp +# You can place them somewhere in bluemap's webroot and add the (relative) link here +styles: [ + #"css/my-custom-style.css" +] diff --git a/paper/plugins/BlueMap/webserver.conf b/paper/plugins/BlueMap/webserver.conf new file mode 100755 index 0000000..1c05ff4 --- /dev/null +++ b/paper/plugins/BlueMap/webserver.conf @@ -0,0 +1,45 @@ +## ## +## BlueMap ## +## Webserver-Config ## +## ## + +# With this setting you can disable the integrated web-server. +# This is useful if you want to only render the map-data for later use, or if you setup your own webserver. +# Default is enabled +enabled: false + +# The webroot that the server will host to the web. +# Usually this should be set to the same directory like in the webapp.conf! +# Default is "bluemap/web" +webroot: "bluemap/web" + +# The port that the webserver listens to. +# Default is 8100 +port: 8100 + +# Config-section for webserver-activity logging +log: { + # The file where all the webserver-activity will be logged to. + # Comment out to disable the logging completely. + # Java String formatting syntax can be used to add time, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Default is no logging + # file: "bluemap/logs/webserver.log" + #file: "bluemap/logs/webserver_%1$tF_%1$tT.log" + + # Whether the logger should append to an existing file, or overwrite it + # Default is false + append: false + + # The format of the webserver-acivity logs. + # The syntax is the java String formatting, see: https://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html + # Possible Arguments: + # 1 - the source address (ignoring any xff headers) + # 2 - the source address (using the (leftmost) xff header if provided) + # 3 - the http-method of the request + # 4 - the full request-address + # 5 - the protocol version of the request + # 6 - the status-code of the response + # 7 - the status-message of the response + # Default is "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" + format: "%1$s \"%3$s %4$s %5$s\" %6$s %7$s" +}