Tags
Creators
Details
1.5.0
Compatibility
Changes
Host and control your worlds with ease
The new host panel is front and centre. You get new controls and a clearer layout of your members list, general world settings, and game rules.
- The host panel opens to the new members tab. It's clutter-free and makes it easy to invite and manage members.
- The new game rules tab sorts all game rules into dedicated sections that can open and close, making it easy to navigate.
- The new start/stop hosting button allows you to stop hosting while staying in your world.
- You can now open the world folder from the host panel.
World-based resource packs
Resource packs can now be added directly to a world and are automatically shared with everyone who joins. No more equipping resource packs to yourself to share them.
Minecraft 26.3 support
We’ve also updated Essential to support Minecraft 26.3 for Fabric.
Retiring unpopular Minecraft versions
Changes we make to Essential have to be built and tested on all Minecraft version that we support. This is slowing us down while we are trying to make meaningful updates to Essential. Because of this, we’re retiring support for the least-used and most unpopular versions of Minecraft. The vast majority of people will not be affected by this change. Learn more
Bug fixes
- Fixed the vanilla friends menu opening via the hotkey when an Essential modal is opened
- Fixed an issue where joining a game through the profile of a world member would not connect you to the host
- Fixed performance issues in the Screenshot Browser with large amounts of screenshots
- Fixed an issue where friends' heads were not rendering correctly on the server list in 1.21.6+
Mod compatibility
- Fixed the Essential button style not persisting correctly after changing its label in FancyMenu
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:k2ZPuTBm:LdqUMhXW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k2ZPuTBm:LdqUMhXW"
}

