Skip to content

Commit e0ddd7d

Browse files
TBlueFTBlueF
committed
Update commands and permissions for v5.6
1 parent f761ea0 commit e0ddd7d

File tree

1 file changed

+24
-25
lines changed

1 file changed

+24
-25
lines changed

‎wiki/getting-started/Commands.md‎

Lines changed: 24 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -21,28 +21,27 @@ Here is a table with all commands and their permissions that you can use if you
2121
> Arguments that look like `[this]` are **optional**!
2222
{: .info }
2323

24-
| command | permission | description |
25-
|------------------------------------------------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
26-
| `/bluemap` | bluemap.status | displays BlueMaps render status |
27-
| `/bluemap version` | bluemap.version | displays BlueMaps version and some more useful system-information |
28-
| `/bluemap help` | bluemap.help | displays a list of all possible BlueMap-commands |
29-
| `/bluemap reload [light]` | bluemap.reload | reloads all resources, configuration-files and the web-server *(`light` => re-loads everything other than resources (resourcepacks/mods) which is faster)* |
30-
| `/bluemap maps` | bluemap.status | shows all maps loaded by BlueMap |
31-
| `/bluemap worlds` | bluemap.status | shows all worlds loaded by BlueMap |
32-
| `/bluemap storages` | bluemap.status | shows all storages configured/available |
33-
| `/bluemap storages <storage>` | bluemap.status | shows a list of all maps that are on this storage |
34-
| `/bluemap storages <storage> delete <map>` | bluemap.delete | deletes the (unloaded) map from that storage *(for deleting loaded maps, use the `/bluemap purge <map>` command)* |
35-
| `/bluemap stop` | bluemap.stop | pauses all rendering *(persists over a server-restart)* |
36-
| `/bluemap start` | bluemap.start | resumes all paused rendering *(persists over a server-restart)* |
37-
| `/bluemap freeze <map-id>` | bluemap.freeze | pauses all updates on a specific map *(persists over a server-restart)* |
38-
| `/bluemap unfreeze <map-id>` | bluemap.freeze | resumes all updates on a previously frozen map *(persists over a server-restart)* |
39-
| `/bluemap purge <map-id>` | bluemap.purge | purges (deletes) all data of a rendered map *(the map will be re-rendered afterwards, as long as it is not frozen)* |
40-
| `/bluemap update [world / map] [x z] [block-radius]` | bluemap.update | updates the whole world or optionally a defined radius around the player *(only renders changed chunks)*<br><br>BlueMap detects and updates your map automatically, usually you should not need this command :) |
41-
| `/bluemap fix-edges [world / map] [x z] [block-radius]` | bluemap.update.force | renders **(even if nothing has changed)** the edges of a map again *(usually not needed, but can help if there is an issue after changing the map-limits)* |
42-
| `/bluemap force-update [world / map] [x z] [block-radius]` | bluemap.update.force | renders **(even if nothing has changed)** the whole world or optionally a defined radius around the player<br><br>BlueMap has a really reliable way of detecting changes in your world and only rendering those. You should only need this command for testing! |
43-
| `/bluemap cancel [task-ref]` | bluemap.cancel | cancels the last (or the referenced) render-task in the queue<br><br>You usually should not need this command. Consider using `/bluemap freeze` instead :) |
44-
| `/bluemap debug block [world x y z]` | bluemap.debug | prints some debug info about the blocks at the players (or defined) position |
45-
| `/bluemap debug map [map x z]` | bluemap.debug | prints some debug info about the map-tile at the players (or defined) position |
46-
| `/bluemap debug flush <world>` | bluemap.debug | saves the world and flushes scheduled tile-updates |
47-
| `/bluemap debug cache` | bluemap.debug | clears bluemap's world-caches |
48-
| `/bluemap debug dump` | bluemap.debug | creates a file `./bluemap/dump.json` containing lots of info about bluemaps current state |
24+
| command | permission | description |
25+
|-------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
26+
| `/bluemap` | bluemap.status | displays BlueMaps render status |
27+
| `/bluemap version` | bluemap.version | displays BlueMaps version and some more useful system-information |
28+
| `/bluemap help` | bluemap.help | displays links to this wiki and the support-discord |
29+
| `/bluemap reload [light]` | bluemap.reload, bluemap.reload.light | reloads all resources, configuration-files and the web-server *(`light` => re-loads everything other than resources (resourcepacks/mods) which is faster)* |
30+
| `/bluemap maps` | bluemap.maps | shows all maps loaded by BlueMap |
31+
| `/bluemap storages` | bluemap.storages | shows all storages configured/available |
32+
| `/bluemap storages <storage>` | bluemap.storages | shows a list of all maps that are on this storage |
33+
| `/bluemap storages <storage> delete <map>` | bluemap.storages.delete | deletes the (unloaded) map from that storage *(for deleting loaded maps, use the `/bluemap purge <map>` command)* |
34+
| `/bluemap stop` | bluemap.stop | pauses all rendering *(persists over a server-restart)* |
35+
| `/bluemap start` | bluemap.start | resumes all paused rendering *(persists over a server-restart)* |
36+
| `/bluemap freeze <map-id>` | bluemap.freeze | pauses all updates on a specific map *(persists over a server-restart)* |
37+
| `/bluemap unfreeze <map-id>` | bluemap.unfreeze | resumes all updates on a previously frozen map *(persists over a server-restart)* |
38+
| `/bluemap purge <map-id>` | bluemap.purge | purges (deletes) all data of a rendered map *(the map will be re-rendered afterwards, as long as it is not frozen)* |
39+
| `/bluemap update [map-id] [x z] [block-radius]` | bluemap.update | updates the whole world or optionally a defined radius around the player *(only renders changed chunks)*<br><br>BlueMap detects and updates your map automatically, usually you should not need this command :) |
40+
| `/bluemap fix-edges [map-id] [x z] [block-radius]` | bluemap.update | renders **(even if nothing has changed)** the edges of a map again *(usually not needed, but can help if there is an issue after changing the map-limits)* |
41+
| `/bluemap force-update [map-id] [x z] [block-radius]` | bluemap.update | renders **(even if nothing has changed)** the whole world or optionally a defined radius around the player<br><br>BlueMap has a really reliable way of detecting changes in your world and only rendering those. You should only need this command for testing! |
42+
| `/bluemap tasks` | bluemap.tasks | shows the current task-queue that is being processed by the render-threads |
43+
| `/bluemap tasks cancel <task-ref>` | bluemap.tasks.cancel | cancels the referenced render-task in the queue<br><br>You usually should not need this command. Consider using `/bluemap freeze` instead :) |
44+
| `/bluemap troubleshoot [map] [x z]` | bluemap.troubleshoot | tries to find potential issues with the map or world at the players (or defined) position and gives suggestions on how to fix them |
45+
| `/bluemap debug world [map] [x y z]` | bluemap.debug.world | prints some debug info about the world at the players (or defined) position |
46+
| `/bluemap debug map [map] [x z]` | bluemap.debug.map | prints some debug info about the map-tile at the players (or defined) position |
47+
| `/bluemap debug dump` | bluemap.debug.dump | creates a file `./bluemap/dump.json` containing lots of info about bluemaps current state |

0 commit comments

Comments
 (0)