-
-
Notifications
You must be signed in to change notification settings - Fork 33
FAQ
Don't forget you need to reapply the resourcepack.
- No resourcepack was 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
- If you're using ItemsAdder, will need to set text-effect to false.
Link: https://github.com/toxicity188/BetterHud/wiki/How-to-install
- Change
merge-boss-bar:
in config.ymlmerge-boss-bar: false
- This is a specialized bossbar and cannot be resolved.
- If you don't use
shader.yml
set:
#shader.yml file
hotbar:
disable: false #true by default
and config.yml
to:
#config.yml file
load-minecraft-default-textures: false
-
font.yml: If you don't use default font
scale: 1
-
Minimize font usage types.
It's a problem with that font. You need to replace it with a different font.
itemsadder used as an example, but the general cause and solution is the same
Shader core files used by betterhud.
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 itemsadder, or when 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"
Be aware of legacy format in PlaceholderAPI. Some placeholders return text with legacy format. it can cause errors 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
- text layout has
use-legacy-format
set tofalse
(default:true
) - legacy-serializer in
config.yml
contains legacy characters of a different type than the one set.
This is usually caused by issue 2. If you encounter this error, try applying a different type and restarting the server.
types of legacy-serializer: ampersand
(&), section
(§)
Yes we give support, join our Discord: https://discord.gg/5tGVx34sQG