Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 hours ago
All versions
mc1.21.1-1.2.0
Release
BRNTalk 1.2.03 weeks ago 17
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
中文
新增
- 校验报告内部改为结构化记录,日志现在会输出资源、剧本、消息和选项定位,便于作者回到脚本排查。
- 新增非阻断式校验警告,覆盖空白消息/选项文本、无法恢复的
wait节点,以及无法从起始消息到达的消息节点。
变更
/reload后的管理员游戏内提示保持为简短摘要,详细校验信息改由latest.log承载。/reload校验摘要和旧存档迁移提示改用翻译键,内置简体中文与英文文本。- 运行时
action命令失败、返回 0 或自动推进触发安全上限时,现在会写入包含剧本、线程和消息定位的日志。 - 补充
BrntalkAPI与PlayerSeenMessageEvent的稳定边界和事件触发语义文档。
外部工具
- 新增规则级校验 fixture,覆盖所有当前阻断式错误和非阻断式警告。
- 新增
tools/debug/run-validation-fixtures.ps1,可通过 RCON 批量注入 fixture、执行reload并检查日志判定。 - 更新
docs/EXTERNAL_VALIDATION_PLAN.md,改为记录当前 fixture、RCON smoke 和批量校验工作流。
修复
- [1.20.1] 修复 Forge 专用服务端在 common setup 注册客户端网络包处理器时误加载客户端 UI 类,导致服务端启动崩溃的问题。
English
Added
- Validation reports now keep structured issue data, and logs include resource, script, message, and choice locations for author debugging.
- Added non-blocking validation warnings for blank message/choice text, non-resumable
waitnodes, and messages unreachable from the start node.
Changed
- After
/reload, the in-game admin validation message stays as a short summary while detailed validation information is written tolatest.log. /reloadvalidation summaries and legacy data migration messages now use translation keys with built-in Simplified Chinese and English text.- Runtime logs now include script, thread, and message locations when an
actioncommand fails, returns 0, or automatic progression reaches the safety limit. - Documented the stable boundaries and event semantics for
BrntalkAPIandPlayerSeenMessageEvent.
External Tooling
- Added rule-level validation fixtures for every current blocking error and non-blocking warning.
- Added
tools/debug/run-validation-fixtures.ps1to inject fixtures, runreload, and verify logs in batches through RCON. - Updated
docs/EXTERNAL_VALIDATION_PLAN.mdto describe the current fixture, RCON smoke, and batch validation workflow.
Fixed
- [1.20.1] Fixed a Forge dedicated-server crash caused by client packet handler registration loading client UI classes during common setup.
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:Pc62JolS:sBjzGpSn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Pc62JolS:sBjzGpSn"
}


