Tags
Creators
Details
0.1.0
Compatibility
Required content
Changes
Superseded by 0.1.1. 0.1.0 can fail to start its TLS host on some servers. Please use 0.1.1.
First release. Unofficial add-on that lets Paper servers work with AutoModpack clients.
Requirements: Paper 26.2, Java 25, packetevents 2.13.0, AutoModpack 4.0.x on the client. Tested with AutoModpack 4.0.6 (Fabric). NeoForge/Forge and a real Geyser join are untested.
Features
- Hosts your mods/configs/resource packs for AutoModpack clients on a dedicated TCP port (default 30037, TLS 1.3)
- Login handshake through packetevents; players use the stock AutoModpack mod
/automodpack4paper(/am4p): status, generate, reload, fingerprint, regenerate-cert- Safe-file scan before every publish (no symlinks, no executables,
.jaronly inmods/) - Optional CA-signed certificate so players get no trust prompt
- Bedrock (Geyser/Floodgate) players are skipped
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:n712yfct"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3bzuRXr6:n712yfct"
}

