File Details
1.21.9-1.21.10-1.0.1+forge
- R
- Jan 6, 2026
- 63.86 KB
- 36
- 1.21.10+1
- Forge
File Name
deathhound-1.21.9-1.21.10-1.0.1+forge.jar
Supported Versions
- 1.21.10
- 1.21.9
Curse Maven Snippet
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

