Tags
Creators
Details
0.7.1
Compatibility
Changes
0.7.1 Update
This update is a minor release, and it only contains one new feature (custom script events) as well some minor bug fixes and code improvements.
The bigger news with this update is that the new documentation site is live! Check it out here.
Additions:
- Added a
CustomEventthat an be created and called by scripts to signal a custom event to other scripts/plugins (visit the docs for more information) - Added another example script
Changes:
- Updated all dependencies to latest versions (including Jython to 2.7.4)
- Minor code improvements/cleanup
- Minor improvements to config file comments and JavaDocs
Bug Fixes:
- Fixed an issue with log messages not being printed correctly when running regular Spigot server software
- Fixed an issue with the library manager attempting to load non-JAR files and folders
See the complete change log here.
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:G91y7RYh:GniYJCSH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G91y7RYh:GniYJCSH"
}

