Tags
Creators
Details
7.1.4
Compatibility
Changes
Yeah, this version is literally just silencing that warning that tells you you're using an unsupported server version when on 1.21. Yeah, 7.1.3 works on 1.21.
That being said though, speaking of versions, HeadsPlus' current build system causes issues for testing, version updating and also CI/CD. Because of this, I'll be looking to change this build system to what its sister plugin, AdvancedTeleport, uses in v6. However, a consequence of that will be losing 1.15.2-1.17.1 support. This probably won't apply next update, but probably in the near future - after that point, it should be easier for me to maintain and work on the plugin, so it doesn't look like AT is my favourite child. Tchau.
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:5BNpeqz1:ELnjxKhr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5BNpeqz1:ELnjxKhr"
}
