Tags
Creators
Details
2.5.2-SNAPSHOT+23
Compatibility
Changes
GH-414 feat: add spear with lunge cooldown (#414)
- add spear cooldown and lunge support based on new api handling without building against it due to support for older versions
Signed-off-by: Michał Wojtas wojtas.michal90@gmail.com
- Resolve AI review. Add gif to readme
Signed-off-by: Michał Wojtas wojtas.michal90@gmail.com
- Optimise SpearLungeController
Signed-off-by: Michał Wojtas wojtas.michal90@gmail.com
- Update eternalcombat-plugin/src/main/java/com/eternalcode/combat/fight/spear/SpearLungeController.java
Co-authored-by: Jakub Kędziora 77227023+Jakubk15@users.noreply.github.com
- Update eternalcombat-api/src/main/java/com/eternalcode/combat/fight/spear/SpearService.java
Co-authored-by: Jakub Kędziora 77227023+Jakubk15@users.noreply.github.com
Signed-off-by: Michał Wojtas wojtas.michal90@gmail.com Co-authored-by: Jakub Kędziora 77227023+Jakubk15@users.noreply.github.com
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:L6sT3a3b:CAj06pAC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L6sT3a3b:CAj06pAC"
}

