Essential Commands Setup, Config Reloading, and Command Feedback Guide
Essential Commands is a Minecraft utility mod operated entirely through its own interface and hotkeys rather than through crafting, and this guide covers its basic configuration handling plus the feedback and error messages you will encounter while using it.
Reloading the Config
The mod's configuration can be reloaded while the game is running. When you trigger a config reload, the mod confirms it with a message combining its fullprefix — shown as [Essential Commands] — and the text "Config Reloaded." If the reload instead fails, you will see a notice that an unexpected error occurred while reloading the rules file, along with a hint that the server console may contain more information. A separate reload action exists for the rules file specifically: on success it reports "Rules file reloaded," and on failure it gives the same style of unexpected-error notice pointing to the server console for details.
General Command Feedback
Many commands confirm their result with a short feedback line. Examples include opening an Ender Chest, toggling invulnerability, and setting a nickname. Flight-related feedback reports the state change and the affected player, and speed changes are reported both to the player making the change and, where another player is affected, to that player as well. Flight speed is capped, and exceeding that cap produces a message stating the limit. Teleport requests, homes, and warps each have their own confirmation lines, such as a request being sent, accepted, denied, or canceled, a home being deleted or moved, or a warp being deleted.
Errors and How to Read Them
Errors tell you why an action did not go through. Common patterns:
- A not found message means the named home or warp does not exist, or that no previous location is stored for the back command.
- A shortcut more than one message appears when your input matches several homes or several pending teleport requests; you must specify which one you mean by name.
- Name conflicts are reported directly: a home or warp cannot be set if one with that name already exists, and homes also fail when your home limit is reached. When a home name already exists you may be asked whether to overwrite it.
- Nickname errors cover insufficient permissions, a nickname longer than the maximum allowed length, and a general failure reason.
- Permission problems also appear for teleporting to a warp that requires explicit permission, and for nicknames.
- Cooldowns are reported with the remaining time in seconds.
- An unknown error message indicates the command failed for an unlisted reason.
Teleport Requests and Queued Teleports
Incoming requests are announced with instructions to accept or deny using the corresponding commands. Sending a request that duplicates an existing pending request is refused. If you try to accept with no requests pending, or with several, the mod tells you so and asks you to name the player. A request can expire, and both sides are notified. Queued teleports announce a countdown, then confirm arrival, and can be interrupted by taking damage or moving. A new teleport cancels a previously queued one. Interdimensional teleportation can be disabled, in which case the teleport fails with that reason.
RTP, Spawn, and Miscellaneous Messages
Random teleport has its own checks: it may be disabled in the current world, it requires a spawn to be set, and it can be on cooldown. It also reports how long location validation took. Other utility feedback covers daytime and nighttime changes, AFK entry being blocked in combat, hunger and health already being full, players not being on fire, items not being damaged, nearby player lists, empty location lists, and range limits. Even dying does not stop commands from being sent, and the mod has a message for that too.
Hotkeys
Actions described here are triggered through the mod's interface or the corresponding hotkey, which you assign yourself in the controls menu.