From 0b1fbe42406243a0c8875a8c7dd2c7db352b0468 Mon Sep 17 00:00:00 2001 From: ME1312 Date: Fri, 18 Mar 2022 12:08:03 -0400 Subject: [PATCH] Updated Commands and Permissions (markdown) --- Commands-and-Permissions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Commands-and-Permissions.md b/Commands-and-Permissions.md index a8b8add..decd491 100644 --- a/Commands-and-Permissions.md +++ b/Commands-and-Permissions.md @@ -315,7 +315,7 @@ Server signs are magic blocks that allow players to start and/or join servers of ## Managing Server Signs **Permission:** `subservers.signs`

-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). +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 server 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. Please do not file a bug report because someone broke your sign.