ArtemisMultipacks

Send multiple resource packs to players on join — fully leveraging Minecraft's native 1.20.3+ multi-pack stacking system.

No hacks. No client mods. No external libraries. ArtemisMultipacks uses Paper's built-in addResourcePack API to queue as many packs as you want, stacked cleanly so your players load all of them automatically when they join.

✦ Features

Unlimited packs — Define as many resource packs as you want in config.yml. No hardcoded limits.
Priority ordering — Packs are applied top-to-bottom. Packs listed lower in the config take higher priority, exactly like vanilla stacking.
Per-pack settings — Each pack independently configures its URL, SHA-1 hash, required flag, and prompt message.
Required enforcement — Set required: true on any pack to kick players who decline it.
MiniMessage prompts — The accept/decline dialog supports full MiniMessage formatting per pack (<gold>, <rainbow>, gradients, etc.).
Join delay — A configurable tick delay before packs are sent gives the client time to finish spawning in, preventing race conditions.
SHA-1 validation — Malformed, missing, or placeholder hashes are caught at load time with a clear console warning rather than silently failing at runtime.
URL validation — URLs are validated to be http:// or https:// with a real host before they're registered.
Live reload — Change your pack list and hit /multipack reload — no server restart needed.
Resend command — Push all packs to yourself or any online player on demand. Useful for testing.

✦ Commands

Command	Description	Permission
`/multipack reload`	Reload config and re-register all packs	`multipack.admin`
`/multipack resend [player]`	Resend all packs to yourself, a named player, or everyone (from console)	`multipack.admin`
`/multipack list`	List all currently loaded packs	`multipack.admin`

multipack.admin defaults to OP only.
All commands support tab completion.

✦ Configuration

# How many ticks after join to send the packs.
# A small delay prevents race conditions with client loading.
# 20 ticks = 1 second
send-delay-ticks: 20

resource-packs:
  # Pack keys are just labels — name them anything you want.
  # Packs are sent in order: top = lowest priority, bottom = highest.

  base_pack:
    url: "https://example.com/base.zip"
    sha1: "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"
    required: true
    prompt: "<gold>Please accept the resource pack to play!</gold>"

  addon_pack:
    url: "https://example.com/addon.zip"
    sha1: "0f1e2d3c4b5a0f1e2d3c4b5a0f1e2d3c4b5a0f1e"
    required: true
    prompt: ""

Finding your SHA-1 hash:

Linux / Mac:  sha1sum yourpack.zip
Windows:      certutil -hashfile yourpack.zip SHA1

✦ Requirements

Paper 1.21.1+ (or any fork — Purpur, Folia, etc.)
Minecraft client 1.20.3+ (multi-pack stacking was added in this version)
No other plugins required

✦ Why multi-pack instead of merging?

Merging resource packs is tedious and breaks every time you update one of them. Minecraft's native multi-pack system lets you keep your packs modular and independent — update one without touching the others. ArtemisMultipacks makes that system dead simple to manage from a single config file.

Artemis MultiPack

📖About Artemis MultiPack