Links
Tags
Creators
Details
1.2.5
Compatibility
Changes
Major stability, performance, and configuration update.
Changes include:
Improved beacon effect performance and entity scanning Added configurable scan limits for advanced effects Optimized particle and visual beam safety checks Expanded language system integration for GUI and item texts Reduced hardcoded menu and item values Improved GUI configurability through gui.yml Added safer scheduler handling for Paper/Spigot environments Fixed YAML storage duplication and beam-style persistence issues Improved custom item metadata handling Added shaded SQL dependencies for standalone deployment General cleanup, optimization, and internal refactoring
Focused on:
Better TPS stability Safer runtime behavior Increased customization Improved long-term maintainability Better compatibility with modern 1.21+ servers
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:ZTqaLGH5:BlSmV33h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZTqaLGH5:BlSmV33h"
}

