PackMerger

Delivery reliability: every player gets the pack, every time, and the pack that is advertised is always the pack that is served. Self-hosting works out of the box, and tells you exactly what to fix when it can't. Plugin packs are discovered from many more plugins and re-merged when a plugin rebuilds its pack, and colliding item definitions, models and overlays are merged the way the client actually reads them. Added · Self-heal resend: FAILED_DOWNLOAD or DISCARDED triggers a resend after distribution.retry.delay-ticks (default 40), at most distribution.retry.max-attempts (default 3) times per session. INVALID_URL and FAILED_RELOAD are not retried; a specific diagnosis is logged instead. · distribution.enforce-required (default off): with required: true, kick players who decline the pack, or whose download still fails after the retries, with a configurable MiniMessage kick-message. · distribution.skip-bedrock-players (default true): Floodgate (Bedrock) players are not sent the Java pack. Detected through the Floodgate API when Floodgate is installed. · Reachability verification (upload.self-host.verify, default true): after every upload the first KiB of the pack is fetched from 127.0.0.1:<port> and from the advertised URL and compared byte for byte (the latter catches closed ports, missing NAT hairpinning and misrouted proxies). It runs off the main thread, and the new pack is only served at /pack once it is published (the check uses a one-off ?pm-verify= token), so the advertised SHA-1 always matches what /pack serves. Failures are logged, sent to online admins and shown in /pm status. · upload.fallback (default []): providers to publish through, in order, when upload.provider fails to upload or (self-host) fails verification or has a non-routable auto host, e.g. ["s3"]. If nothing better works, a self-host URL that failed its check is still used rather than sending no pack. · upload.self-host.public-host: host name or IP for the auto-built URL. · upload.self-host.detect-public-ip (default false) and public-ip-services: opt-in lookup of the server's public IP. This contacts a third party (by default Amazon checkip, then ipify), which learns the server's IP; it runs once per start/reload and only when public-url and public-host are empty. · /pm status shows the hosting route (and why a fallback was used), the self-host port and whether it is listening, the resolved host and where it came from (with the exact setting to change when it is not routable), and the last verification result with its reason and time. · Admins (packmerger.admin) get a notice a few seconds after joining when players probably can't download the pack. · Self-host warns when its port is out of range, equals the Minecraft port, or collides with rcon.port/query.port (when enabled). · messages_en.yml keys missing from an older copy on disk now fall back to the bundled text instead of showing the raw key. · 13 more plugin-pack integrations: Nova, BetterHUD, ValhallaMMO, vane-core, BackpackPlus, BetterStructures, CannonRTP, EternalTD, InfiniteVehicles, MegaBlockSurvivors and ResurrectionChest from disk, plus MMOInventory and RealisticSurvival, whose packs are downloaded from the author's published link only while the plugin is installed (opt out with plugin-packs.sources.<alias>.enabled: false). · Cluster sources: a folder holding several packs is unioned into one staged pack (lang/atlas/sounds/model JSON merged, first pack wins other clashes). Folders of packs are detected automatically; cluster: true forces it. · Operator-defined adapters: any alias under plugin-packs.sources that is not built in becomes an adapter (plugin, path (string or list), cluster, enabled), so new plugins need no release. Built-ins accept the same keys, and url for the two download-only plugins. · Plugin pack watcher (plugin-packs.watch.enabled, interval-seconds, default on / 5 s): polls the resolved source paths and re-merges when a plugin rebuilds its pack, so /oraxen reload-style rebuilds no longer need a /pm command. · Stability check (plugin-packs.stability.polls / interval-millis, default 3 / 1000): a changed source is copied only once its size and mtime hold steady, so half-written zips are never staged; a still-changing source is retried. · /pm merge: re-stages plugin packs, merges and uploads without reloading the config. It was documented before but did not exist. · /pm status lists the plugin packs merged on the last pass. · ItemsAdder zip protection and compress-json-files are detected and reported in the admin advisory. · merge.model-policy (whole-file | deep) controls how colliding models and blockstates are combined. See "Changed" for the new default. · Merge notes in provenance: every collision warning and automatic rewrite a merge strategy makes is stored with the file in the provenance sidecar and shown by /pm inspect collisions and /pm inspect export. The console prints one summary line per merge. · Overlay format repair: when two packs' overlay lists are combined and any entry reaches format 64 or below, entries that only declare min_format/max_format gain the matching formats range, which 1.21.9+ clients require for the list to load. The merged pack.mcmeta also declares the union of both packs' format ranges in a consistent shape (min_format/ max_format, plus supported_formats and an in-range pack_format when the range reaches format 64 or below). · Pack registration API: PackMergerApi.registerPack(plugin, alias, Path|URI[, PackOptions]), unregisterPack(alias) and getRegisteredPacks(). Registered packs are staged into packs/.api-packs/<alias>.zip with the same validation, cluster union and stability check as plugin packs, are placed in priority: by alias, and are dropped automatically when the owning plugin is disabled. Registering schedules a (coalesced) merge. PackMergerApi.get() returns the API (it is also registered with Bukkit's ServicesManager). · PackMergerCollectPacksEvent: fired asynchronously at the start of every merge so plugins can contribute packs lazily; packs registered from it are part of that merge. · Other pack hosts: PackMerger detects ItemsAdder (resource-pack.hosting.*), Oraxen (Pack.upload.enabled, Pack.dispatch.send) and Nexo (Pack.server.type) hosting or sending their own pack, plus ItemsAdder unzip protection and compress-json-files, and reports them on the console, in /pm status and to admins on join with the exact setting to change. · /pm fixup <itemsadder|oraxen|nexo> backs up that plugin's config (<file>.packmerger-backup-<date>), writes the fix (keeping comments) and says which reload command to run; /pm fixup lists the findings and /pm fixup dismiss hides the current ones (persisted in dismissed-warnings.yml). · /pm verbose [on|off] switches debug logging at runtime and saves it as log-level (debug/info). · merge.output-copy-to (default []): folders that get a copy of every merged zip (written via a temp file; folders inside packs/ are refused). · /pm status also shows the last upload result, each installed pack-generating plugin and its state, API-registered packs, other pack hosts, the Bedrock/Floodgate/Geyser state and the log level. · Bedrock: Geyser's folder is detected (an installed Geyser-* plugin's data folder, then plugins/Geyser-Spigot, then plugins/Geyser-Paper) instead of assuming Geyser-Spigot. · BungeeCord proxy plugin (packmerger-bungee, new jar in every release). Bungee has no resource-pack API, so it asks PackMerger on the player's backend to send the network pack with a signed request; needs secret on both sides and PackMerger on the backends. Same config and behaviour as the Velocity plugin otherwise. · Signed proxy mess