Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
All versions
4.0.0-beta1
Beta
AutoModpack 4.0.0-beta1 fabric2 years ago 6,118
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Changes
- Support for minecraft 1.20.2/4!
- Modpack now updates as soon as possible making updates almost completely seamless!
- Separate window popups are gone!
- Re-written modpack hosting to netty.
- AutoModpack doesn't require new separate port anymore, by default it injects into minecraft network IO (configurable)
- Downloads should be faster and should be less resource intensive.
- Reduced a lot requests to Modrinth and CurseForge API's.
- Modpack generation should be faster.
- Switched from Preloading Tricks to our own implementation due to requiring more invasive code.
- Switched from fabric-networking-api-v1 to our implementation based of that API but made that it injects before it and we no longer need to worry about other mods kicking us from server before letting download a modpack - previously we were dealing with that by disabling those kicks by key words which wasn't great solution...
- Switched from using Forgified Fabric API in forge version to our own implementations allowing me to port to different forge versions.
- Support for other forge minecraft versions like 1.18.2, 1.19.2 and neoforge 1.20.2, 1.20.4!
- New wildcard, now you can use
!to exclude some file insyncedFiles.- Removed
excludeSyncedFilesfrom config.
- Removed
- Mods are now only stored inside automodpack folders.
- Fixed a lot of issues.
- More modular gradle setup.
Known issues:
- Quilt build is not ready
- Auto excluding server side mods doesn't do anything
- Connector - fabric on forge - mods won't load
New Contributors
- @wellcoming made their first contribution in https://github.com/Skidamek/AutoModpack/pull/199
Full Changelog: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0-beta1
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:GFCEupNV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k68glP2e:GFCEupNV"
}

