Skip to content

External Resource Packs

alexisleder edited this page Nov 8, 2026 · 1 revision

External resource packs — 1.5.0

LederProtections ships no resource pack. It does not host, export, download, offer, merge or remove packs. Its default menus use vanilla items and readable translated text; heads are optional. The server administrator owns the artwork and distribution.

Basic setup

  1. Start with the generated menus.yml. Change materials, labels and positions first.
  2. Create or configure your server pack in your chosen pack manager. Use your own namespace and version-compatible item models/fonts.
  3. Set item-model or custom-model-data on the relevant menu icons. material supplies a readable vanilla alternative; preserve descriptive names/lore.
  4. Use pack-aware: true in menus.yml. Configure config.yml:
resource-pack:
  mode: external
  external:
    pack-id: "YOUR-PACK-UUID"

Replace the placeholder with the exact full UUID used by the server or pack manager for the pack containing your GUI resources. Do not use the SHA-1, a download URL, a random UUID or an unrelated pack UUID. LP enables models only after a matching SUCCESSFULLY_LOADED event. Other packs cannot change this state. Rejected/failed/ discarded matching packs return to fallback. Reconnect after changing the UUID or when enabling tracking after the pack has already loaded. Reloading the same UUID preserves the known state. This is client-reported load status, not asset verification.

resource-pack.mode: off disables tracking. With pack-aware: true the fallback remains active. pack-aware: false explicitly allows models/custom titles without load tracking (for administrators managing client-side packs themselves).

Menu customization

  • item-model: "myserver:menu/manage": namespaced item model on supporting servers.
  • custom-model-data: 1001: integer legacy model selection; match material and pack.
  • material: ANVIL: vanilla fallback; no dependency on a custom item registry.
  • title: optional custom font glyphs. Set a readable fallback-title or leave it empty to use LP's normal translated title. LP does not supply glyphs or fonts.
  • background and decorations: optional styling. An explicit per-menu background takes precedence over global glass colors. gui-style.clean-background: true removes the filler; set it only when that is appropriate for your layout.
  • {user}, {name}, {owner}, {id}, {title}, {plain_title} are presentation placeholders; protection-specific values require a protection context.

Example menu fragments are in examples/menus-vanilla.yml, examples/menus-heads.yml and examples/menus-external-pack.yml. They are alternatives, not files to apply together. Back up existing customization.

Integration limits

ItemsAdder, Oraxen, Nexo, CraftEngine or another server pack workflow can own delivery. LP accepts the resulting model keys/CMD and pack UUID; it does not query their item registries or automatically merge their resources. ModelEngine entity models are not automatically inventory icons. There is no automatic manager detection or claim that these plugins have all been tested in-game.

LP cannot determine whether a successfully loaded pack contains a particular model. Test your exact resources, server/client versions and proxy setup. Pack formats and future versions are the pack creator's responsibility. Detection of Bedrock through Geyser/Floodgate keeps Java model/title presentation disabled; no Bedrock pack is provided. Actual crossplay and third-party integration testing remains pending.

Upgrade from the retired integrated-pack preview

  • auto, local and standalone modes are disabled and produce an explanatory log.
  • Legacy URL/hash/profile/localhost settings are ignored, not executed.
  • LP does not open the old HTTP port or prompt joining players to download anything.
  • Recognizable LP glyph/model references get an in-memory vanilla fallback and a log warning. Positions and external namespaces remain; this does not overwrite menus.yml.
  • Replace the old theme with your own resources or a vanilla example after backing up your configuration. Old exports are left on disk; LP neither uses nor deletes them.
  • Restart the server and reconnect the client after upgrading. Remove any manually enabled old LP pack from your client if desired. LP does not remove another sender's packs.

Historical art and integration sources remain under resource-packs/ for reference, outside the build. They are not supported examples or distributed in the plugin JAR.

Configuration cleanup

gui-style now belongs to menus.yml, alongside layouts and icons. Existing values from config.yml migrate with backups; explicit values already in menus.yml win. Missing fields inherit defaults. Invalid style values reject the menu reload and retain the last valid theme. Old config values remain a fallback if file migration fails.

Clone this wiki locally