Tags
Creators
Details
0.1.1
Compatibility
Required content
Changes
Fixes from real-server testing of 0.1.0. Upgrade recommended: 0.1.0 can fail to start its TLS host on some servers.
- Fixed the TLS key crash (
NoClassDefFoundError: org/bouncycastle/openssl/PEMParser) - Clear log messages when a client cannot use the modpack host
- New
login.on-host-error: kick|allow; players are always let in whenrequireAutoModpackOnClientis false disableInternalTLS: trueis refused unlesstls.external-termination: trueis set- Fingerprint is shown only when TLS is on
- Smaller jar (8.9 MB)
Requirements unchanged: Paper 26.2, Java 25, packetevents 2.13.0, AutoModpack 4.0.x.
Not affiliated with AutoModpack or its author.
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:3bzuRXr6:4KiejMlC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3bzuRXr6:4KiejMlC"
}

