Tags
Creators
Details
1.1.0
Compatibility
Changes
Added a new config option to specify how many points to draw each cycle, allowing you to make traces that reach their target within a single tick if you wish. Can be set to 0 or -1 to draw as many points as needed to reach the target within the first tick, but don't do that in production! Particle effects and sounds are not thread-safe, so the tracing logic has to be run on your main server thread, freezing your entire server if too many points are drawn in one tick.
Fixed UpdateChecker not notifying the console when a new update is available.
Adjusted a few config descriptions and added a hint that makes sure you know the reload command exists.
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:81eeEpc1:OTyHXwqX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:81eeEpc1:OTyHXwqX"
}

