Tags
Creators
Details
4.0.0-beta25
Compatibility
Changes
New March, new AutoModpack release, brought to you by Yours Truly. This update is more significant than previous ones, so you might want to read these patch notes.
Changes
- Replaced plain text HTTP hosting with a custom simple TCP protocol, encrypted using TLS 1.3, for enhanced security.
- All files are now sent compressed using the zstd algorithm, which should result in a significant reduction in bandwidth usage, those with slower internet connections or larger modpacks can expect their downloads speeds to accelerate. (This doesn't change anything for files downloaded directly from modrinth or curseforge)
- Modpack access is now authorized using secrets, ensuring that only whitelisted players can download the server modpack. Secrets are generated upon each player's join and previous secrets are then immediately invalidated #324.
Config
- A new
secretLifetimefield has been added, which determines the time in hours that a player's secret remains valid. By default, this is set to 336 hours (14 days). - The
validateSecretsboolean field has been introduced, allowing modpack host to validate who is attempting to download the modpack.
Commands
- The /
automodpack host connectionscommand has been added, enabling operators to monitor in real-time who is currently downloading the server modpack.
Bug fixes
- Edge cases that caused modpack download freezes have been resolved #319.
- The issue with fabric nested mods being copied too often, also known as the "owo-sentiel bug", has been finally properly fixed.
- Fixed some forge mods not being detected as mods and thus incorrectly being copied to
/mods/folder #250. - Encoding fixes, non-standard characters in filenames should not longer cause any issues.
- Modpacks will no longer download upon restart if the download was previously cancelled in game #328.
Full Changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta24...v4.0.0-beta25
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:k68glP2e:gDHIN6rG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k68glP2e:gDHIN6rG"
}

