Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 3 days ago
All versions
5.0.0-rc.3
Beta
AutoModpack 5.0.0-rc.32 weeks ago 1,992
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
- Replaced
modpack.<category>.<id>.requiredandmodpack.<category>.<id>.default-selectedbooleans with a singlemodpack.<category>.<id>.selectionenum, takingREQUIRED,RECOMMENDEDorOPTIONAL - The
auto-exclude-server-side-modsoption now takes to account results from Modrinth and CurseForge APIs when we cannot make a decision based solely on the included mod metadata - Improved UI elements to look more readable on wider range of high contrast resourcepacks
- Improved download source selection algorithm, to measure all available download paths for each file and use the best available while always prioritizing Modrinth or CurseForge
- Custom waiting music is now previewable in the modpack screen
- Fixed an loader edge case with some connector mods
- Fixed not properly recognizing mods containing ImmediateWindowProvider service to force-copy on neo/forge
- Shortened generated-copies file location to avoid hitting default windows publishable path limit
- Improved Minecraft version detection on startup to work on more non standard environments
- Fixed couple edge cases related to instance timeline
Full Changelog: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.2...v5.0.0-rc.3
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:oj8KYjbo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k68glP2e:oj8KYjbo"
}

