Updated Commands and Permissions (markdown)

ME1312 2022-03-17 01:31:36 -04:00
parent e5a24ce796
commit 1314904a5e

@ -4,6 +4,7 @@ This page defines all the commands provided by SubServers apps across your netwo
> [BungeeCord Commands](https://github.com/ME1312/SubServers-2/wiki/Commands-and-Permissions#BungeeCord-Commands)<br>
> [SubServers Commands](https://github.com/ME1312/SubServers-2/wiki/Commands-and-Permissions#SubServers-Commands)<br>
> [Selecting Multiple Servers](https://github.com/ME1312/SubServers-2/wiki/Commands-and-Permissions#Selecting-Multiple-Servers)<br>
> [Using Server Signs](https://github.com/ME1312/SubServers-2/wiki/Commands-and-Permissions#Using-Server-Signs)<br>
### BungeeCord Commands
@ -303,4 +304,19 @@ Lastly, you can select subservers using their hosts. To begin selecting using ho
```
/sub cmd ::. say Hello World!
```
<br>
# Using Server Signs
**Exclusive To:** `SubServers.Client.Bukkit`<br>
**Permission:** `subservers.teleport`<br><br>
Server signs are magic blocks that allow players to start and/or join subservers of your choosing with a simple click. Even so, only the teleport permission is required for players to interact with the signs.<br><br>
## Managing Server Signs
**Permission:** `subservers.signs`<br><br>
An admin with the above permission can turn a regular old sign into a server sign by writing `[SubServers]` on the first line, and the name of a subserver on the second. In an instant, all four lines will be replaced by that which was globally configured in `lang.yml`, with [native placeholder support](https://github.com/ME1312/SubServers-2/wiki/Integrations#placeholderapi).
At this point you should think about securing the area if you haven't already. Signs are fragile things, so you should protect them with plugins that have been painstakingly built to serve that purpose. In other words, SubServers intentionally provides only the bare minimum in terms of block protection. <ins>Please do not file a bug report because someone broke your sign.</ins>
<br><br><br>