All versions
1.2.0
Release
Warp Field HUD 1.2.08 months ago 20
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
[1.2.0] - 2026-02-16
Added
- Crosshair HUD Element -- fully custom crosshair replacement with dynamic spread
- Spread reacts to movement, sprinting, jumping, and attacking
- Configurable dot, gap size, line length, and line thickness
- Per-component color customization (lines and dot independently)
- Smooth "heartbeat" spread animation with natural ease-in/ease-out
- Foreground opacity control
- Player Tracking on Compass -- track other players directly on the compass strip
- Colored arrow glyphs for nearby players (within chunk simulation distance)
- Player Markers mode: Off / All / Tracked Only
- Track Player selector cycles through all online players via the server tab list
- Tracked player name displayed on the compass strip
- Smart Settings -- settings that don't apply to an element are now grayed out
- Crosshair: "Move This Element", "Reset Position", and "Background Opacity" are non-interactive
- Non-moveable elements are excluded from the HUD Arrange screen
- Mod Icon -- custom WarpField icon now displays in the mod menu
Fixed
- Track Player button no longer appears frozen -- now uses the server player list instead of only nearby loaded entities
- Crosshair dynamic spread animation smoothed significantly (was erratic, now gradual)
Changed
- Migrated HUD rendering from deprecated
HudRenderCallbacktoHudElementRegistry.attachElementAfter - HUD overlay now registers as a single
warpfield:hud_overlaylayer after the hotbar - Elements inherit vanilla HUD visibility rules (hidden when HUD is toggled off)
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:9Nen7JW9:qKJIXDfI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9Nen7JW9:qKJIXDfI"
}

