Tags
Creators
Details
All versions
2.3.0+1.21.11
Release
NeoForge v2.3.0+1.21.113 weeks ago 14
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Changes
This is the stable release of v2.3.0, to recap:
- Folder Packs can now be nested.
- Folder Packs can now be locked and unlocked.
- Locked folders behave exactly the same as usual.
- Nested folders within locked folder packs will be force-locked.
- Children of unlocked folders can be enabled individually
(#47).
- Unlocked folders that become locked will automatically recall its descendants.
- Unlocked folders themselves cannot be enabled, they will be flattened instead.
- Folder packs are now unlocked by default. This can be changed from the options menu.
- Existing folder packs with saved configs (that has no
moduleflag) will be locked to preserve behavior.
- Existing folder packs with saved configs (that has no
- Allowed built-in packs in folder packs (#61)
- The built-in pack ID must be in the folder config's
packIds, - This can only be done outside the Packed Packs screen due to the change below.
- The built-in pack ID must be in the folder config's
- Folder pack config files are no longer watched and are loaded immediately upon entering the screen. This is to prevent overwriting unsaved state on refreshes.
- Empty folders will now load as folder packs.
- Renaming a pack from the Packed Packs screen should now also update all profiles and its parent folder pack.
- Updated Russian Translations (#75 by iceban)
- Updated icons for
trash,lock, andunlock. - Widgets on pack entries are now navigable by keyboard.
- Fixed search not working for folders.
- Fixed being unable to drag non-required fixed position packs from the enabled list.
Changes since v2.3.0-beta.3
- Removed restrictions on symlinks, however restrictions set by vanilla Minecraft may still apply (symlinks may need to
be specified in
allowed_symlinks.txt). - Improved compatibility with Controlify.
Fixes with v2.3.0-beta.3:
- Fixed hidden folders being loaded as folder packs
- Fixed empty folders not showing up inside folders.
- Fixed folder order not saving on undo/redo
- Fixed remember last viewed profile option not working.
- Fixed incorrect warning being logged about opening non-module folder from enabled list.
- Fixed folders sometimes changing its lock state when the "Folders Locked by Default" option is changed.
- Built-in packs contained in folders will now log duplicates in other folders. The precedence of which folder wins is not known.
API Changes
- Folders no longer trigger pack-related events (they are not
Packs anymore). PackContextare now considered asPackSelectionModel.EntryScreenContext#getAvailablePacksandScreenContext#getSelectedPacksare now flattened.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| packed_packs-neoforge-2.3.0+1.21.11-sources.jar | Unknown | 194.56 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:keOjUQLS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8Pq6Exn2:keOjUQLS"
}

