Links
Tags
Creators
Details
Licensed AGPL-3.0-or-later
Published 2 years ago
Updated 31 minutes ago
All versions
v1.0.0
Release
1.0.02 weeks ago 45
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
- Favorita now runs on OneConfig and needs it installed. All of its settings are in the OneConfig menu.
- The favorite slot key is a OneConfig keybind. It still shows up in Minecraft's Controls menu, and it can be a mouse button or a key combination.
- Each singleplayer world now has its own locked slots. Before, every world shared one set. A world you play for the first time after updating starts with that old shared set.
- Locked slots are now kept safe from number key and offhand swaps, and from double-clicks that gather matching items. The double-click protection can be turned off.
- Shift-clicking and dragging stacks skip locked slots, so items go to the next free slot instead.
- You can stop the favorite slot key from unlocking your held hotbar slot while no inventory is open, so slots only unlock from an inventory.
- You can pick the lock's tint color, hide the padlock, and choose whether hotbar locks always show, show for a few seconds when used, or never show.
- Sounds can be turned off, and the locked slot warning can be a notification, a chat message or nothing.
- Added
/favoritato open the settings and/favorita clearto unlock every slot in the current world or server. - Locked slots move from
Deftu/favorita.jsontoconfig/Favorita/favorites.jsonon first launch. - Supports Minecraft 1.21 to 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.10, 1.21.11 and 26.1 to 26.3 on Fabric, and 1.8.9 on Ornithe. Forge, NeoForge and Minecraft 1.12.2 to 1.20.6 are no longer supported.
- Favorita is now licensed under AGPL-3.0-or-later.
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:XLpX6IPW:jNYmzrWd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XLpX6IPW:jNYmzrWd"
}

