Tags
Creators
Details
All versions
0.12.0-alpha+26.1
Alpha
BtrBz v0.12.0-alpha for 26.1.xlast week 2,077
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
[0.12.0-alpha] - 2026-09-16
Breaking
- Install Hypixel Mod API 1.0.2 or newer before updating BtrBz
- To use BtrBz outside SkyBlock, enable "Always Active" in General > Activation
Added
- Added a price-alert screen for creating, editing, and removing alerts with
/btrbz alert - Added item search for price alerts
- Added threshold expressions with Buy Price and Sell Price references
- Added a Reached tab with the latest 10 triggered alerts and options to reopen their Bazaar pages or remove entries
- Added
/btrbz enableand/btrbz disablecommands to toggle BtrBz - Added an "Always Active" setting to bypass SkyBlock detection, disabled by default
Changed
- Renamed price-alert conditions to Buy Price and Sell Price
- By default, BtrBz now waits for Hypixel to confirm that you are in SkyBlock before activating features and fetching Bazaar prices
- Disabling BtrBz, disconnecting, or leaving SkyBlock clears session state
Fixed
- Fixed Bazaar HUD widgets hiding when hitboxes or chunk borders are enabled. The full F3 debug overlay still hides them
- Fixed saved bookmarks losing their bookmark markers after restarting Minecraft
Removed
- Removed the
/btrbz alert add,/btrbz alert list, and/btrbz alert removecommands. Use/btrbz alertinstead
Internal
- Reorganized feature initialization and widget configuration
- Reworked release automation and Discord announcements
Optional dependencies
Any compatible version
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:IzWPcaNg:niSMEKWM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IzWPcaNg:niSMEKWM"
}

