Resource Packs

Resource packs

The resource-pack integration provides customized restriction messages for supported map interfaces and restores the display name of the test block used for the Xaero restriction. Blocking and alerts do not require a resource-pack plugin, but the customized presentation requires a pack that the player accepts.

resource-pack:
  enabled: true
  provider: none
  rebuild-on-reload: false

Set enabled to false to disable the integration. This does not automatically remove files previously written to a provider's pack. The none setting can still select an installed provider automatically; it is not a switch to disable integration. auto also selects automatically. When several supported providers are present, the selection priority is ItemsAdder, Nexo, CraftEngine, then Oraxen. To choose one explicitly, set provider to itemsadder, nexo, craftengine or oraxen.

The integration writes its assets into these locations inside the server directory:

Provider	Assets location
ItemsAdder	plugins/ItemsAdder/contents/dev/resourcepack/assets
Nexo	plugins/Nexo/pack/external_packs/NahNoMinimap/assets
CraftEngine	plugins/CraftEngine/resources/nahnominimap/resourcepack/assets
Oraxen	plugins/Oraxen/pack/assets

Existing language JSON is merged: unrelated keys are preserved, while keys managed by NahNoMinimap are updated. Check for conflicts if other packs change the same keys. Resource-pack providers may differ in how they merge and distribute assets; verify the resulting pack on your server. In particular, ensure CraftEngine merges language JSON when other resources target the same files.

Rebuilding

After changing the message or pack assets, rebuild and distribute the pack using your provider. Examples:

Provider	Rebuild or reload command
ItemsAdder	/iazip
Nexo	/nexo reload pack
CraftEngine	/craftengine reload all
Oraxen	/oraxen reload pack

Alternatively, set rebuild-on-reload: true to request a provider rebuild when running /nm reload. Leave it false to rebuild manually. Make sure players receive and accept the updated pack; a rebuild alone does not guarantee delivery.

When provider is none and no supported provider is installed, pack changes must be handled manually. See Languages for the message and language settings.