Tags
Creators
Details
2.3.0-beta.3+26.2
Compatibility
Required content
Changes
- Allowed built-in packs in folder packs (#61)
- The built-in pack ID must be in the folder's
packed_packs.folderpack.jsonpackIds,- Note: Pack IDs can be copied to clipboard by entering dev mode (
F12), right-clicking a pack, and selecting the copy option. - Example:
{ "module": false, "packIds": [ "continuity:default", "examplenamespace:examplepath" ] }
- Note: Pack IDs can be copied to clipboard by entering dev mode (
- This must be done outside the Packed Packs screen since the folder metadata is not watched and loaded once only.
- Note: It's loaded once only to avoid overwriting unsaved changes as the folder metadata is practically mutable. There is probably a better solution to this but this is the current limitation.
- The built-in pack ID must be in the folder's
- Allowed empty folders to load as folder packs.
- Added
sort_noneicon for none sort. - Updated icons for
trash,lockandunlock. - Widgets on top of pack entries are now navigable by keyboard.
- Fixed crash when saving state while a folder nested more than two levels deep is opened.
- Fixed sort button not working consistently for nested folders.
- Fixed folders nested more than three levels deep not being watched.
- Fixed folders not showing up first on
OLDESTandZ_Asort options. - Fixed pack rename incorrectly updating configs.
Packed Packs API
- Fixed
ScreenContext#rebuildnot rebuilding pack list entries (affectsv2.3.0-beta.2only)
This is an unstable version, things may break or change.
These are the last new changes for v2.3.0 so please report any issues and provide feedback here before I take another break on developing new features, it would be greatly appreciated. If no more issues are found in around a week then a stable version may be released.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| packed_packs-fabric-2.3.0-beta.3+26.2-sources.jar | Unknown | 194.71 KiB |
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:8Pq6Exn2:vQ0lGymN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8Pq6Exn2:vQ0lGymN"
}

