ProgressiveStages 3.0
? 通过游戏内编辑器构建完整的 Minecraft 进度系统——然后让 ProgressiveStages 在所有地方强制执行它们。
✨ 在游戏内创建你的进度
运行 /pstages editor 以打开 ProgressiveStages 编辑器图形界面。
无需手动构建每个 TOML 文件,即可创建、编辑、组织和配置你的阶段。设计整合包所需的进度流程,连接其依赖项,配置锁定和解锁条件,自定义其外观,然后在游戏内测试它。
ProgressiveStages 不仅仅是一个物品锁定模组。它是一个完整的进度创作平台,让整合包创作者能够决定玩家可以使用什么、可以前往何处、必须完成什么、进度如何共享、获得或失去阶段时会发生什么,以及整个旅程在游戏中如何呈现。
每个阶段都在一个可读的 TOML 文件中定义。一个阶段几乎可以代表任何东西:时代、章节、技能、职业、研究主题、任务里程碑、Boss 层级、维度、科技分支、魔法学派、服务器事件、临时祝福、惩罚或可购买的升级。
? 构建 practically 任何类型的进度
- 简单的
石器时代 → 铁器时代 → 钻石时代 进度。
- 多个独立的技术、探索、农业和魔法分支。
- 拥有数百个相互关联里程碑的大型任务驱动型整合包。
- 带有成本、前置条件、属性、奖励和退款功能的 RPG 风格技能树。
- 使用 FTB Teams 或全服服务器里程碑的团队进度。
- 在玩家发现其前置条件之前保持隐藏的隐秘路径。
- 会过期、死亡时消失或需要维持经验值的临时挑战阶段。
- 使用 KubeJS 和 Java API 进行完全脚本化的进度。
ProgressiveStages 本身不需要任务模组、配方查看器、团队模组、脚本模组或覆盖层模组。所有集成都是可选的,并且仅在安装了相关模组时激活。
?️ 服务器权威: 服务器掌控阶段进度、授予、撤销、依赖、成本和执行。修改后的客户端无法给自己授予阶段、伪造购买或绕过进度规则。
? 进度可能呈现的样子
进度可以是线性的:
? Stone Age
└── ? Iron Age
└── ? Diamond Age
└── ⚔️ Netherite Age
它可以分支成不同的玩法风格,然后再汇合:
? Survival Basics
└── ? Iron Age
├── ⚙️ Engineering ──────┐
│ └── ? Advanced Tech │
├── ? Arcane Studies ───┼──▶ ? Endgame
│ └── ? Master Sorcery│
└── ? Exploration ──────┘
└── ? Outer Realms
依赖关系支持 all(全部)、any(任意)和计数满足。这意味着终局阶段可以要求完成所有分支、任一专业方向,或可配置数量的路径。
? Choose a Specialization
├── ⚙️ Technology ─┐
├── ? Magic ──────┼──▶ ? Mastery (complete any 2 paths)
└── ⚔️ Combat ─────┘
阶段也可以完全独立。服务器可以同时拥有主线故事树、可选技能树、临时事件和隐藏的秘密。
?️ 玩家进度地图
使用 /stage、/stages、/ps、/stage gui 或可配置的快捷键打开地图。
3.0 版本的地图模仿了 Minecraft 的成就屏幕,同时完全由整合包作者控制:
- 熟悉的原版任务、目标和挑战框架。
- 可拖拽、滚轮缩放依赖图。
- 省略坐标时自动布局图表。
- 当偏好手工设计的布局时,精确设置
x 和 y 位置。
- 依赖连接线,使分支和汇合易于理解。
- 悬停卡片显示描述、依赖、触发进度和解锁预览。
- 点击固定详细信息面板以查看更长的信息。
- 按名称、ID、描述、类别或锁定物品进行搜索。
- 一个切换选项,用于隐藏玩家已拥有的阶段。
- 每个阶段的图标、颜色、类别、背景、框架和排序顺序。
- 直接从地图验证的服务器阶段购买。
- 自动触发条件的实时进度。
- 未知图标、隐藏的名称和防剧透安全的描述。
作者通过 [display].reveal 决定节点何时可见:
| 揭示模式 |
行为 |
always |
阶段始终可见。 |
dependencies |
当其前置路径变得相关时,阶段出现。 |
unlocked |
阶段在被拥有之前保持隐藏。 |
设置 [stage].hidden = true 可从地图中完全省略该阶段,同时在内部仍可使用它。
示例显示配置:
[stage]
id = "diamond_age"
display_name = "Diamond Age"
description = "Master diamond tools and unlock advanced machinery."
icon = "minecraft:diamond"
color = "#55FFFF"
category = "Main Progression"
tags = ["main", "tier3", "technology"]
[display]
frame = "challenge"
background = "minecraft:block/deepslate_tiles"
reveal = "dependencies"
sort_order = 30
# Optional manual map placement. Omit both for automatic layout.
x = 168
y = 0
客户端仅显示同步的数据。服务器保持权威性: 修改后的客户端无法授予阶段、绕过依赖、伪造触发进度或在未支付经验证的成本的情况下购买阶段。
? ProgressiveStages 可以限制的一切
每个分类都是可选的。全局执行设置提供整合包范围的默认值,而各个阶段的 [enforcement] 部分可以自定义其自身锁定的行为方式。
? 物品与背包
限制单个物品、标签(tags)、整个模组或 ID 模式。根据配置的不同,ProgressiveStages 可以防止:
- 使用被锁定的物品。
- 拾取该物品。
- 使用鼠标移动该物品。
- 将其保留在快捷栏或背包中。
- 放置其方块形态。
- 在铁砧中修理、重命名或合并该物品。
- 在配方查看器中隐藏或遮蔽该物品。
- 在支持的 Curios 槽位中装备它。
锁定覆盖层会渲染在普通背包、箱子、快捷栏、背包(backpacks)、铁砧以及其他基于槽位的界面中。
? 方块与交互
限制方块的放置、破坏和右键交互。细粒度的规则可以区分以下情况:
- 空手右键点击方块。
- 使用特定物品右键点击特定方块。
- 使用特定物品右键点击实体。
- 打开方块菜单。
- 打开手持物品菜单(例如背包)。
?️ 配方与合成
锁定确切的配方 ID,或锁定所有输出为已锁定物品的配方。执行保护既包括配方的发现,也包括实际的合成产出,因此在 JEI 或 EMI 中隐藏配方并非唯一的防御手段。
? 流体
限制流体的采集、桶装放置、世界内放置、流动、玩家淹没以及配方查看器的可见性。
? 作物与农业
限制种植、自然生长、骨粉使用、收获以及作物掉落。这允许农业分支中的种子、成熟作物、自动化系统或整个农业模组在不同的时间解锁。
? 维度与传送
阻止通过传送门旅行或使用命令/模组传送到被锁定的维度。一次旅行后的安全检查会捕获那些绕过正常传送门事件集成。
✨ 附魔
ProgressiveStages 可以:
- 完全锁定某个附魔。
- 使其不出现在附魔台、铁砧和交易中。
- 从现有装备中移除非法附魔。
- 将附魔等级临时限制在最大级别。
当多个缺失的阶段对同一附魔施加限制时,最严格的剩余限制生效。
[enchants]
locked = ["minecraft:mending"]
max_levels = [
"minecraft:sharpness:3",
"minecraft:protection:2"
]
⚔️ 实体、战斗与交互
限制攻击或与特定实体、注册标签、ID 模式或整个模组的交互。战斗分支可以要求一个阶段用于对抗亡灵,另一个阶段用于挑战 Boss。
? 生物生成与替换
取消锁定生物的生成,或用其他实体替换它们。这可以将后期游戏的敌人阻挡在早期区域之外,或在获得相关阶段之前将其转化为更安全的替代品。
? 宠物与坐骑
限制驯服、繁殖、指挥、互动或骑乘宠物及其他支持的实体。
? 战利品
从以下内容中过滤掉被锁定的内容:
- 箱子和生成的容器。
- 钓鱼。
- 考古挖掘。
- 生物掉落。
- 方块掉落。
- Lootr 的玩家专属战利品投掷。
战利品过滤在服务端进行,防止玩家仅仅因为某内容出现在生成的表中就获得该内容。
?️ 屏幕与菜单
阻止特定的方块菜单或手持物品菜单。当物品本身可以被携带但其配置或存储界面应该稍后解锁时,这非常有用。
?? 村民、交易与职业
使用 [trades] 根据其结果隐藏个别报价,或使用 [professions] 阻止打开整个职业的贸易界面。流浪商人没有职业,可以通过交易规则进行管理。
? 进度
被锁定的进度可以完全不对客户端显示。它们不仅仅显示为灰色——只要未拥有所需的阶段,它们就会保持隐藏状态,然后在获得阶段时无需重新登录即可刷新显示。
? 结构体
限制进入结构体,并独立控制:
- 容器访问。
- 方块破坏。
- 方块放置。
- 爆炸。
- 生物生成。
突破锁定结构体的玩家会被送回他们上一个安全位置,并可配置入口缓冲距离以使其远离边界。
? 区域
定义由手工编写的三维区域,拥有各自的限制、消息、规则标志和减益效果。区域对于服务器枢纽、地牢、竞技场、城镇、故事地点或未在 Minecraft 结构中注册的区域非常有用。
? Curios 装备槽
安装 Curios 后,各个槽位可以要求特定阶段。被锁定的装备会被弹出,并且正常的物品执行机制仍可作为后备方案。
⛏️ 矿石与加密方块
被锁定的矿石或方块 ID 可以在视觉上被替换为另一个方块——默认为石头——直到玩家获得相应阶段。区块数据、破坏行为和掉落物受到保护,确保视觉伪装不会成为绕过限制的手段。
[blocks]
locked = ["minecraft:diamond_ore", "minecraft:deepslate_diamond_ore"]
[display]
encrypt_blocks = true
encrypt_as = "minecraft:stone"
? 玩家能力
独立限制移动能力:
[abilities]
locked = ["elytra", "sprint", "swim", "climb"]
? 信标效果与酿造
限制每个玩家的信标效果,并防止未经授权的玩家或自动化系统从酿造台中提取被锁定的药水产出。
? 阶段拥有的属性
在拥有阶段时,可以为任何注册的原版或模组属性应用加成,包括生命值、缩放比例、攻击伤害、移动速度或攻击距离。修饰符支持加法、基础乘法和总乘法运算,并在阶段被撤销时移除。
? 模组中统一的匹配语言
锁定列表在几乎所有分类中都使用相同的可读语法:
| 条目 |
含义 |
示例 |
id: |
精确的注册表 ID |
id:minecraft:diamond |
| 无前缀 |
id: 的简写形式 |
minecraft:diamond |
mod: |
整个模组命名空间 |
mod:mekanism |
tag: |
注册表标签 |
tag:minecraft:logs |
# |
标签简写 |
#minecraft:logs |
name: |
不区分大小写的 ID 子串 |
name:netherite |
宽泛锁定(Broad locks)可以包含精确的排除项:
[items]
locked = ["mod:mekanism"]
always_unlocked = ["mekanism:configurator"]
如果多个阶段共同管控同一内容,玩家必须拥有所有相关的阶段。白名单或 [unlocks] 条目仅影响声明它的那个阶段;它不会静默覆盖其他阶段的锁定。
⚡ 自动阶段触发器
触发器存在于它们所解锁的阶段内部——没有单独的全局触发器文件。
一个阶段可以拥有多个 [[triggers]] 块。每个块都是通向同一阶段的不同路径。在块内使用:
mode = "all_of" 表示需要满足所有条件。
mode = "any_of" 表示只需满足至少一个条件。
内置的触发条件涵盖以下类别:
| 类别 |
示例 |
| 物品 |
手持、拾取、使用、丢弃、制作、挖掘或破坏物品/工具。 |
| 战斗 |
击杀实体、击杀Boss、使用特定物品击杀、驯服或繁殖。 |
| 玩家状态 |
等级、经验值、效果、统计数据、游戏时长、睡觉、钓鱼或骑乘。 |
| 探索 |
维度、生物群系、在生物群系中的停留时间、结构、海拔、距离及进度成就。 |
| 世界状态 |
天气、天数和世界时间。 |
| 进度状态 |
持有另一阶段一段时间。 |
| 外部进度 |
由命令、KubeJS、任务或其他模组控制的命名计数器。 |
| 自定义逻辑 |
KubeJS 谓词和脚本提供的进度。 |
基于计数器的条件在依托原版统计数据时具有回溯性。基于事件索引的评估意味着相关的游戏事件只会重新检查可能受影响的条件,而可配置的轮询间隔则安全地处理实时状态条件。
? 示例:单一必需路径
[[triggers]]
mode = "all_of"
description = "挖掘钻石并完成十个工厂任务"
[[triggers.conditions]]
type = "mine"
block = "minecraft:diamond_ore"
count = 3
[[triggers.conditions]]
type = "custom_counter"
counter = "factory_quests"
count = 10
? 示例:替代路径
# 路径 1:击败龙。
[[triggers]]
mode = "all_of"
description = "击败末影龙"
[[triggers.conditions]]
type = "kill"
entity = "minecraft:ender_dragon"
count = 1
# 路径 2:转而成为大师级探险家。
[[triggers]]
mode = "all_of"
description = "访问末地并移动 50,000 格"
[[triggers.conditions]]
type = "dimension"
dimension = "minecraft:the_end"
[[triggers.conditions]]
type = "distance"
movement = "all"
count = 50000
依赖关系始终通过正常的触发器授予得到尊重。进度可能会提前积累,但其前置规则未满足之前,该阶段无法自动授予。
? 依赖关系、作用域、标签和分类
阶段支持:
- 线性、分支、汇聚、循环验证或独立的图结构。
all、any 以及计数的依赖要求。
- 单人游玩或 FTB Teams 的团队级所有权。
- 全服务器里程碑的服务器级所有权。
- 用于组织和展示的类别。
- 用于查询和批量操作的标签。
- 隐藏的内置阶段。
- 起始阶段。
全服务器事件示例:
[stage]
id = "dragon_defeated"
display_name = "巨龙陨落"
description = "首次胜利将为整个服务器解锁末时代。"
scope = "server"
tags = ["story", "server_event"]
⏳ 阶段可以是临时的或会丢失
进度不一定是永久的。
[stage].duration = "30m" 创建一个临时阶段,在经过真实时间(包括离线时间)后过期。
[revoke].on_death = true 会在玩家死亡时移除它。
[revoke].xp_below = N 仅在总经验值高于阈值时才保留它。
[revoke].cascade = true 也会移除依赖于它的阶段。
[stage]
id = "berserker_blessing"
display_name = "狂战士的祝福"
duration = "30m"
[revoke]
on_death = true
cascade = true
这支持限时事件、临时职业、挑战模式、维持资格、诅咒、祝福以及真正的倒退系统。
? 可购买的技能树节点
[cost] 表将阶段变为可购买的地图节点。
[cost]
xp_levels = 30
items = ["minecraft:diamond:5", "minecraft:emerald:3"]
bypass_requirements = false
cooldown = "5m"
refund_percent = 50
- 依赖关系仍然有效。
bypass_requirements = true 跳过触发器要求,但不跳过前置阶段。
- 冷却时间按玩家单独追踪。
- 当购买过的阶段被撤销时,退款可以返还物品和经验值成本的一定百分比。
- 任何成本扣除前,服务器都会重新验证每次购买。
这使得 ProgressiveStages 适用于 RPG 技能、研究系统、声望树、职业升级以及无需额外 GUI 模组的服务器商店。
? 奖励与解锁展示
[rewards] 控制玩家在真正获得阶段时收到的内容:
[rewards]
items = ["minecraft:diamond:5", "minecraft:netherite_scrap:2"]
effects = ["minecraft:strength:120:1", "minecraft:regeneration:60:0"]
commands = [
"give {player} minecraft:cake 1",
"say {player} has entered the Diamond Age!"
]
teleport = "minecraft:the_nether 0 70 0"
xp_levels = 5
xp_points = 100
奖励仅在每次真正的归属权变更时运行一次,而非在登录或同步时运行。团队进度奖励实际赚取或购买该阶段的玩家,而不是将奖励复制给每个团队成员。
[unlock] 控制瞬间的展示效果:
[unlock]
toast = "达到钻石时代!"
title = "&b&l钻石时代"
subtitle = "&7新纪元伊始"
sound = "minecraft:ui.toast.challenge_complete"
particle = "minecraft:totem_of_undying"
progress_nudges = true
hud_bar = true
每个效果均为可选。一个资源包可以使用低调的背景阶段、戏剧性的故事里程碑,或介于两者之间的任何形式。
? 完整的起始阶段示例
[stage]
id = "iron_age"
display_name = "铁器时代"
description = "冶炼铁矿石以解锁铁制工具、机械以及下一代科技层级。"
icon = "minecraft:iron_ingot"
dependency = ["stone_age"]
category = "主要进度"
tags = ["main", "technology", "tier2"]
color = "#D8D8D8"
scope = "team"
[display]
frame = "goal"
reveal = "dependencies"
sort_order = 20
show_tooltip = true
show_description_on_tooltip = true
[items]
locked = [
"minecraft:iron_pickaxe",
"minecraft:iron_axe",
"minecraft:iron_shovel",
"minecraft:iron_sword",
"minecraft:iron_helmet",
"minecraft:iron_chestplate",
"minecraft:iron_leggings",
"minecraft:iron_boots"
]
[blocks]
locked = ["minecraft:anvil", "minecraft:blast_furnace"]
[recipes]
locked_outputs = ["tag:minecraft:iron_tool_materials"]
[[triggers]]
mode = "all_of"
description = "冶炼你的第一块铁锭"
[[triggers.conditions]]
type = "advancement"
advancement = "minecraft:story/smelt_iron"
[rewards]
items = ["minecraft:iron_ingot:3"]
xp_points = 25
[unlock]
toast = "铁器时代开始了!"
sound = "minecraft:ui.toast.challenge_complete"
particle = "minecraft:happy_villager"
重要的设计原则:不要锁定获取该阶段本身所需的操作。如果开采钻石矿石解锁了“钻石时代”,玩家必须在拥有“钻石时代”之前仍然能够开采矿石;请改为锁定实用的钻石装备和高级内容。
⌨️ 命令
? 玩家与检查命令
/stage 或 /stage gui — 打开进度地图。
/stage list — 列出已拥有或可用的阶段。
/stage check — 检查所有权状态。
/stage info — 检查某个阶段的定义。
/stage tree — 检查依赖关系。
/stage progress next — 显示向可达阶段进度的情况。
/stage progress all — 显示所有可见的进度。
/stage progress <stage> — 检查单个阶段的条件。
/stage simulate — 模拟运行可达阶段及依赖阻塞项。
?️ 管理与资源包作者命令
/pstages editor — 打开游戏内阶段编辑器 GUI。
/stage grant 和 /stage revoke。
/stage tag grant、revoke 和 list。
/stage category grant、revoke 和 list。
/stage bulk grant 和 revoke。
/stage counter get、add、set 和 reset。
/stage sync 用于刷新玩家的客户端状态。
/stage new <id> 用于生成新的 TOML 阶段脚手架。
/stage export 用于生成 Markdown 格式的进度指南。
/progressivestages reload 用于经过验证的热重载。
/progressivestages validate 用于解析、注册表、图和触发器的诊断。
/progressivestages ftb status 用于 FTB Quests 的诊断。
命令建议会根据加载的阶段 ID、标签、类别、玩家和计数器名称(如适用)自动生成。
? KubeJS 脚本编写
当安装 KubeJS 时,服务器脚本会收到一个全局 ProgressiveStages 对象,而玩家会获得一流的 player.stages 桥接接口。
ProgressiveStages.has(player, 'diamond_age')
ProgressiveStages.grant(player, 'diamond_age')
ProgressiveStages.revoke(player, 'diamond_age')
ProgressiveStages.toggle(player, 'diamond_age')
ProgressiveStages.available(player, 'diamond_age')
ProgressiveStages.percent(player, 'diamond_age')
ProgressiveStages.progress(player, 'diamond_age')
ProgressiveStages.addCounter(player, 'factory_quests', 1)
ProgressiveStages.openGui(player)
API 还支持:
- 针对实际引擎更改触发的授予和撤销回调。
- 自定义布尔触发条件。
- 自定义进度提供程序。
- 命名计数器。
- 立即触发评估。
- 依赖项和受依赖项查询。
- 标签和类别查询。
- 批量授予和撤销。
- 定义快照。
- 同步功能。
授予和撤销调用返回所有权是否实际发生变化;批量操作返回发生变化的阶段数量。
自定义条件示例:
ProgressiveStages.condition('is_rich', player => {
return player.inventory.count('minecraft:diamond') >= 64
})
[[triggers]]
mode = "all_of"
[[triggers.conditions]]
type = "script"
id = "is_rich"
☕ Java API
ProgressiveStagesAPI 向其他模组暴露所有权、定义、依赖项、触发进度、计数器、批量变异和同步功能。NeoForge 事件报告实际的授予和撤销及其原因,包括命令、触发器、购买、集成和回退。
可选集成被隔离在兼容性层和保护型 mixin 之后,因此核心模组不需要加载可选类即可运行。
? 可选集成
| 集成项 |
ProgressiveStages 提供的功能 |
| EMI |
隐藏锁定的条目,添加覆盖层/工具提示,并在阶段变更后立即刷新。 |
| JEI |
隐藏锁定的物品/配方,并在解锁后立即恢复它们。 |
| FTB Teams |
共享团队范围内的阶段,同时保留单人回退选项。 |
| FTB Quests + FTB Library |
所需阶段字段、阶段任务、奖励和实时重新检查。 |
| KubeJS |
全局脚本 API、player.stages、回调、自定义条件和计数器。 |
| Jade |
在查看被锁定的方块或实体时显示所需阶段。 |
| WTHIT |
在查看被锁定的方块或实体时显示所需阶段。 |
| Curios |
限制装备槽位并弹出被锁定的装备。 |
| Lootr |
过滤每个玩家独立的战利品投掷结果。 |
| Mekanism |
处理重度 NBT 变体、化学品及相关自动化表面。 |
| Nature's Compass |
防止会绕过锁定维度进度的搜索。 |
| Create |
保持由 Create 驱动的交互和采集路径的正确分类。 |
| Visual Workbench |
通过替换工作台行为,保持对方块和制作的强制执行。 |
除非整合包使用了相应功能,否则所有集成均为可选。
? 配置结构
首次启动后:
config/
└── progressivestages/
├── progressivestages.toml
└── stages/
├── stone_age.toml
├── iron_age.toml
└── diamond_age.toml
progressivestages.toml 包含全局默认值、执行与性能设置、集成开关、披露设置、视觉行为以及可自定义的消息。
stages/ 包含各个阶段的 TOML 文件。
- 支持嵌套文件夹以组织大型整合包。
- 生成的
diamond_age.toml 是一个带有大量注释的参考文件,涵盖了完整的模式定义。
- 数据包可以在
data/<namespace>/progressivestages/stages/*.toml 提供默认值。
- ID 相同的配置文件中的阶段会覆盖数据包版本。
- 旧版布局可以迁移,而不会覆盖现有的 3.0 目标。
✅ 安全重载与验证
/progressivestages reload 不会部分应用损坏的数据。它会先构建并验证完整的候选快照。如果解析失败、阶段 ID 重复、依赖图无效、注册表引用失效或运行时应用失败,之前的有效快照将保持激活状态。
/progressivestages validate 有助于识别以下问题:
- TOML 解析错误。
- 重复的阶段 ID。
- 缺失的依赖项。
- 多节点依赖循环。
- 传递性不可达的阶段。
- 无效的注册表引用。
- 无效的触发目标。
- 无效的职业 ID。
- 特定集成的配置问题。
这使得本地整合包开发和运行服务器时的实时迭代更加安全。
? Beta 测试与发布准备
ProgressiveStages 3.0 作为项目方被视为稳定的 3.0 版本发布,但大型整合包仍应像对待针对该整合包的 Beta 版一样测试其自身配置。每个整合包都结合了不同的模组、脚本、配方、团队和自动化系统。
推荐的 Beta 测试流程:
- 使用最终的模组列表和数据包运行
/progressivestages validate。
- 在授予阶段之前和之后测试每一个阶段。
- 测试每一个依赖分支和收敛点。
- 测试撤销、死亡丢失、过期、级联、退款和重新授予。
- 测试资源不足、刚好足够和超出资源的购买情况。
- 在至少两名玩家和独立团队的专用服务器上测试。
- 测试重新登录、服务器重启、
/reload 和 /progressivestages reload。
- 测试整合包使用的漏斗、管道、机器、假人、背包和其他自动化设备。
- 测试所有已安装的配方查看器、任务模组、覆盖层和 Curios 槽位。
- 确认没有任何触发器要求在当前阶段所禁止的操作。
建议用于使用 ProgressiveStages 的整合包的发布标签:
| 阶段 |
目的 |
| Internal Alpha(内部 Alpha) |
验证依赖图、文件结构和主要进度路线。 |
| Closed Beta(封闭 Beta) |
发现绕过漏洞、死胡同、多人游戏问题和平衡性问题。 |
| Open Beta(公开 Beta) |
测试真实玩家行为、替代路线、自动化和性能。 |
| Release Candidate(发布候选版) |
冻结阶段 ID 并验证迁移、重启和全整合包兼容性。 |
| Stable(稳定版) |
在所有关键路径和回归案例均通过后才发布。 |
? 性能与多人游戏安全性
- 执行和所有权由服务器权威控制。
- 相关事件会重新检查索引后的触发器,而不是不断扫描每个条件。
- 轮询仅作为基于状态的条件的可配置安全网保留。
- 当未使用时,可选类别具有快速路径。
- 团队、服务器和单人范围是独立存储和评估的。
- 重载和服务器停止时会正确清除运行时状态。
- 阶段变更会将锁定内容、地图状态、实体、方块、流体和配方查看器同步到客户端。
- 购买会在花费任何资源之前验证先决条件、触发要求、冷却时间和资源。
? 要求
- Minecraft 1.21.1。
- NeoForge 21.1 或在声明的 Minecraft 范围内兼容的新版 21.1 构建。
- 无强制要求的任务、团队、脚本、配方查看器、装备或覆盖层模组。
? 安装
- 为 Minecraft 1.21.1 安装 NeoForge。
- 将 ProgressiveStages jar 文件放入客户端和服务器的
mods/ 目录中。
- 安装整合包所需的任何可选集成模组。
- 启动一次以生成主配置和示例阶段文件。
- 创建或编辑
config/progressivestages/stages/ 下的文件。
- 运行
/progressivestages validate。
- 通过
/progressivestages reload 或重启服务器应用更改。
? 文档与支持
❤️ 完整的进度框架
ProgressiveStages 为整合包作者提供了一个单一、高度可定制且对服务器安全的系统,用于构建、强制执行、自动化、奖励、脚本化、展示、测试和演进 virtually 任何类型的 Minecraft 进度体系。
ProgressiveStages 3.0
? Build complete Minecraft progression systems through an in-game editor—then let ProgressiveStages enforce them everywhere.
✨ Create your progression in-game
Run /pstages editor to open the ProgressiveStages editor GUI.
Create, edit, organize, and configure your stages without needing to build every TOML file by hand. Design the progression your pack needs, connect its dependencies, configure its locks and unlock conditions, customize how it looks, and then test it in-game.
ProgressiveStages is not simply an item-locking mod. It is a complete progression-authoring platform that lets modpack creators decide what players can use, where they can travel, what they must accomplish, how progression is shared, what happens when a stage is earned or lost, and how the entire journey is presented in-game.
Every stage is defined in a readable TOML file. A stage can represent almost anything: an age, chapter, skill, class, research topic, quest milestone, boss tier, dimension, technology branch, magic school, server event, temporary blessing, punishment, or purchasable upgrade.
? Build practically any kind of progression
- A simple
Stone Age → Iron Age → Diamond Age progression.
- Several independent technology, exploration, farming, and magic branches.
- A large quest-driven modpack with hundreds of interconnected milestones.
- RPG-style skill trees with costs, prerequisites, attributes, rewards, and refunds.
- Team progression with FTB Teams or world-wide server milestones.
- Secret paths that remain hidden until the player discovers their prerequisites.
- Temporary challenge stages that expire, disappear on death, or require maintained XP.
- Fully scripted progression using KubeJS and the Java API.
ProgressiveStages itself does not require a quest mod, recipe viewer, team mod, scripting mod, or overlay mod. Every integration is optional and activates only when its related mod is installed.
?️ Server authoritative: the server owns stage progress, grants, revocations, dependencies, costs, and enforcement. A modified client cannot give itself stages, fake a purchase, or bypass progression rules.
? What progression can look like
Progression can be linear:
? Stone Age
└── ? Iron Age
└── ? Diamond Age
└── ⚔️ Netherite Age
It can branch into different playstyles and later converge:
? Survival Basics
└── ? Iron Age
├── ⚙️ Engineering ──────┐
│ └── ? Advanced Tech │
├── ? Arcane Studies ───┼──▶ ? Endgame
│ └── ? Master Sorcery│
└── ? Exploration ──────┘
└── ? Outer Realms
Dependencies support all, any, and counted satisfaction. That means an endgame stage can require every branch, any one specialization, or a configurable number of paths.
? Choose a Specialization
├── ⚙️ Technology ─┐
├── ? Magic ──────┼──▶ ? Mastery (complete any 2 paths)
└── ⚔️ Combat ─────┘
Stages may also be completely independent. A server can have a main story tree, optional skill trees, temporary events, and hidden secrets at the same time.
?️ The player progression map
Open the map with /stage, /stages, /ps, /stage gui, or a configurable keybind.
The 3.0 map is modeled after Minecraft's advancement screen while remaining fully controlled by the pack author:
- Familiar vanilla task, goal, and challenge frames.
- A draggable, wheel-scrollable dependency graph.
- Automatic graph layout when coordinates are omitted.
- Exact
x and y placement when a hand-authored layout is preferred.
- Dependency connectors that make branches and convergence easy to understand.
- Hover cards with descriptions, dependencies, trigger progress, and unlock previews.
- Click-to-pin detail panels for longer information.
- Search by name, ID, description, category, or locked item.
- A toggle to hide stages the player already owns.
- Per-stage icons, colors, categories, backgrounds, frames, and sort order.
- Server-validated stage purchases directly from the map.
- Live progress for automatic trigger conditions.
- Unknown icons, concealed names, and spoiler-safe descriptions.
Authors decide when a node becomes visible with [display].reveal:
| Reveal mode |
Behavior |
always |
The stage is always visible. |
dependencies |
The stage appears when its prerequisite path becomes relevant. |
unlocked |
The stage stays concealed until it is owned. |
Set [stage].hidden = true to omit a stage from the map entirely while still using it internally.
Example display configuration:
[stage]
id = "diamond_age"
display_name = "Diamond Age"
description = "Master diamond tools and unlock advanced machinery."
icon = "minecraft:diamond"
color = "#55FFFF"
category = "Main Progression"
tags = ["main", "tier3", "technology"]
[display]
frame = "challenge"
background = "minecraft:block/deepslate_tiles"
reveal = "dependencies"
sort_order = 30
# Optional manual map placement. Omit both for automatic layout.
x = 168
y = 0
The client only displays synchronized data. The server remains authoritative: a modified client cannot grant a stage, bypass a dependency, fake trigger progress, or purchase a stage without paying its validated cost.
? Everything ProgressiveStages can gate
Each category is optional. Global enforcement settings provide pack-wide defaults, while a stage's [enforcement] section can customize how its own locks behave.
? Items and inventories
Gate individual items, tags, entire mods, or ID patterns. Depending on configuration, ProgressiveStages can prevent:
- Using a locked item.
- Picking it up.
- Moving it with the mouse.
- Keeping it in the hotbar or inventory.
- Placing its block form.
- Repairing, renaming, or combining it in an anvil.
- Hiding or obscuring it in recipe viewers.
- Equipping it in supported Curios slots.
Lock overlays render in normal inventories, chests, hotbars, backpacks, anvils, and other slot-based menus.
? Blocks and interactions
Gate block placement, breaking, and right-click interaction. Fine-grained rules can distinguish:
- Right-clicking a block with an empty hand.
- Using a specific item on a specific block.
- Using a specific item on an entity.
- Opening a block menu.
- Opening a held-item menu such as a backpack.
?️ Recipes and crafting
Lock exact recipe IDs or every recipe whose output is a locked item. Enforcement protects both recipe discovery and actual crafting output, so hiding a recipe in JEI or EMI is never the only defense.
? Fluids
Gate fluid pickup, bucket placement, world placement, flow, player submersion, and recipe-viewer visibility.
? Crops and farming
Gate planting, natural growth, bonemeal, harvesting, and crop drops. This allows farming branches where seeds, mature crops, automation, or entire agriculture mods unlock at different times.
? Dimensions and teleportation
Prevent portal travel and command/mod teleportation into locked dimensions. A post-travel safety check catches integrations that bypass normal portal events.
✨ Enchantments
ProgressiveStages can:
- Lock an enchantment completely.
- Keep it out of enchanting, anvils, and trades.
- Remove illegal enchantments from existing gear.
- Cap an enchantment at a temporary maximum level.
When several missing stages cap the same enchantment, the strictest remaining cap wins.
[enchants]
locked = ["minecraft:mending"]
max_levels = [
"minecraft:sharpness:3",
"minecraft:protection:2"
]
⚔️ Entities, combat, and interaction
Gate attacking or interacting with specific entities, registry tags, ID patterns, or entire mods. A combat branch can require one stage to fight undead and another to challenge bosses.
? Mob spawning and replacement
Cancel locked mob spawns or replace them with a different entity. This can keep late-game enemies out of early areas or transform them into a safer substitute until the relevant stage is earned.
? Pets and mounts
Gate taming, breeding, commanding, interacting with, or riding pets and other supported entities.
? Loot
Filter locked content from:
- Chests and generated containers.
- Fishing.
- Archaeology.
- Mob drops.
- Block drops.
- Lootr's per-player loot rolls.
Loot filtering is server-side, preventing players from receiving content simply because it appeared in a generated table.
?️ Screens and menus
Block specific block menus or held-item menus. This is useful when the item itself may be carried but its configuration or storage interface should unlock later.
?? Villagers, trades, and professions
Use [trades] to hide individual offers based on their result, or [professions] to prevent opening an entire profession's trading screen. Wandering traders have no profession and can be managed through trade rules.
? Advancements
Locked advancements can be withheld from the client entirely. They do not merely appear greyed out—they remain hidden until their required stage is owned, then refresh without requiring a relog.
? Structures
Gate entry into structures and independently control:
- Container access.
- Block breaking.
- Block placement.
- Explosions.
- Mob spawning.
Players who breach a locked structure can be returned to their last safe position, with configurable entry padding to keep them away from its boundary.
? Regions
Define hand-authored three-dimensional regions with their own restrictions, messages, rule flags, and debuffs. Regions are useful for server hubs, dungeons, arenas, towns, story locations, or areas not represented by a registered Minecraft structure.
? Curios equipment slots
When Curios is installed, individual slots can require stages. Locked equipment can be ejected and normal item enforcement remains available as a fallback.
⛏️ Ores and encrypted blocks
Locked ore or block IDs can be visually replaced with another block—stone by default—until the player earns the stage. Chunk data, break behavior, and drops are guarded so the visual disguise does not become a bypass.
[blocks]
locked = ["minecraft:diamond_ore", "minecraft:deepslate_diamond_ore"]
[display]
encrypt_blocks = true
encrypt_as = "minecraft:stone"
? Player abilities
Gate movement abilities independently:
[abilities]
locked = ["elytra", "sprint", "swim", "climb"]
? Beacon effects and brewing
Gate individual beacon effects per player and prevent unauthorized players or automation from extracting locked potion outputs from brewing stands.
? Stage-owned attributes
A stage can apply any registered vanilla or modded attribute while owned, including health, scale, attack damage, movement speed, or reach. Modifiers support additive, base-multiplicative, and total-multiplicative operations and are removed when the stage is revoked.
? One matching language across the mod
Lock lists use the same readable syntax in nearly every category:
| Entry |
Meaning |
Example |
id: |
One exact registry ID |
id:minecraft:diamond |
| No prefix |
Shorthand for id: |
minecraft:diamond |
mod: |
An entire mod namespace |
mod:mekanism |
tag: |
A registry tag |
tag:minecraft:logs |
# |
Tag shorthand |
#minecraft:logs |
name: |
Case-insensitive ID substring |
name:netherite |
Broad locks can contain exact carve-outs:
[items]
locked = ["mod:mekanism"]
always_unlocked = ["mekanism:configurator"]
If multiple stages gate the same content, the player must own every applicable stage. A whitelist or [unlocks] entry affects only the stage that declared it; it does not silently override another stage's lock.
⚡ Automatic stage triggers
Triggers live inside the stage they unlock—there is no separate global trigger file.
A stage may have multiple [[triggers]] blocks. Each block is an alternative route to the same stage. Inside a block, use:
mode = "all_of" to require every condition.
mode = "any_of" to require at least one condition.
Built-in trigger conditions cover:
| Family |
Examples |
| Items |
Hold, pick up, use, drop, craft, mine, or break an item/tool. |
| Combat |
Kill entities, kill bosses, kill with a specific item, tame, or breed. |
| Player state |
Level, XP, effects, statistics, play time, sleeping, fishing, or riding. |
| Exploration |
Dimension, biome, time in biome, structure, altitude, distance, and advancements. |
| World state |
Weather, day count, and world time. |
| Progression state |
Hold another stage for a duration. |
| External progress |
Named counters controlled by commands, KubeJS, quests, or another mod. |
| Custom logic |
KubeJS predicates and script-supplied progress. |
Counter-based conditions can be retroactive when backed by vanilla statistics. Event-indexed evaluation means relevant game events recheck only the conditions they may affect, while a configurable polling interval safely handles live state conditions.
? Example: one required route
[[triggers]]
mode = "all_of"
description = "Mine diamonds and complete ten factory quests"
[[triggers.conditions]]
type = "mine"
block = "minecraft:diamond_ore"
count = 3
[[triggers.conditions]]
type = "custom_counter"
counter = "factory_quests"
count = 10
? Example: alternative routes
# Route 1: defeat the dragon.
[[triggers]]
mode = "all_of"
description = "Defeat the Ender Dragon"
[[triggers.conditions]]
type = "kill"
entity = "minecraft:ender_dragon"
count = 1
# Route 2: become a master explorer instead.
[[triggers]]
mode = "all_of"
description = "Visit the End and travel 50,000 blocks"
[[triggers.conditions]]
type = "dimension"
dimension = "minecraft:the_end"
[[triggers.conditions]]
type = "distance"
movement = "all"
count = 50000
Dependencies are always respected by normal trigger grants. Progress may accumulate early, but the stage cannot auto-grant until its prerequisite rules are satisfied.
? Dependencies, scopes, tags, and categories
Stages support:
- Linear, branching, converging, circularly validated, or independent graphs.
all, any, and counted dependency requirements.
- Team-scoped ownership for solo play or FTB Teams.
- Server-scoped ownership for world-wide milestones.
- Categories for organization and presentation.
- Tags for queries and bulk operations.
- Hidden internal stages.
- Starting stages.
Example server-wide event:
[stage]
id = "dragon_defeated"
display_name = "The Dragon Has Fallen"
description = "The first victory unlocks the End Age for the entire server."
scope = "server"
tags = ["story", "server_event"]
⏳ Stages can be temporary or lost
Progression does not have to be permanent.
[stage].duration = "30m" creates a temporary stage that expires after real time, including time spent offline.
[revoke].on_death = true removes it when the player dies.
[revoke].xp_below = N keeps it only while total XP remains above a threshold.
[revoke].cascade = true also removes stages that depend on it.
[stage]
id = "berserker_blessing"
display_name = "Berserker's Blessing"
duration = "30m"
[revoke]
on_death = true
cascade = true
This supports timed events, temporary classes, challenge runs, maintained qualifications, curses, blessings, and true regression systems.
? Purchasable skill-tree nodes
A [cost] table turns a stage into a purchasable map node.
[cost]
xp_levels = 30
items = ["minecraft:diamond:5", "minecraft:emerald:3"]
bypass_requirements = false
cooldown = "5m"
refund_percent = 50
- Dependencies are still enforced.
bypass_requirements = true skips trigger requirements, not prerequisite stages.
- Cooldowns are tracked per player.
- Refunds can return a percentage of item and XP cost when a purchased stage is revoked.
- Every purchase is revalidated by the server before any cost is removed.
This makes ProgressiveStages suitable for RPG skills, research systems, prestige trees, class upgrades, and server shops without requiring a separate GUI mod.
? Rewards and unlock presentation
[rewards] controls what the player receives on a real grant:
[rewards]
items = ["minecraft:diamond:5", "minecraft:netherite_scrap:2"]
effects = ["minecraft:strength:120:1", "minecraft:regeneration:60:0"]
commands = [
"give {player} minecraft:cake 1",
"say {player} has entered the Diamond Age!"
]
teleport = "minecraft:the_nether 0 70 0"
xp_levels = 5
xp_points = 100
Rewards run once for each real ownership change, not on login or synchronization. Team progression rewards the player who actually earned or purchased the stage rather than duplicating rewards to every team member.
[unlock] controls the moment-to-moment presentation:
[unlock]
toast = "Diamond Age reached!"
title = "&b&lDIAMOND AGE"
subtitle = "&7A new era begins"
sound = "minecraft:ui.toast.challenge_complete"
particle = "minecraft:totem_of_undying"
progress_nudges = true
hud_bar = true
Every effect is optional. A pack can use a quiet background stage, a dramatic story milestone, or anything between them.
? A complete starter stage example
[stage]
id = "iron_age"
display_name = "Iron Age"
description = "Smelt iron to unlock iron tools, machinery, and the next technology tier."
icon = "minecraft:iron_ingot"
dependency = ["stone_age"]
category = "Main Progression"
tags = ["main", "technology", "tier2"]
color = "#D8D8D8"
scope = "team"
[display]
frame = "goal"
reveal = "dependencies"
sort_order = 20
show_tooltip = true
show_description_on_tooltip = true
[items]
locked = [
"minecraft:iron_pickaxe",
"minecraft:iron_axe",
"minecraft:iron_shovel",
"minecraft:iron_sword",
"minecraft:iron_helmet",
"minecraft:iron_chestplate",
"minecraft:iron_leggings",
"minecraft:iron_boots"
]
[blocks]
locked = ["minecraft:anvil", "minecraft:blast_furnace"]
[recipes]
locked_outputs = ["tag:minecraft:iron_tool_materials"]
[[triggers]]
mode = "all_of"
description = "Smelt your first iron ingot"
[[triggers.conditions]]
type = "advancement"
advancement = "minecraft:story/smelt_iron"
[rewards]
items = ["minecraft:iron_ingot:3"]
xp_points = 25
[unlock]
toast = "The Iron Age begins!"
sound = "minecraft:ui.toast.challenge_complete"
particle = "minecraft:happy_villager"
Important design rule: do not lock the action required to earn its own stage. If mining diamond ore unlocks Diamond Age, players must still be able to mine the ore before owning Diamond Age; lock the useful diamond equipment and advanced content instead.
⌨️ Commands
? Player and inspection commands
/stage or /stage gui — open the progression map.
/stage list — list owned or available stages.
/stage check — check ownership.
/stage info — inspect a stage definition.
/stage tree — inspect dependency relationships.
/stage progress next — show progress toward reachable stages.
/stage progress all — show all visible progress.
/stage progress <stage> — inspect one stage's conditions.
/stage simulate — dry-run reachable stages and dependency blockers.
?️ Administration and pack-author commands
/pstages editor — open the in-game stage editor GUI.
/stage grant and /stage revoke.
/stage tag grant, revoke, and list.
/stage category grant, revoke, and list.
/stage bulk grant and revoke.
/stage counter get, add, set, and reset.
/stage sync to refresh a player's client state.
/stage new <id> to scaffold a new TOML stage.
/stage export to generate a Markdown progression guide.
/progressivestages reload for a validated live reload.
/progressivestages validate for parsing, registry, graph, and trigger diagnostics.
/progressivestages ftb status for FTB Quests diagnostics.
Command suggestions are generated from loaded stage IDs, tags, categories, players, and counter names where applicable.
? KubeJS scripting
When KubeJS is installed, server scripts receive a global ProgressiveStages object and players receive the first-class player.stages bridge.
ProgressiveStages.has(player, 'diamond_age')
ProgressiveStages.grant(player, 'diamond_age')
ProgressiveStages.revoke(player, 'diamond_age')
ProgressiveStages.toggle(player, 'diamond_age')
ProgressiveStages.available(player, 'diamond_age')
ProgressiveStages.percent(player, 'diamond_age')
ProgressiveStages.progress(player, 'diamond_age')
ProgressiveStages.addCounter(player, 'factory_quests', 1)
ProgressiveStages.openGui(player)
The API also supports:
- Grant and revoke callbacks that fire for real engine changes.
- Custom boolean trigger conditions.
- Custom progress providers.
- Named counters.
- Immediate trigger evaluation.
- Dependency and dependent queries.
- Tag and category queries.
- Bulk grants and revocations.
- Definition snapshots.
- Synchronization.
Grant and revoke calls return whether ownership actually changed; bulk operations return how many stages changed.
Example custom condition:
ProgressiveStages.condition('is_rich', player => {
return player.inventory.count('minecraft:diamond') >= 64
})
[[triggers]]
mode = "all_of"
[[triggers.conditions]]
type = "script"
id = "is_rich"
☕ Java API
ProgressiveStagesAPI exposes ownership, definitions, dependencies, trigger progress, counters, bulk mutations, and synchronization to other mods. NeoForge events report real grants and revocations together with their causes, including commands, triggers, purchases, integrations, and regression.
Optional integrations are separated behind compatibility layers and guarded mixins, so the core mod does not require optional classes to load.
? Optional integrations
| Integration |
What ProgressiveStages adds |
| EMI |
Hide locked entries, add overlays/tooltips, and refresh immediately after stage changes. |
| JEI |
Hide locked items/recipes and restore them immediately on unlock. |
| FTB Teams |
Share team-scoped stages while retaining a solo fallback. |
| FTB Quests + FTB Library |
Required-stage fields, stage tasks, rewards, and live rechecks. |
| KubeJS |
Global scripting API, player.stages, callbacks, custom conditions, and counters. |
| Jade |
Show the required stage while looking at a locked block or entity. |
| WTHIT |
Show the required stage while looking at a locked block or entity. |
| Curios |
Gate equipment slots and eject locked equipment. |
| Lootr |
Filter each player's independent loot rolls. |
| Mekanism |
Handle NBT-heavy variants, chemicals, and relevant automation surfaces. |
| Nature's Compass |
Prevent searches that would bypass locked-dimension progression. |
| Create |
Preserve correct classification for Create-driven interactions and harvesting paths. |
| Visual Workbench |
Preserve block and crafting enforcement through replaced workbench behavior. |
All integrations are optional unless the pack uses the corresponding feature.
? Configuration layout
After the first launch:
config/
└── progressivestages/
├── progressivestages.toml
└── stages/
├── stone_age.toml
├── iron_age.toml
└── diamond_age.toml
progressivestages.toml contains global defaults, enforcement and performance settings, integration switches, disclosure settings, visual behavior, and customizable messages.
stages/ contains the individual stage TOML files.
- Nested folders are supported for organizing large packs.
- The generated
diamond_age.toml is a heavily commented reference covering the complete schema.
- Datapacks may provide defaults at
data/<namespace>/progressivestages/stages/*.toml.
- A config-folder stage with the same ID overrides the datapack version.
- Older layouts can be migrated without overwriting an existing 3.0 target.
✅ Safe reloads and validation
/progressivestages reload does not partially apply broken data. It builds and validates a complete candidate snapshot first. If parsing fails, a stage ID is duplicated, the dependency graph is invalid, a registry reference is dead, or runtime application fails, the previous working snapshot remains active.
/progressivestages validate helps identify:
- TOML parsing errors.
- Duplicate stage IDs.
- Missing dependencies.
- Multi-node dependency cycles.
- Transitively unreachable stages.
- Invalid registry references.
- Dead trigger targets.
- Invalid profession IDs.
- Integration-specific configuration problems.
This makes live iteration much safer for both local pack development and running servers.
? Beta testing and release readiness
ProgressiveStages 3.0 is presented by the project as the stable 3.0 release, but large modpacks should still test their own configuration as if it were a pack-specific beta. Every pack combines different mods, scripts, recipes, teams, and automation systems.
Recommended beta pass:
- Run
/progressivestages validate with the final mod list and datapacks.
- Test every stage before and after grant.
- Test every dependency branch and convergence point.
- Test revocation, death loss, expiration, cascade, refunds, and re-grants.
- Test purchases with insufficient, exact, and excessive resources.
- Test a dedicated server with at least two players and separate teams.
- Test relogging, server restart,
/reload, and /progressivestages reload.
- Test hoppers, pipes, machines, fake players, backpacks, and other automation used by the pack.
- Test all installed recipe viewers, quest mods, overlays, and Curios slots.
- Confirm that no trigger requires an action the same stage prevents.
Suggested release labels for a modpack using ProgressiveStages:
| Phase |
Purpose |
| Internal Alpha |
Validate the graph, file structure, and main progression route. |
| Closed Beta |
Find bypasses, dead ends, multiplayer issues, and balance problems. |
| Open Beta |
Test real player behavior, alternative routes, automation, and performance. |
| Release Candidate |
Freeze stage IDs and verify migration, restart, and full-pack compatibility. |
| Stable |
Ship only after every critical path and regression case passes. |
? Performance and multiplayer safety
- Enforcement and ownership are server-authoritative.
- Relevant events recheck indexed triggers rather than scanning every condition constantly.
- Polling is reserved as a configurable safety net for state-based conditions.
- Optional categories have fast paths when unused.
- Team, server, and solo scopes are stored and evaluated independently.
- Runtime state is cleared correctly on reload and server stop.
- Stage changes synchronize locked content, map state, entities, blocks, fluids, and recipe viewers to clients.
- Purchases validate prerequisites, trigger requirements, cooldowns, and resources before spending anything.
? Requirements
- Minecraft 1.21.1.
- NeoForge 21.1 or a compatible newer 21.1 build within the declared Minecraft range.
- No mandatory quest, team, scripting, recipe-viewer, equipment, or overlay mod.
? Installation
- Install NeoForge for Minecraft 1.21.1.
- Place the ProgressiveStages jar in
mods/ on the client and server.
- Install any optional integrations your pack needs.
- Launch once to generate the main configuration and example stages.
- Create or edit files under
config/progressivestages/stages/.
- Run
/progressivestages validate.
- Apply changes with
/progressivestages reload or restart the server.
? Documentation and support
❤️ The complete progression framework
ProgressiveStages gives modpack authors a single, deeply customizable, server-safe system for building, enforcing, automating, rewarding, scripting, displaying, testing, and evolving virtually any kind of Minecraft progression.
评论 0
登录后参与评分
还没有评论,来抢沙发吧