Links
Creators
Details
3.0.2
Compatibility
Changes
This is a bugfix for Kappa:
- Fixed a crash that would happen when a server had too many players with the same name at the same time.
- Use the HTTPS server at
optifine.netwhen available. If that is unavailable, the original HTTP server ats.optifine.netserver will be used in case of outages.
This version was compiled against 21w37a for Java 16 and has been tested to work successfully with:
- 1.18.1
- 1.18.2 Snapshots: 22w03a, 22w05a, 22w06a, 22w07a
- 1.18.2 Pre-releases and Release Candidates: 1.18.2-pre1, 1.18.2-pre1, 1.18.2-pre3, 1.18.2-rc1
- 1.18.2
- 1.19 Snapshots: Deep Dark Experimental Snapshot 1, 22w11a, 22w12a, 22w13a, 22w14a, 22w15a
- April's Fools Snapshots: 22w13oneBlockAtATime
Additionally, the changes in this release do not touch Minecraft exclusive things, meaning that, theoretically, this release should be binary compatible with every Minecraft version that Kappa v3.0.1 is compatible with.
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:2wsNAbi3:u2AvkHZp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2wsNAbi3:u2AvkHZp"
}
