Links
Tags
Creators
Details
1.9.0.2
Compatibility
Changes
新增功能 / New Features
-
结构列表、预览与子结构步骤:新增结构选择器与实时预览组件,
show_structure/show_extra_structure可直接浏览本地结构文件,并将额外结构作为子结构插入场景。 Added a structure picker with live previews, and expandedshow_structureworkflows withshow_extra_structureso local structure files can be browsed and inserted as sub-structures in scenes. -
NBT 扩展编辑器:新增可展开的大型 NBT 文本编辑器,支持路径 / 坐标识别、多行输入增强,以及方块实体、实体、掉落物等步骤的 NBT 编辑与选取流程。 Added an expanded NBT editor with path/coordinate detection, improved multi-line editing, and better NBT edit/pick flows for block entities, entities, and item entities.
-
文本轨道与进度条:新增场景文本列表与文本标记指令,支持在 Ponder 播放过程中展示进度条、同步文本步骤,并改进共享文本的悬浮定位。 Added a scene text list and marker instructions for progress bars and synchronized text playback, while also improving floating shared-text positioning.
-
高级动画与界面回放:扩展
show_interface的客户端截图 / 回放能力,并为区段、实体、掉落物等步骤补充外部动画与更细致的移动动画配置。 Expandedshow_interfacewith client-side screen capture/replay, and added richer movement/external animation controls for sections, entities, and item entities.
改进 / Improvements
-
导出与脚本生成优化:重构 Java 导出模板与运行时支持代码,改进结构引用、导出结果反馈与清单生成,为复杂场景导出提供更稳定的产物。 Reworked Java export templates and runtime support generation, improving structure references, export feedback, and manifest output for more reliable complex-scene exports.
-
编辑器交互与缩放适配:新增 UI 缩放支持,优化长文本输入框、结构预览、旋转相机和多处步骤表单细节,提升大场景编辑体验。 Added dedicated UI scaling support and refined long text inputs, structure previews, rotate-camera controls, and multiple step forms for better large-scene editing.
修复 / Fixes
- 场景运行兼容性修复:修复合并区段后
hide_section清理错误、Ponder 原生界面层级 / 文本索引问题,以及若干 NBT 选取与边界框相关回归。 Fixed merged-sectionhide_sectioncleanup, vanilla Ponder UI layering/text-index issues, and several regressions around NBT picking and scene bounds.
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:voXQB5Hr:gNCG8F9T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:voXQB5Hr:gNCG8F9T"
}

