Tags
Creators
Details
All versions
3.4.3-1.21.1+neoforge
Beta
3.4.3-1.21.1+neoforge8 months ago 86.3K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
The Slap My Forehead Patch
⚠️ NOTE: If you are playing on 1.21.1, you do not technically need this, unless you're seeing dozens of hamsters on your shoulder. Go have a snack.
Fixed
1.20.1
- Server Crash: "Unknown Message Type" (The 'I misunderstood how old Architectury works' bug)
- The Issue: On dedicated 1.20.1 servers, the game would crash immediately upon trying to sync hamster data.
- The Cause: I (sort of) copy-pasted the shiny, modern Architectury networking code from 1.21.1 into the 1.20.1 backport. Turns out, the older Architectury API requires you to introduce packets to the server politely before sending them. The server received the hamster data, said "I don't know her," and panicked.
- The Fix: Refactored the network registration to actually work on 1.20.1.
- Also, I have left several aggressively capitalized comments in the source code warning my future self that 1.20.1 Architectury networking is different. So hopefully this will never happen again!
1.21.1 and 1.20.1
- "Mutant Hamster Pile" Cleanup
- The Issue: Players affected by the previous Invalid Player Data bug might have ended up with "ghost" hamster data, resulting in dozens of duplicate hamsters appearing on their shoulder.
- The Fix: Spamming your dismount button should fix the issue, but not everyone reads changelogs so I added an auto-sanitizer that runs on login. It will instantly detect and delete any ghost/duplicate hamster entries, returning your character to normal without you needing to do anything.
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:MRf39DcQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LmrhZdK2:MRf39DcQ"
}







