Tags
Creators
Details
1.0.1+mc26.2
Compatibility
Changes
CrowBar v1.0.1
A bugfix release for the Minecraft 26.1.x and 26.2 Fabric builds. Clients running CrowBar 1.0.0 could crash out of the world immediately after connecting to servers that hold players in a verification phase before the login handshake finishes.
Fixed
- Fixed a crash on join (
NullPointerExceptioninCrowBarState.checkXpGain) that disconnected the client from servers running anti-bot or verification plugins.Player.gameMode()is null between the moment the client enters the level and the server's first game mode packet. Servers that hold players in a "please do not move" verification phase tick the player during that window, so CrowBar's experience-gain check dereferenced a null game mode and threw aReportedExceptionfromLevel.guardEntityTick, tearing down the level session.- The game mode is now checked for null before the survival test, so the experience-gain tracker simply skips ticks that happen before the server assigns a game mode.
Affected Builds
- Minecraft 26.1.x (Fabric) and Minecraft 26.2 (Fabric) carried the bug and are fixed.
- The NeoForge builds and the 1.21.x Fabric builds never read the game mode in the experience-gain check and were never affected; they are rebuilt at 1.0.1 so every listing stays on one version.
Testing
- Verified the 26.1.x and 26.2 Fabric subprojects compile and package cleanly with the guard in place.
- Confirmed no other code path in any loader build dereferences
Player.gameMode().
Downloads
CrowBar-1.21.6-1.21.8-1.0.1.jarfor Minecraft 1.21.6-1.21.8 (Fabric)CrowBar-1.21.6-1.21.8-neoforge-1.0.1.jarfor Minecraft 1.21.6-1.21.8 (NeoForge)CrowBar-1.21.9-1.21.10-neoforge-1.0.1.jarfor Minecraft 1.21.9-1.21.10 (NeoForge)CrowBar-1.21.x-1.0.1.jarfor Minecraft 1.21.9-1.21.11 (Fabric)CrowBar-1.21.x-neoforge-1.0.1.jarfor Minecraft 1.21.11 (NeoForge)CrowBar-26.1.x-1.0.1.jar/CrowBar-26.1.x-neoforge-1.0.1.jarfor Minecraft 26.1.xCrowBar-26.x-1.0.1.jar/CrowBar-26.2.x-neoforge-1.0.1.jarfor Minecraft 26.2
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:yP7IdsBH:zTCtzPVm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yP7IdsBH:zTCtzPVm"
}

