LederProtections 1.4.1

A maintenance release focused on clearer menus, more polished holograms, and safer, more efficient per-viewer displays.

GUI and public directory

• Replaced repeated icons in the protection menu with more distinct materials, making unrelated actions easier to tell apart.
• Added optional Minecraft skin heads for public-directory categories.
• Configure a category texture with public-protections.categories.<id>.head-texture using the 64-character hash from a textures.minecraft.net skin URL.
• Leave the texture blank to use the category's configured material icon. Invalid or unsupported values also fall back to that icon.
• Category textures are validated locally; the plugin does not contact a skin catalogue at runtime.

Holograms

• Removed the large rectangular background panel from protection holograms while keeping text shadows for readability.
• Improved the default hologram to show a welcome message, protection name, owner, description, world, and protection coordinates.
• Documented the available native hologram variables in config.yml, including {title} / {name}, {owner}, and {user}.
• Clarified the distinction between {owner} (the protection owner) and {user} (the player viewing the hologram).
• Holograms that use {user} are displayed privately to each nearby viewer, so viewer-specific text is not shared with other players.
• Updated viewer displays on relevant events such as movement, joining, respawning, and chunk loading. Displays are cleaned up when players leave the area or disconnect.
• Holograms do not use per-tick world scans or force chunks to load just to display text.
• Hologram lines support legacy & color and formatting codes.
• PlaceholderAPI tokens can be used in holograms when PlaceholderAPI is installed. Private holograms resolve them using the viewer's context and refresh on movement or reload, not every tick.

bStats metrics

• Server owners can disable bStats for all plugins in plugins/bStats/config.yml by setting enabled: false.

Compatibility and configuration

• Continues to use Bukkit APIs and the existing supported Spigot API matrix.
• No protection-data migration is required.
• Existing custom hologram lines are preserved when the configuration is updated.
• If a custom hologram line used {user} to mean the protection owner, change it to {owner}. {user} now means the viewing player.