From aae417a709817863b4ac19800cae4b26d6902f9a Mon Sep 17 00:00:00 2001 From: Kristian Knarvik Date: Sat, 22 Jan 2022 20:42:56 +0100 Subject: [PATCH] Update 'Create command' --- Create-command.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Create-command.md b/Create-command.md index 12290aa..dc17948 100644 --- a/Create-command.md +++ b/Create-command.md @@ -11,7 +11,7 @@ Fields: As the permission field has some special behavior, this section goes more in-depth. -The simplest way of using the permision field is to just specify one permission such as `essentials.gamemode.creative`, but you can put any number of comma-separated permissions in the field such as: `essentials.gamemode.creatice,essentials.gamemode.survival,essentials.gamemode.spectator`. +The simplest way of using the permission field is to just specify one permission such as `essentials.gamemode.creative`, but you can put any number of comma-separated permissions in the field such as: `essentials.gamemode.creatice,essentials.gamemode.survival,essentials.gamemode.spectator`. This plugin also supports per-world permissions. By default, permissions are set for all worlds. You can change a setting in the config to only grant the permission for the world the clicked sign belongs to. In addition to this, you can override the default behavior by specifying the world before each permission node. *Any* specifies that a permission should be given regardless of world, and *World_Name* specifies that a permission should only be set for the given world. *World_Name* can also be specified as a different world that the one the permission sign belongs to.