Links
Tags
Creators
Details
1.2.1
Compatibility
Changes
What's Changed
-
Fixed an issue where regions were still not visible even when the client's debug option to display all regions was enabled.
-
Fixed an issue where track initialization would fail if the chunk was not loaded.
-
Fixed an issue where stopping a specific track would fail if the chunk was not loaded. (If this still occurs, use the command
/kill @e[type=speed_uuuuuuup:region_marker]to remove the marker). -
Fixed an issue where entities used for marking points were incorrectly removed after a chunk was unloaded.
-
修复了客户端打开显示所有区域的调试选项时,依然无法看到区域的问题。
-
修复了当区块未加载时,初始化赛道不成功的问题。
-
修复了当区块未加载时,停止指定赛道不成功的问题。(若仍有此情况,使用指令
/kill @e[type=speed_uuuuuuup:region_marker]即可移除) -
修复了区块卸载之后,用于标记点位的实体被异常移除的问题。
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:tx7ZR2Oe:qajWQCck"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tx7ZR2Oe:qajWQCck"
}

