Updated Configuration (markdown)

Lukas Rieger 2020-08-26 01:54:39 +02:00
parent aae526166e
commit 9ac8302c19

@ -94,18 +94,19 @@ The integrated web-server is the easiest way to host your map to the web, so you
- The `maxConnectionCount` field limits the max number of active connections that the web-server accepts simultaneously. - The `maxConnectionCount` field limits the max number of active connections that the web-server accepts simultaneously.
## Plugin configuration: `plugin.conf` ## Plugin configuration: `plugin.conf`
This section controls how player-markers are handled. This section is about server-interaction.
It currently mainly controls how player-markers are handled.
```yml ```yml
liveUpdates { liveUpdates: true
enabled: true skinDownload: true
hiddenGameModes: [ hiddenGameModes: [
"spectator" "spectator"
] ]
hideInvisible: true hideInvisible: true
hideSneaking: false hideSneaking: false
}
``` ```
- If you don't want any live data being used, set `enabled` to `false`. This disables the full live-updates module. - If you don't want any live data being used, set `liveUpdates` to `false`. This disables the full live-updates module.
- If `skinDownload` is set to true, BlueMap will download and update the current skin of each player to make it available for the web-app.
- With `hiddenGameModes` you can control what gamemodes are visible on the map. By default everyone is visible, except players in spectator-mode. - With `hiddenGameModes` you can control what gamemodes are visible on the map. By default everyone is visible, except players in spectator-mode.
- When `hideInvisible` is `true`, players that have the invisibility effect will not be displayed on the map. - When `hideInvisible` is `true`, players that have the invisibility effect will not be displayed on the map.
- `hideSneaking` controls if a player that is sneaking should be visible on the map. - `hideSneaking` controls if a player that is sneaking should be visible on the map.