From BetterHud

🌎 Choose language: EN — English · RU — Русский

Coming from BetterHud

HUDEngine reads configuration in the same shape BetterHud uses, so an existing HUD usually moves by copying folders. This page is what carries over, what does not, and what to do about the difference.

The two plugins are unrelated codebases that happen to agree on a config format. Nothing here is a criticism of BetterHud — it does things HUDEngine does not.

Moving

Copy these from plugins/BetterHud/ into plugins/HUDEngine/:

huds/  layouts/  images/  texts/  heads/  compasses/  assets/  fonts/

Then start the server and read the compile report. Anything HUDEngine does not understand is named with the file and the element it is in, so the list of things to fix is in front of you rather than discovered one restart at a time.

config.yml does not move. The keys differ and HUDEngine writes its own; set it up from Configuration.

What is not supported

BetterHud has	HUDEngine
popups/	no equivalent. Use a HUD and showFor from the API to show it for a while
animations/	not supported. Frames of an animation would each need their own element
backgrounds/	not supported. A background is an ordinary image on a lower layer
color-equation on a compass	parsed and ignored, with a warning
non-linear scale-equation	only the linear form is read. 1 - t/30 works; anything with a square or a curve does not
Velocity and Fabric	HUDEngine is Paper and Folia only

Everything in that table produces a warning rather than a failure, so a copied configuration starts and runs with the unsupported parts absent rather than refusing to load.

What HUDEngine adds

• condition on any image or bar, naming a value that decides whether it draws.
• Built-in values. [health], [food], [armor], coordinates, world state — about forty five of them, resolved with no PlaceholderAPI installed. See How a HUD is built.
• hide-vanilla-hud, which blanks vanilla hearts, hunger, hotbar and the rest through the pack.
• points/, fixed compass markers in config rather than only through code.
• Built-in pack hosting, so no separate web server is needed.
• Validation before compilation: every problem reported at once, with the file, the element and a suggestion for a typo.

Things that look the same but are not

• include in texts/. Same idea, and the language names match: russia, greece, japan, china, korean, thailand, hebrew, arab, hindi, bengal. HUDEngine adds cyrillic-full, and its russia is the living alphabet only rather than the whole Unicode block — which is why a Russian HUD often needs no font file here at all. See Fonts.
• max in a bar listener. HUDEngine accepts both a value name and a plain number, so max: "20" works as written.

If something is off after moving

Start with the compile report, then Troubleshooting. A HUD that renders in the wrong place vertically is usually the boss bar line rather than the configuration — see Boss bars.