Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 2 weeks ago
All versions
5.0.0-rc.5
Beta
AutoModpack 5.0.0-rc.52 weeks ago 2,382
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
- Improved
auto-exclude-server-side-modsbehavior, it now excludes only dedicated server mods, server mods that may run on client are shipped by default, it will no longer end up excluding mods that potentially clients might need to have in order to connect to the server. To exclude more, useexcludelist. - Added
/automodpack generate replace-notes [text...]to caption the live generation without publishing a new one. Without text it readsautomodpack/host-modpack/patch-notes.mdand clears the file after a successful replace. - [Windows] Fixed update apply stalling when a managed file stays locked or an empty directory cannot be removed.
- [Windows] Locked files are now recognized by error type, so the update helper behaves the same on non-English locale.
- Fixed resumable downloads losing stream alignment when the server answers with a whole file instead of the requested range.
- Fixed a download that finished without every slice on disk, and a served object whose length does not match what the client expected.
- A mod that cannot be mounted as a zip is treated as unreadable instead of aborting the scan.
- Fixed client storage maintenance counting history objects that were never fetched as missing.
- Filesystems that cannot make a file read-only no longer fail the protection step. AutoModpack probes the filesystem once and skips enforcement there.
- Fixed couple UI bugs like modpack '🎵' button breaking after visiting sub-menu or input screen exiting after button press with some mods.
- A failing command worker no longer crashes the server, and command replies are sent on the server thread.
Full Changelog: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.4...v5.0.0-rc.5
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:8zGbAZKm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k68glP2e:8zGbAZKm"
}

