Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 4 months ago
All versions
2.2.0
Release
WynnToolZ v2.2.05 months ago 88
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Changes
⭐ New Features
- Mount Item Overlay
- Modifier Key
- Requires the selected modifier key to show stat bars in inventory screens
- Always Show In Hotbar
- New toggle to always show mount stat bars on hotbar items, even when inventory bars require a modifier key
- Show Skin Names
- Displays the mount skin name above the item while viewing a mount in the Trade Market
- Modifier Key
- Edit Overlays
- New keybind to toggle an overlay editing mode, allowing WTZ overlays to be adjusted without opening the
fuckingchat
- New keybind to toggle an overlay editing mode, allowing WTZ overlays to be adjusted without opening the
- macOS Movement Key Fix
- Fixes a macOS issue where held movement keys can stop working after an inventory or menu closes
✍️ Adjustments
- Mount Data API
- Added support for the new mount data payload format
- Mount Skin Reporting
- Updated the tooltip to better explain what it does
- Mount Stats Overlay
- Auto Update Stats
- Now also updates when the vanilla energy bar changes
- Auto Update Stats
- WTZ Website
- Fully reworked website's tooltip system
- Added better descriptions and keybind shortcut information
🐞 Bug Fixes
- Mount Stats Overlay
- Fixed overlay hitboxes from blocking interactions when the overlay is not visible
- Shopping List
- Fixed an issue where the Shopping List could reopen after being manually closed while browsing Market screens
- Auto-open now only triggers when the Trade Market is opened through an NPC interaction
Optional dependencies
Unavailable 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:Vgo1fklU:US6BfcAe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vgo1fklU:US6BfcAe"
}

