Links
Tags
Creators
Details
1.7.0
Compatibility
Required content
Changes
1.7.0
中文
- 新增“潘多拉之祝”进度分页,成功转化七个诅咒可分别解锁对应祝福进度。进度界面、解锁提示和聊天公告中的名称带有烫金彩虹流光与轻微上下浮动,描述同步美化。
- 第一、第五诅咒改为击杀凋零、坚守者后概率反转:默认初始 20%,失败后增加 10 个百分点,最高 100%;目标和概率均可配置,取消原药水效果及手持物品要求。
- 反转说明实时显示当前概率;第一、第五诅咒的失败进度分别保存,卸下、死亡和重登后保留,成功后重置。
- 修复祝福额外饰品栏位反复刷新、饰品闪烁及无法放入的问题;栏位随佩戴增减,兼容旧存档,并补齐第六祝福的 3 个护符栏位。
- 修复第二诅咒的旧下落记录在死亡、退出或跨维度后残留,导致后续错误转化的问题。
适用 Minecraft 1.20.1 / Forge。联机时客户端与服务端需同步更新至 1.7.0。必装潘多拉之咒 2.4.26+、Curios 5.4.5+;若安装 JEI,需 15.20.0.106 或更新版本。
English
- Added a Blessing of Pandora advancement tab, with an advancement for converting each of the seven curses. Titles shimmer with a gilded rainbow and gently float in the advancement screen, unlock popups and chat announcements; descriptions have also been restyled.
- The First and Fifth Curses now reverse after killing a Wither or Warden: a 20% starting chance, increasing by 10 percentage points after each failure, up to 100%. Targets and chances are configurable; previous status-effect and held-item requirements are removed.
- Reversal guides show your current chance. Failure progress for the First and Fifth Curses is saved separately, survives unequipping, death and relogging, and resets after conversion.
- Fixed repeated refreshes of blessing-granted Curios slots, flickering accessories and items refusing to enter slots. Slots now follow equipped blessings, support existing saves, and correctly include Requiem's three charm slots.
- Fixed stale Second Curse fall records after death, logout or dimension changes that could cause an incorrect later conversion.
For Minecraft 1.20.1 / Forge. Update both client and server to 1.7.0 for multiplayer. Requires Curse of Pandora 2.4.26+ and Curios 5.4.5+. JEI is optional; if installed, use 15.20.0.106 or newer.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:1Zd4JFKt:V0vFBe5X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1Zd4JFKt:V0vFBe5X"
}

