1.2.0
Compatibility
Changes
updata log — goety-client-fix v1.2.0 Rewrote player instance detection: PlayerEvent.Clone does not fire on the client side in Forge 1.20.1, and ClientPlayerNetworkEvent.LoggingOut only fires on disconnect — neither catches death/respawn. Replaced both with tick-based tracking of Minecraft.player, which reliably detects every instance change. On player instance change: invalidates old player capabilities, clears mob targets and lastHurtByMob references in the old level, and cleans Goety/GoetyAwaken static fields via reflection. On level instance change: invalidates old ClientLevel capabilities to break reference chains. Periodic cleanup: every 30 seconds, verifies old player was GC'd and re-cleans if not. Removed dead code (PlayerEvent.Clone handler, LoggingIn handler, unused imports).
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:tqkySVQb:jodOUXko"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tqkySVQb:jodOUXko"
}

