FAQ

Try "/hud reload" does not move the y coordinate.

You will also need to reapply the resourcepack.

---

HUD doesn't appear

• No resourcepack were applied. Go and apply it.

• The Resourcepack path for BetterhHud is 'BetterhHud/build' by default.

• If you're using ItemsAdder, go here -> https://github.com/toxicity188/BetterHud/wiki/How-to-install

Don't see any bossbars, don't see any HUD, it's clean.

• If you're using ItemsAdder, will need to set text-effect to false.

Link: https://github.com/toxicity188/BetterHud/wiki/How-to-install

If the bossbar for Enderdragon or Wither pops up, the HUD is out of alignment.

• Set on config.yml merge-boss-bar: false

• This is a specialized bossbar and cannot be resolved.

Optimize resourcepack

1. config.yml If you don't use shader.yml set:

#shader.yml file
hotbar:
	disable: false #true by default

and:

#config.yml file
load-minecraft-default-textures: false

2. font.yml: If you don't use default font scale: 1

3. Minimize font usage types.

Text is displaying strangely

It's a problem with that font. need to replace it with a different font

Items turned black

have used itemsadder as an example, but the general cause and solution is the same.

the shader core files that betterhud is using.

rendertype_entity_cutout.vsh, rendertype_entity_translucent_cull.vsh, rendertype_text.vsh, block.fsh, block.vsh, item.fsh, item.vsh, text.vsh, text.fsh

the resourcepack for betterhud was not merged properly, resulting in only some shader cores being applied.

this happens when you make a mistake in the itemsadder, or when the itemsadder has a different shader core inside and ignores the betterhud's shader core.

check and resolve the console error caused by a configuration error in itemsadder, or delete all shader core files that are duplicated with betterhud in the folders included in “merge_other_plugins_resourcepacks_folders” or in "itemsadder/contents"

When put the PlaceholderAPI in pattern, the layout disappeared.

Be aware of legacy format in PlaceholderAPI.

Some placeholder returns a text with legacy format. it can occurs error with BetterHud.

for example, a color code. e.g.&aText

Even if it is plainly printed in white, it may be color-coded like "&fText", "§fText".

This issue can be caused by the following

1. text layout has use-legacy-format set to false (default: true)
2. legacy-serializer in config.yml contains legacy characters of a different type than the one set.

It is usually caused by issue 2. If you get the error, try applying a different type and restarting the server.

types of legacy-serializer: ampersand(&), section(§)

Extra Support?

Yes we have support, join our Discord: https://discord.gg/5tGVx34sQG Remember that BetterHud is a free plugin, and we have no obligation of answer sometimes.