All versions
1.21.9-1.21.10-1.0.1+neoforge
Release
deathhound-1.21.9-1.21.10-1.0.1+neoforge.jar10 months ago 28
Compatibility
Minecraft: Java Edition
1.21.9–1.21.10
Platform
NeoForge
Supported environments
Client-side
Changes
Changelog
All notable changes to Death Hound will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.0.1] - 2026-01-05
Fixed
- Critical: Death records now use local profile ID instead of server UUID, ensuring deaths are specific to each local Minecraft account/character and don't bleed across different profiles
Breaking
- Existing death records will not automatically migrate to the new storage format. Previous deaths will remain on disk but won't be visible in-game after updating.
[1.0.0] - 2026-01-05
Added
- Server-safe initialization for all loaders to prevent crashes when mistakenly installed on dedicated servers
- Reflection-based client environment detection for cross-loader compatibility
Fixed
- Critical: Dedicated server crash when mod is included server-side in modpacks (now gracefully no-ops)
- HUD arrow rendering reliability issues (replaced pose-stack transforms with manual rotation)
- World marker rendering performance (implemented batching, reduced GL state changes, added simple LOD)
- Hotkey toggle now properly closes Death Hound screen when already open
Changed
- Relaxed NeoForge minimum version requirement from 21.9.16-beta to 21.9.0-beta
- Refactored Forge and NeoForge entrypoints to be server-safe
- Added explicit
clientSideOnly=truemetadata to NeoForge mod descriptor - Improved marker rendering with distance-based culling (markers hidden beyond 300 blocks, wireframe simplified beyond 100 blocks)
Technical
- Split client-only initialization into separate loader-specific client classes
- Removed all
net.minecraft.client.*references from main loader entrypoints - Optimized world marker rendering loop to batch depth-test state changes
- Cached game time calculations to reduce redundant
System.currentTimeMillis()calls
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:bWgJrvXm:LuwYGkQe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bWgJrvXm:LuwYGkQe"
}

