Easel

Why Easel

• Your own pack server, locked down: every player gets a personal, signed download link that expires after 15 minutes and only works for them.
• Real merging, not overwriting: fonts, sounds, languages, atlases, item models (custom_model_data and 1.21.4+ item definitions) and note-block blockstates are combined, so plugin packs stop fighting.
• Works with your plugins: /easel integrations detects plugin packs (Nexo, ItemsAdder, Stormwall and others) and tells you what to change in their configs.
• Fast for players: builds are reproducible (same content, same hash), so clients keep their cached copy; with multiple packs, players only download what changed.
• Safe updates: edit a pack and it's rebuilt and pushed to online players within seconds. A broken upload never replaces the last working build.

Features

Pack merging

• Merge any number of folders or zips, with priorities; /easel info reports every override.
• JSON minified, junk files stripped, zip-in-a-folder mistakes fixed, uppercase asset paths flagged.
• Zip-slip and zip-bomb protection on every source.

Multiple packs

• Several outputs layered together (1.20.3+ clients), per-world outputs on Paper, per-server outputs on Velocity.
• Older clients via ViaVersion automatically get one combined pack.
• Per-output permission gating.

Velocity

• Install on the proxy only: packs are sent once and survive server switches.
• Different packs per backend server.

Security & operations

• Per-IP rate limits and download caps, optional speed cap and IP binding, trusted reverse-proxy support, optional native HTTPS.
• Required packs: kick on decline or failed download, with retries and an easel.bypass permission.
• Web dashboard (/easel dashboard): a one-time sign-in link, no password to set or leak.

Supported versions

• Java 21+
• Paper 1.21.4+ (including Folia and 26.x)
• Velocity 3.4+ and 4.x

Quick setup

1. Put the jar in plugins/ on your Paper server, or on your Velocity proxy (not the backends).
2. Start once and open TCP port 7270 (or set server.port).
3. Drop packs into plugins/Easel/packs/ and run /easel reload.
4. Run /easel test: the printed /health URL should say ok from another network.

Commands

All need easel.admin (op by default).

/easel dashboard      one-time link to the web dashboard
/easel integrations   detected plugin packs and what to change
/easel reload         reload config, rebuild, resend changed packs
/easel list           outputs with size, hash and sources
/easel info <output>  what was merged and overridden
/easel send <player|*> offer packs again
/easel status         web server, downloads, refused requests
/easel test           check the web server answers