1.1.0
Compatibility
Changes
π§ͺ ImprovedHoppers v1.1.0 β The Bottled Experience & Localization Update
A feature-rich update focused on XP storage & bottling, a localization overhaul, and lots of stability and integration improvements.
β¨ Highlights
-
Experience Storage & Bottling
- Store hopper-generated XP and bottle it directly from the menu.
- Supports partial withdrawals, per-XP bottle queues, and localized metadata/lore.
- PRs: #924, #925, #927, #928, #929, #930, #931, #932, #933
-
Localization Overhaul
- New
messages.ymland MessageService powering all menus, prompts, and command feedback. - Covers settings, filters, links, network views, stats, admin/trusted menus, holograms, and more.
- PRs: #820β#852 (selected)
- New
-
Compatibility & Integrations
- Guarded hologram hook when DecentHolograms isnβt present. (#806)
- Runtime particle adapter and legacy-safe item metadata helpers. (#812, #809)
- Graceful NamespacedKey handling on older servers. (#813, #814)
- 1.21 shaped recipe category support. (#815)
- Relaxed BentoBox startup gating. (#818)
-
Performance & Stability
- Coalesced async hopper node saves and prevented tasks from loading distant chunks. (#926, #934)
- Reloads config before applying power settings. (#819)
- Shared data directory migration for cleaner upgrades. (#807)
-
UI/UX Tweaks
- New main menu entrypoint for hoppers. (#919)
- Back button in filter browser; Search moved above Simulate. (#923, #922)
- Trimmed settings button from filter list where redundant. (#920)
- Compatibility icons (e.g., Experience Bottle, End Crystal, Redstone Torch). (#921, #903, #904)
π§ Additional Improvements & Fixes (selected)
- Refactors and helpers for sound/particle lookups across legacy runtimes. (#901, #911β#918)
- Safer fallbacks for GUIs, icons, dyes, panes, and comparator/stats visuals on older servers. (#878β#882, #879, #880)
- Misc. legacy guards (API availability, version detection) and cleanups. (#870, #877, #887, #883)
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:TqOuB4ae:RqqqHXkd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TqOuB4ae:RqqqHXkd"
}

