Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
- Use PacketEvents API instead of VPacketEvents by @MemencioPerez in https://github.com/MemencioPerez/UnSignedVelocity/pull/14
- chore(deps): update dependency xyz.jpenilla.run-velocity to v2.3.1 by @renovate in https://github.com/MemencioPerez/UnSignedVelocity/pull/16
- chore(deps): update actions/checkout digest to eef6144 - autoclosed by @renovate in https://github.com/MemencioPerez/UnSignedVelocity/pull/15
Full Changelog: https://github.com/MemencioPerez/UnSignedVelocity/compare/1.4.3...2.0.0
Note: If you are coming from UnSignedVelocity 1.x.x, it is recommended to delete the old configuration file and let the updated plugin regenerate it, as many new features have been added.
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:yTTknbVs:g39MJWp6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yTTknbVs:g39MJWp6"
}

