• Add extra folders for pack discovery.
• Configure in config/packed_packs.json by adding paths under the additionalFolders array inside resourcepacks or datapacks.
• If the array doesn’t exist, create it manually or open and close the Packed Packs screen to update the config.
• Paths can be absolute or relative to the game directory.
• Correctly added folders appear as a context menu option under Open Pack Folder.
• Requires game restart to apply.

• Any folder without a pack.mcmeta will be treated as a folder pack.
• Add a pack.png at the folder root to set a custom icon.
• Folders can be nested.
• They can be opened to view and reorder their contents. The order is saved to packed_packs.folderpack.json in the folder root.
• Folder packs can be locked to make them behave like regular packs which can be moved between rows and columns. These are also known as modules.
  • Children cannot be moved outside locked folder packs. Locking a folder pack will automatically recall its children.
  • Locked folder packs will also lock all descendants that are folders.
  • Newly discovered folders can be made locked by default from the options menu.
• Built-in packs can be added inside folder packs when specified in packed_packs.folderpack.json.
  • Example:

    {
      "module": false,
      "packIds": [
        "continuity:default",
        "examplenamespace:examplepath"
      ] 
    }

  • Note: This can only be done outside the Packed Packs screen as the packed_packs.folderpack.json file is only loaded once on enter to prevent overwriting unsaved state.

• Apply resource packs automatically on close.
• Replace the default resourcepack & datapack screens.
• Remove the red background on incompatible packs.
• Make folder packs locked by default.
• Remember the last viewed profile when reopening the screen.

• Toggle developer mode — `Ctrl` + `Shift` + `I` | `F12`
• Additional options will appear in the context menu when in developer mode.
• Preferences: Toggle the visibility of certain widgets.
• Lock Profiles: Locked profiles cannot be deleted, renamed, or modified.
• Override Pack Properties:
  • Overrides are configured per profile and apply only to that profile unless set as default.
  • Override the required property of packs. Also allows disabling required packs.
  • Override the position property of packs. Also allows moving fixed packs.
  • Hide packs.
• Default Profiles:
  • Overrides from the default profile are enabled globally for all profiles and even without one, including the original screen.
  • Enabled packs under the default profile are automatically marked as compatible.
  • Default profiles load automatically in the following cases:
    • Resource Packs:  when the options.txtor the config/packed_packs/__version.json, is missing.
    • Data Packs: when creating a new world.
• Pack Aliases: Add aliases to Pack IDs
  • Designed to help modpack devs migrate resource/data packs when updates are needed without affecting the user's configured pack selection and order.
  • Only used if the pack is selected but doesn't exist. Matching starts from the top of the alias map and resolves to the first match, see the config.meta.json file.
  • Supports regex (must be prefixed with regex:), the text color will change in the Edit Aliases dialog if done correctly.
  • Exact matches always take priority over regex matches, regardless of their position in the alias map (e.g., a pack ID of file/test-v1.2 will always match "file/test-v1.2": "file/test-v1.4" over "regex:file\\/test-v\\d*": "file/test-v2").
  • Aliases can also map to a regex value (must be prefixed with regex:), which will attempt to match with any available pack. This can only be done from the config.meta.json file.
  • Aliases are never cleared automatically, even if it points to a pack that no longer exists. They are only removed manually from the in-game GUI or the config file.
  • It is generally not recommended to use on data packs as it could break worlds. Test thoroughly.

The Java API, designed as an optional dependency, allows mods to extend functionality or add compatibility with Packed Packs. This includes subscribing to various events and registering custom preferences to add configurable widgets at certain positions of the screen.

You can find example implementations in the testmod, and in the compat package of the **main** source set.

You may also view the javadocs from the source code.

Visit the wiki page for more details.

Explicit compatibility is added for:

• Resourcify
• Respackopts
• VTDownloader
• Entity Texture Features
• Polytone

Submit an issue if the above mods have become incompatible. Make sure to verify that the correct mod version is used for the target minecraft version, and if the issue only occurs with Packed Packs installed.

Note: Compatibility for the above mods were added before the Java API was made. It would be better for other mods to make use of the Java API instead for better long term compatibility. If the above mods make enough breaking changes, it may have to be dropped.