From 52ad84445e17eaf6661f084883416106c7dde705 Mon Sep 17 00:00:00 2001 From: ME1312 Date: Sun, 14 Mar 2021 15:11:13 -0400 Subject: [PATCH] Updated Commands and Permissions (markdown) --- Commands-and-Permissions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Commands-and-Permissions.md b/Commands-and-Permissions.md index 9b7997d..67a1f86 100644 --- a/Commands-and-Permissions.md +++ b/Commands-and-Permissions.md @@ -157,7 +157,7 @@ To return to the BungeeCord console from sudo, type `exit`.

## /sub teleport **Aliases:** `tp`, `teleport`
**Exclusive To:** `SubServers.Client`
-**Permission:** `subservers.server..teleport`, `subservers.server..teleport-others`
+**Permission:** `subservers.teleport`, `subservers.teleport-others`
**Usage:** `/sub teleport [Player] `
**Examples:**
    `/sub teleport Server1`
@@ -168,7 +168,7 @@ Server-side teleportation command; teleports a player on this server to another This is different from proxy-side teleportation commands, like `/server` and `/send`, because the execution is handled on the side of the server. Additionally, the command is limited to only selecting players that are on same the server it is being ran on. Because of these limitations, it is hidden from the help menu.
-You can grant players `subservers.request` instead of `subservers.command` if they require access to this command to keep them from accessing other SubServers commands, such as `/sub version`.
+Unlike the other commands in this group, granting `subservers.command` is not required. This is because, despite not being used directly by players, you may find a situation where they'd need to be able to pass the permission check for this command.
### Usage in Command Blocks Aside from usage in other server-side plugins, Command Blocks are pretty much the de facto reason for this command's existence. Among other creative uses, you could do things like creating portals by using this command.