Skip to content

Commit 04e9146

Browse files
committed
Add missing page content.
1 parent 8ed1ce5 commit 04e9146

File tree

2 files changed

+17
-0
lines changed

2 files changed

+17
-0
lines changed
7.33 KB
Loading

Writerside/topics/ES-Disabling-Commands.md

+17
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,23 @@
55
This does not remove the commands from /help or /es help at this time, it also does not prevent the server from recognising they exist.
66
</warning>
77

8+
To disable commands in Essence, you can add them to a list in the configuration file.
9+
10+
1. Open Essence's config.yml
11+
2. Scroll to disabled-commands.
12+
3. Add any commands you'd like to disable. Most codes are what you'd expect, but since some commands have aliases we've included the full list below.
13+
4. Restart your server
14+
15+
## Limitations and Drawbacks
16+
If you're looking to disable a command because you prefer another plugin's (or vanilla's) alternative, this system likely won't work for you. Spigot requires Essence to register commands in the plugin.yml file, because of this the server still expects the command to work. Since Essence has disabled the command it will refuse to process it, causing the default error message to appear in chat. Here's an example with the /tp command disabled:
17+
18+
![es-disabling-commands.png](es-disabling-commands.png)
19+
20+
If you want to use a vanilla command, you can append minecraft: to it. For example: /minecraft:teleport
21+
22+
## Alternatives
23+
Permissions! Essence has a robust permissions system - simply disallow players from using the commands. This gives them an error message instead of it appearing as though the command doesn't work at all.
24+
825
<seealso>
926
<category ref="es-commands">
1027
<a href="ES-Commands.md">Commands</a>

0 commit comments

Comments
 (0)