Перейти к содержимому
Mineforgian

ElytraHud3

Aviation-style flight HUD for elytras (Fabric & NeoForge) — speed, altitude, artificial horizon, compass. Do a Barrel Roll compatible.

Загрузки
7K
Подписчики
3
Обновлён
5 августа 2026 г.
Лицензия
MIT

Опубликован 12 июня 2026 г.

Исходный кодСообщить об ошибке

ElytraHud3

Need help or found a bug? Report it at the support forum.

ElytraHud3 is a client-side aviation-style flight HUD for elytra flight. While you glide it draws a corner instrument cluster - airspeed, altitude, vertical speed, an artificial horizon, a compass, and elytra durability - so you can fly your elytra on instruments instead of by guesswork.

This is my effort to keep one of my favorite mods alive - updated for the 26.x series and the newest Minecraft versions as they release.

Ships for Fabric, NeoForge, and Forge across Minecraft 1.20 through 26.x (Forge through 1.21.11; on 26.x it's Fabric and NeoForge). Client-side only - safe to run without installing it on the server. Based on elytrahud-rework by inorganic / wancor1. Licensed MIT.

Source code: minecraft-1.20-26.3 branch

Why ElytraHud3

  • Fly on instruments. A full six-gauge cluster - airspeed, altitude, vertical speed, artificial horizon, compass, and durability - appears the moment you start gliding and clears when you land.
  • Roll-aware horizon. The artificial horizon tilts with your view and is compatible with Do a Barrel Roll, so aerobatics read correctly.
  • Your units, your layout. Toggle imperial (default) or metric, and turn each gauge, its title, and its numeric readout on or off independently.
  • Lightweight and client-side. Pure Java, about 33 KB, with no Kotlin / FLK / YACL runtime dependencies - no blocks, no items, no commands, no server install, just a HUD.
  • Everywhere you play. Runs across Minecraft 1.20 through 26.x on Fabric, NeoForge, and Forge (Forge through 1.21.11).

Usage

Install it on the client - it does nothing on a server and does not need to be installed there. Equip and deploy an elytra and start gliding; the instrument cluster appears in the corner while you are fall-flying and disappears when you land. ElytraHud3 adds no blocks, items, or commands - it is a HUD only.

Open the config screen through Mod Menu (Fabric) or the loader's mod-config entry (NeoForge / Forge) to toggle individual gauges, their titles, and their numeric value boxes, and to switch between imperial and metric units.

Dependencies

  • Fabric API - required on Fabric builds.
  • Mod Menu and Do a Barrel Roll - optional (Do a Barrel Roll enables the roll-aware horizon).

Credits and license

MIT. Based on elytrahud-rework by inorganic / wancor1 (MIT); ElytraHud3 modifications (c) Kishku7. Flight-HUD design inspired by neo-elytra-hud (CC0) and by Microsoft Flight Simulator's instrument styling; roll compatibility via Do a Barrel Roll's public API.

Ченджлог

1.2.11+26.3Бета26.3-snapshot-7 · 5 августа 2026 г.

Changed

  • Fabric 26.3 cell moved to MC 26.3-snapshot-7 (from snapshot-6): fabric-api 0.156.1+26.3 -> 0.156.2+26.3, resource pack_format 94 -> 95, exclusive window [26.3-alpha.6, 26.3-alpha.7) -> [26.3-alpha.7, 26.3-alpha.8). Every 26.3 snapshot bumps pack_format by one, so each jar stays snapshot-exclusive. No other cell changed.

Notes

  • No source change required. snapshot-7's breaking surfaces were checked against this mod and none are touched: the trailing Prediction argument on LivingEntity.drop(ItemStack, boolean) / Inventory.placeItemBackInInventory, the client-side LocalPlayer.drop(boolean) return type going boolean -> void, the InteractionResult.SwingSource CLIENT/SERVER -> PREDICTED/SERVER_ONLY rename together with the deletion of ServerboundSwingPacket, and the 32 new concrete slab/stair blocks plus the filled-map colour component removals.
1.2.10+26.1-neoforgeРелиз26.1, 26.1.1, 26.1.2 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.8-forgeРелиз1.21.8 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.11-neoforgeРелиз1.21.11 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.11-forgeРелиз1.21.11 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.11Релиз1.21.9, 1.21.10, 1.21.11 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.10-neoforgeРелиз1.21.10 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).
1.2.10+1.21.10-forgeРелиз1.21.10 · 1 августа 2026 г.

Fixed

  • Full D1-D22 doctrine re-audit found + fixed real live-boot and resource-pack bugs across 9 cells. Rebuilt and republished the affected (loader, MC) pairs:
    • D3 claim-gate over-claims (4 cells), root-caused via built-jar manifest inspection: Forge/1.21.1 claimed MC [1.21,1.21.2) needing javafml 52+, but MC 1.21.0 shipped Forge 51.0.33/javafml 51 -- narrowed to [1.21.1,1.21.2). Forge/1.21.8 claimed [1.21.6,1.21.9) needing javafml 58+, but 1.21.6/1.21.7 are permanent orphan Forge builds -- narrowed to [1.21.8,1.21.9). Forge/1.20.6 claimed [1.20.5,1.21) but Forge never shipped MC 1.20.5 -- narrowed to [1.20.6,1.21). NeoForge/1.21.1 had the same shape ([1.21,1.21.2) vs the neo 21.1 floor, MC 1.21.0 ships neo 21.0.x) -- narrowed to [1.21.1,1.21.2). Each of these previously refused to boot on part of its claimed range.
    • D3a NeoForge 26.1 over-blocking floor: relaxed [26.1.2.0-beta,) -> [26.1.0-alpha,) -- the mod's actual NeoForge glue uses no 26.1.2-specific API, so the tighter floor was silently blocking 26.1 and 26.1.1 users for no reason.
    • D4 pack.mcmeta dead-zone (5 cells) -- the mod had never gotten the 2026-07-12 doctrine correction every sibling mod already carries. Fabric/1.21.11, NeoForge/1.21.10, NeoForge/1.21.11 were shipping the WRONG resource-major pack.mcmeta (should ship NONE -- both loaders synthesise correct metadata in the 1.21.9-1.21.11 dead zone); Forge/1.21.10/1.21.11 were shipping the wrong major too (corrected to the DATA-major form, 88/94). A present-but-wrong pack.mcmeta drops the mod's WHOLE resource pack on Forge/NeoForge -- HUD gauge textures and lang were gone for every live user on those versions. Verified in every rebuilt jar (unzip-checked) and client-render smoketested.

Changed

  • Version 1.2.9 -> 1.2.10 on the 10 affected cells only (Forge 1.20.6/1.21.1/1.21.8/ 1.21.10/1.21.11, NeoForge 1.21.1/1.21.10/1.21.11/26.1, Fabric 1.21.11); every other cell is byte-unchanged and stays at its prior published version. All 10 rebuilt -Xlint:all zero warnings; client-render smoketested on Raider (all 10 CELL PASS, HUD instruments verified by eye in every screenshot).

Комментарии

Загружаем…