ArtemisMultipacks
在玩家加入时发送多个资源包——充分利用 Minecraft 原生的 1.20.3+ 多包堆叠系统。
无需黑客手段,无需客户端模组,无需外部库。ArtemisMultipacks 利用 Paper 内置的 addResourcePack API,将任意数量的资源包排队并干净地堆叠起来,以便玩家在加入时自动加载所有资源包。
✦ 功能特性
- 无限数量资源包 — 在
config.yml 中定义任意数量的资源包。没有硬编码的限制。
- 优先级排序 — 资源包按从上到下的顺序应用。配置文件中列在底部的资源包具有更高的优先级,这与原版堆叠机制完全一致。
- 单包独立设置 — 每个资源包都可以独立配置其 URL、SHA-1 哈希值、强制要求标志以及提示消息。
- 强制要求执行 — 将任何资源包的
required: true,即可踢出拒绝该资源包的玩家。
- MiniMessage 提示 — 接受/拒绝对话框支持针对每个资源包的全套 MiniMessage 格式(如
<gold>、<rainbow>、渐变效果等)。
- 加入延迟 — 在发送资源包之前可配置的刻数延迟,给予客户端足够的时间完成生成,从而防止竞态条件。
- SHA-1 验证 — 在加载时捕获格式错误、缺失或占位符哈希值,并在控制台中显示清晰的警告,而不是在运行时静默失败。
- URL 验证 — 在注册之前验证 URL 是否为
http:// 或 https:// 且具有有效主机名。
- 热重载 — 更改资源包列表后使用
/multipack reload,无需重启服务器。
- 重新发送命令 — 根据需要向自己或任何在线玩家推送所有资源包。非常适合测试。
✦ 命令
| 命令 |
描述 |
权限节点 |
/multipack reload |
重载配置并重新注册所有资源包 |
multipack.admin |
/multipack resend [player] |
向你自己、指定玩家或所有人(从控制台)重新发送所有资源包 |
multipack.admin |
/multipack list |
列出当前已加载的所有资源包 |
multipack.admin |
multipack.admin 默认仅允许 OP(管理员) 使用。
所有命令均支持 Tab 补全。
✦ 配置
# 加入后多少刻再发送资源包。
# 较小的延迟可防止与客户端加载产生竞态条件。
# 20 刻 = 1 秒
send-delay-ticks: 20
resource-packs:
# 资源包键只是标签——你可以随意命名它们。
# 资源包按顺序发送:顶部=最低优先级,底部=最高优先级。
base_pack:
url: "https://example.com/base.zip"
sha1: "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2"
required: true
prompt: "<gold>请接受此资源包以进行游戏!</gold>"
addon_pack:
url: "https://example.com/addon.zip"
sha1: "0f1e2d3c4b5a0f1e2d3c4b5a0f1e2d3c4b5a0f1e"
required: true
prompt: ""
查找你的 SHA-1 哈希值:
Linux / Mac: sha1sum yourpack.zip
Windows: certutil -hashfile yourpack.zip SHA1
✦ 依赖要求
- Paper 1.21.1+(或任何分支版本——Purpur、Folia 等)
- Minecraft 客户端 1.20.3+(多包堆叠功能在此版本中添加)
- 无需其他插件
✦ 为什么选择多包而不是合并?
合并资源包既繁琐又容易在你更新其中一个时出错。Minecraft 的原生多包系统让你能够保持资源包的模块化和独立性——更新一个而不影响其他包。ArtemisMultipacks 通过单个配置文件让管理这一系统变得极其简单。
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.
评论 0
登录后参与评分
还没有评论,来抢沙发吧