Many Minecraft modpack players rely on FTB Essentials for core server commands like /home, /spawn, and /tpa. When those commands suddenly stop showing up—or never appear at all—it can quickly turn an organized server into a frustrating experience. Fortunately, in most cases, the issue is not complex. With a few targeted checks and adjustments, the majority of players can restore functionality without rebuilding their entire modpack.
TLDR: If FTB Essentials commands are not showing up, the issue is usually related to permissions, missing dependencies, incorrect installation, mod conflicts, or configuration settings. Most problems can be resolved by verifying server-side installation, adjusting permission levels, and confirming version compatibility. Simple fixes like restarting the server or checking the config file often restore command visibility. In rare cases, removing conflicting mods or reinstalling the mod solves the problem entirely.
Why FTB Essentials Commands Might Not Show
FTB Essentials works by registering server-side commands during startup. If something disrupts that process, the commands will not appear in chat suggestions or function when typed manually. Common symptoms include:
- Typing /home returns “Unknown command.”
- No auto-complete suggestions appear in chat.
- Only operators can access commands.
- Commands worked previously but stopped after an update.
Below are seven proven fixes that resolve the issue for approximately 90% of Minecraft modpack users.
1. Confirm FTB Essentials Is Installed Server-Side
One of the most common mistakes is installing FTB Essentials only on the client. Since it is a server-side utility mod, it must be present in the server’s mods folder to register commands.
What to check:
- Open the server directory.
- Navigate to the mods folder.
- Verify that the FTB Essentials .jar file is present.
If it is only installed on a local client but not on the server, commands will not exist in multiplayer. After adding the mod to the server, restart completely—not just a reload.
2. Check for Missing Dependencies
FTB Essentials often requires FTB Library or other related FTB core mods to function properly. If dependencies are missing or mismatched in version, the commands may fail to register.
Steps to verify:
- Review the modpack documentation.
- Check the server startup log for dependency errors.
- Ensure FTB Library versions match the Essentials version.
Server logs will usually display warnings such as “Missing dependency” or “Failed to load FTB Essentials.” Resolving those errors often restores commands immediately after a restart.
3. Verify Operator and Permission Settings
Sometimes the commands exist—but players simply do not have permission to use them.
FTB Essentials integrates with Minecraft’s permission levels. If a player is not an operator (OP) or lacks assigned permissions in a dedicated permissions mod, commands may not appear.
Solutions include:
- Using /op PlayerName in the server console.
- Checking permission mods such as LuckPerms.
- Reviewing the FTB Essentials config file.
If operators can access the commands but regular players cannot, the issue is almost always permission-related rather than a broken installation.
4. Inspect the FTB Essentials Config File
Many modpacks modify default settings. It is possible that certain commands have been disabled in the configuration.
The configuration file is typically located in:
server/config/ftbessentials.snbt (or similar)
Image not found in postmetaInside the config, look for entries that control features such as:
- Enable homes
- Enable teleport requests
- Command cooldown settings
If a section shows false next to a feature, changing it to true and restarting the server may restore hidden commands.
5. Ensure Version Compatibility
Modpacks frequently update, and mismatched versions are a leading cause of command failures. If Minecraft, Forge/Fabric, FTB Library, and FTB Essentials versions are not aligned, commands may silently fail.
Key compatibility checks:
- Minecraft version matches the mod version.
- Correct mod loader (Forge vs Fabric).
- All FTB mods are from the same release cycle.
After updating any mod, a complete server restart is required. A common mistake is performing a hot swap or partial reload, which does not properly re-register commands.
6. Look for Conflicting Mods
Some utility or server management mods override default command systems. When two mods attempt to register similar commands, one may suppress the other.
Experimental troubleshooting involves:
- Temporarily removing recently added mods.
- Checking logs for command registration conflicts.
- Testing with only core FTB mods installed.
If FTB Essentials commands reappear after isolating a particular mod, a conflict is likely responsible. In such cases, server owners may need to choose between overlapping utilities or adjust load order where possible.
7. Fully Restart the Server (Not Just Reload)
It may sound simple, but many players attempt to use /reload or similar commands instead of fully shutting down the server. FTB Essentials registers commands during startup, and partial reloads often fail to apply configuration changes.
Proper restart procedure:
- Stop the server completely.
- Wait until it fully shuts down.
- Start it fresh.
This refreshes command registration and resolves a surprising percentage of issues—especially after installing, updating, or editing configs.
Additional Troubleshooting Tips
If the primary fixes do not solve the issue, deeper diagnostics may help:
- Check server logs carefully for red error messages during startup.
- Delete and regenerate config files (after backing them up).
- Reinstall the mod by downloading a fresh .jar file.
- Test in a clean instance to confirm the mod functions independently.
In rare cases, corrupted files or incomplete uploads (especially when using FTP clients) may prevent commands from loading correctly.
Common Scenarios and Quick Answers
Commands work in singleplayer but not multiplayer:
The mod is likely installed only on the client.
Commands disappeared after updating:
Version mismatch or altered config settings are the most probable causes.
Only admins can use commands:
Permission configuration needs adjustment.
Across community discussions and support forums, these patterns appear repeatedly, reinforcing that most issues stem from installation and configuration—not from bugs in FTB Essentials itself.
Final Thoughts
When FTB Essentials commands are not showing up, frustration is understandable. These commands are central to managing teleportation, homes, server spawn points, and player quality-of-life features. However, the solution is usually straightforward.
By methodically checking installation location, permissions, dependencies, configuration files, and version compatibility, most server owners resolve the issue in under 30 minutes. Rather than assuming the mod is broken, a structured troubleshooting approach typically restores functionality quickly.
FAQ
Why does /home say “Unknown command” even though FTB Essentials is installed?
The mod may not be installed on the server, or dependencies like FTB Library are missing. Check the server mods folder and logs.
Do players need to be OP to use FTB Essentials commands?
Not necessarily. Permissions can be configured to allow non-operators to access certain features.
Can another mod disable FTB Essentials commands?
Yes. Command registration conflicts with other utility or management mods can override or hide commands.
Where are FTB Essentials config files located?
They are typically found inside the server’s config folder. The file name may vary slightly by version.
Will reinstalling Minecraft fix the issue?
Usually not. Since FTB Essentials is server-side, reinstalling the server mod files is more effective than reinstalling the client.
Why did commands disappear after updating my modpack?
Updates can overwrite config files, change permissions, or introduce version incompatibilities. Checking logs after updates is essential.
Is /reload enough after changing config settings?
No. A full server shutdown and restart is recommended to properly re-register commands.
