Tags
Creators
Details
All versions
2.3.0-beta.1+26.3
Beta
Fabric v2.3.0-beta.1+26.3last week 2,016
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
- Folder Packs are now discoverable recursively
- Folder Packs can now be locked/unlocked
- Can be toggled from the folder view or from the metadata under the
moduleflag. - Locked folders behave exactly the same as regular folder packs.
- Nested folders within locked folder packs will be force-locked.
- Cannot be sorted
- An unlocked folder's children can be transferred outside the folder.
(#47)
- Cannot itself be enabled, will instead be flattened.
- Can be sorted
- Folders cannot be unlocked from the enabled list.
- Folders are unlocked by default. Can be changed from the options menu.
- Existing folder packs prior to updating will be locked to preserve behavior.
- Can be toggled from the folder view or from the metadata under the
- Folder pack metadata files are no longer watched and are loaded immediately with the folder pack upon entering the screen.
- Renaming a pack from the Packed Packs screen now also updates all profiles and folders that contain that pack.
- Fixed search not working for folders.
- Fixed being unable to drag non-required fixed position packs from the enabled list.
API Changes
- Folders no longer trigger pack-related events (they are not
Packs anymore). PackContextare now considered asPackSelectionModel.EntryScreenContext#getAvailablePacksandScreenContext#getSelectedPacksnow includes all descendants (flattened).
This is an unstable version, thing may break or change. Please report any issues here.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| packed_packs-fabric-2.3.0-beta.1+26.3-sources.jar | Unknown | 191.42 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:kHk67giV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8Pq6Exn2:kHk67giV"
}

