Common Questions
Last updated
Last updated
The default bossbar in plugin should be Yellow. If you see a purple bossbar, it's a bug in Lunar Client.
You should surround your images with font tags for instance
This is because the plugin doesn't know the advance(width) of your custom images. Images registered in CustomNameplates would fit the background but if you are using another plugin for instance ItemsAdder to create new images, you should input your images' advance at /configs/advance-data.yml.
If you are using a custom font through bitmap, just put it into plugin's /font folder and override the previous one. Then delete the /tmp folder from the plugin folder. At last, restart the server.
This is caused by ItemsAdder hud. Just disable it in ItemsAdder config.yml
If the image is registered by CustomNameplates, simply edit the ascent option.
You can't move the image down/up from CustomNameplates side if you are using an image from other plugins. Actually it's easy to fix because in those plugins they provide an option to edit the image's ascent (In ItemsAdder it's called y_position)
You should give them permission "bossbar.show" or remove the permission condition from bossbar configs.
This is because any chat plugin would cancel the player chat event. To solve that, firstly check if the plugin is officially supported in config.yml and enable the integration if available
If you are using an unsupported plugin, you can make a suggestion, but only if that plugin has an API repository. The worst solution is to turn on unsafe-chat-event in config.yml
Setting send-delay to a proper value in config.yml would fix
If you encounter shader conflicts, you will need to either merge the shaders (which requires some GLSL knowledge) or disable the CustomNameplates shader.
If you notice that your background color is unusually dark, it means the shader has not been successfully applied to your client. This is usually caused by a shader conflict, as the client can only apply one shader at a time. If you need to use multiple shaders, you'll have to manually merge them. If you're unable to resolve the issue, you can consider reducing the opacity of the image as an alternative solution. This can help mitigate the visual impact of the shader conflict.
(Alternative images can be downloaded here. To use, replace the ones under /contents/backgrounds/ folder)
This issue occurs because unifont_jp cannot be read by clients running versions 1.19.4 to 1.20.3, and unifont cannot be read by 1.19.4 clients. This means that compatibility between certain fonts and specific Minecraft versions may lead to display issues.
If you're running a 1.20+ server, you can consider removing unifont_jp as shown in the example below if you don't really need it:
If you're running a 1.19.4 server, you can configure as shown in the example below:
