mirror of
https://github.com/ME1312/SubServers-2.git
synced 2024-11-25 03:35:26 +01:00
Updated Commands and Permissions (markdown)
parent
172e47fc56
commit
a94bd5a4ec
@ -315,7 +315,7 @@ Server signs are magic blocks that allow players to start and/or join subservers
|
||||
## 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`. You can also do this for server groupings by prefixing the name with `:` or `::` as described in the last section.
|
||||
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`. You can also do this for server groupings by prefixing the name with `:` or `::` as described in the [last section](https://github.com/ME1312/SubServers-2/wiki/Commands-and-Permissions#selecting-multiple-servers-using-groups).
|
||||
|
||||
At this point, you should think about securing the area if you haven't already. Signs are fragile things, so you should protect them using 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>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user