Deliver
Resource Packs
How a design becomes a pack and how players receive it.
A build compiles every HUD in the project into fonts, textures and a text shader. The same project content always produces the same file, identified by its SHA-1. Builds are cached, and the five most recent are kept.
Building
- Deploying to a server builds automatically.
- Resource Pack in the editor and Build resource pack on the project page build and download the file.
- Warnings list anything that cannot be drawn in game, for example an image element without an image.
How it is drawn
The plugin shows each player one boss bar whose bar is invisible. Its title is text in custom fonts whose glyphs are your HUD graphics. Horizontal position comes from spacing characters and vertical position from the font definition.
The pack makes white boss bars invisible. If another plugin uses a white boss bar, give it a different color.
Delivery to players
With resource-pack.auto-apply enabled, the plugin offers the pack to players when they join and when a new deployment arrives. Before that it downloads the pack itself and compares the SHA-1; a mismatch is reported on the Servers page and the pack is not offered. The pack is required only if you set resource-pack.required or enable it in the project.
If you turn auto-apply off, distribute the downloaded pack yourself, for example by merging it into your existing server pack.
Item icons
Item icons use the client's own item textures. To place them, the web service reads texture sizes from the official client once per Minecraft version, which needs outbound access to piston-meta.mojang.com. Without it, builds succeed and item icons are left out with a warning.
Limits
- Minecraft 1.19.4 to 1.21.8. Choose the version of your server next to Build resource pack on the project page.
- 100 MB per pack
- Images larger than 256 texels are split into tiles automatically