Links
Tags
Creators
Details
1.0.1
Compatibility
Changes
From now on, each cannon will be able to customize its own parameter values. The values in config.yml are only for mapping when creating a new default cannon.
Two new commands will be added to support the new feature.
Add /cannon set <cannon> <parameter> <value> - Set a parameter for a cannon Add /cannon info <cannon> - Show info for a cannon
These two commands will be updated to use actual cannons rather than creating virtual ones based on config values.
Modify /cannon fire <cannon> Modify /cannon target <cannon> <x> <y> <z>
Added the update-notify: true option to config.yml to notify admins and the console when a new version is released.
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:sx0zgaef:OcyndeLP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sx0zgaef:OcyndeLP"
}

