Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 6 hours ago
All versions
5.0.0-rc.6
Beta
AutoModpack 5.0.0-rc.6yesterday 1,998
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.10–1.21.11
1.21.4–1.21.8
1.21–1.21.1
1.20–1.20.1
1.19–1.19.2
1.18.x
Platforms
Fabric
Forge
NeoForge
Supported environments
Client and server
Changes
What's Changed
Security
- The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background.
- Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically.
- The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning.
- The server no longer replaces its TLS key and certificate when one of them is missing. If
cert.crtexists withoutkey.pem, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk.
In-game updates
- Updates, switches and removals made in-game now always apply right away on best effort basis. Files the game holds open (common on Windows) are finished after the game exits or on the next launch.
- Several changes in one session now stack properly. Each starts where the previous one left off, so the next launch always ends up on the latest one.
- Fixed updates getting stuck on a file that was already deleted.
- A Minecraft or loader version switch is now written to the launcher together with the files of its update, so the launcher never starts versions the installed mods weren't made for.
- If an update's files stay held through two restarts, AutoModpack stops asking and loads what's installed, trying again every launch. From the third launch like that, an in-game message tells you the update is still unfinished.
Other changes
- Fixed a crash with Sinytra Connector and mixin-booster in the same pack on Forge/NeoForge. Early-service mods that run in place now get each other's names and their own launch options the way ModLauncher gives them, so mixin-booster stands down for Connector like it does in
mods/. If one of them fails to load, the crash now names it. - The update helper and the restart window now run in a separate JVM.
- Faster boots and update checks on large packs.
- Quieter console logs.
Full Changelog: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.5...v5.0.0-rc.6
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:Iwx6SFt5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k68glP2e:Iwx6SFt5"
}

