Links
Tags
Creators
Details
Forge-1.20.1-2.4.14
Compatibility
Changes
Fixed: server system prompts are no longer claimed as player messages. The EasyBot colon shape ([label] nick: content) only exact-matched its label, so [玩家系统] 请使用以下命令登录: /log <密码> became a bubble sent by 「请使用以下命令登录」; system-domain labels (containing 系统/公告/服务器/广播/提示/通知 or ending in 插件/助手) and /-prefixed command content are now rejected, while the angle-bracket shape is unchanged. Blank-sender chat and disguised packets are no longer claimed as nameless bubbles either, and the pre-name separator guard no longer misfires on separators inside balanced decorations: [Lv.10|VIP] Steve: hello, 【Lv.10|VIP】Steve » hello and [世界] [Lv.10|VIP] Steve: hello parse again, while 系统>>Steve, VIP|Steve and [系统|公告]Steve stay rejected. Server-declared exact templates now also apply to senderless disguised lines, and template logs carry a System/Disguised source tag.
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:onBSJreQ:sOujhC36"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:onBSJreQ:sOujhC36"
}

