Tags
Creators
Details
3.4.2-1.20.1+fabric
Compatibility
Required content
Changes
The Tiny Patch
This patch is hamster-sized, but fixes a pretty big issue. In my zeal to make my code more defensive against Macaw's Mods on Sunday, I accidentally created a bug that locked players out of worlds if they logged out with a shoulder hamster. That is now fixed. Your worlds are safe, and you can log in again. I also squeezed in Xaero's Minimap support and a few other things while I was at it.
Added
- New Translations
- Added 6 new locals for the Spanish translation thanks to @The Retro Stitcher.
- Xaero's Minimap Compatibility
- Thanks to help from @Kazerio, added hamster icons to Xaero's Minimap!
Fixed
- Invalid Player Data / World Join Crash
- Resolved a critical issue where the game would crash or lock players out of worlds if they had a hamster on their shoulder. This was accidentally introduced in version 3.4.1 when I refactored the code to defend against the network protocol error caused by Macaw's Mods.
- I had accidentally introduced a race condition where the mod attempted to sync pet data before the player's network connection was fully established. If you had previously been locked out of any of your worlds due to this bug, you should now be able to join just fine and your hamsters will still be on your shoulder.
- Config Screen Localization
- Implemented a work-around for an issue where the "Main Settings" and "World Gen Settings" descriptions were not translatable due to a known bug with Fzzy Config.
- Fixed untranslated enum values (e.g., "Near/Medium/Far", "Sneak Key") in dropdown menus.
- Fixed untranslated conditional help text (e.g., "Only available when...").
- EMI Compatibility
- Resolved tooltip mod name duplication when EMI is installed.
Optional dependencies
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:LmrhZdK2:BbhiDYLc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LmrhZdK2:BbhiDYLc"
}

