ВЕРСИИ (93)

## Changes * Updated to 26.1. * Support for reading the legacy Patched metadata (which has been deprecated since 1.21.1) has been withdrawn. Packs that aren't yet using the `patched { ... }` format will need to be updated to use it.

## Changes * Updated to 26.1. * Support for reading the legacy Patched metadata (which has been deprecated since 1.21.1) has been withdrawn. Packs that aren't yet using the `patched { ... }` format will need to be updated to use it.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present. ## Backported Changes * Fixed patches not being detected from data/resource packs that contain overlays.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present. ## Backported Changes * Fixed patches not being detected from data/resource packs that contain overlays.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present. * Fixed broken `FilePackResources` handling on 1.20.2. * Fixed patches not being detected from data/resource packs that contain overlays on 1.20.2.

## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Fixed `pack_enabled` test condition erroring when no dynamic patches are present. * Fixed broken `FilePackResources` handling on 1.20.2. * Fixed patches not being detected from data/resource packs that contain overlays on 1.20.2.

## Known Issues * ModernFix's `mixin.perf.resourcepacks` option breaks Patched's resource scanning, causing mod resources to not be suggested in `/patched dump` and `/patched trace`. If you need those suggestions, then set `mixin.perf.resourcepacks=false` in `modernfix-mixins.properties`. * Fabric API breaks Patched's vanilla resource scanning, causing vanilla's assets and data to not be suggested in `/patched dump` and `/patched trace`. This is not something I can fix or work around. ## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Backported Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new test types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Patched now names packs using the format from 1.20.1 and up. In other words, instead of `<folder name>` it's `file/<folder name>`, instead of `Default` it's `vanilla`, and instead of `Programmer Art` it's `programmer_art`. This allows data/resource packs using the `patched:pack_enabled` test condition to work on 1.19.2 and 1.18.2 without needing to account for these names. (Side note: this change doesn't break anything because the `patched:pack_enabled` test condition didn't exist on this version yet.) ## Backported Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a patched section. **Patched will still load old-style packs.** * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors. * On Fabric, give custom builtin packs better names. ## Backported Changes (for mod developers) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Known Issues * ModernFix's `mixin.perf.resourcepacks` option breaks Patched's resource scanning, causing mod resources to not be suggested in `/patched dump` and `/patched trace`. If you need those suggestions, then set `mixin.perf.resourcepacks=false` in `modernfix-mixins.properties`. * Fabric API breaks Patched's vanilla resource scanning, causing vanilla's assets and data to not be suggested in `/patched dump` and `/patched trace`. This is not something I can fix or work around. ## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Backported Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new test types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Patched now names packs using the format from 1.20.1 and up. In other words, instead of `<folder name>` it's `file/<folder name>`, instead of `Default` it's `vanilla`, and instead of `Programmer Art` it's `programmer_art`. This allows data/resource packs using the `patched:pack_enabled` test condition to work on 1.19.2 and 1.18.2 without needing to account for these names. (Side note: this change doesn't break anything because the `patched:pack_enabled` test condition didn't exist on this version yet.) ## Backported Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a patched section. **Patched will still load old-style packs.** * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors. * On Fabric, give custom builtin packs better names. ## Backported Changes (for mod developers) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Known Issues * ModernFix's `mixin.perf.resourcepacks` option breaks Patched's resource scanning, causing mod resources to not be suggested in `/patched dump` and `/patched trace`. If you need those suggestions, then set `mixin.perf.resourcepacks=false` in `modernfix-mixins.properties`. * Fabric API breaks Patched's vanilla resource scanning, causing vanilla's assets and data to not be suggested in `/patched dump` and `/patched trace`. This is not something I can fix or work around. ## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Backported Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new test types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Patched now names packs using the format from 1.20.1 and up. In other words, instead of `<folder name>` it's `file/<folder name>`, instead of `Default` it's `vanilla`, and instead of `Programmer Art` it's `programmer_art`. This allows data/resource packs using the `patched:pack_enabled` test condition to work on 1.19.2 and 1.18.2 without needing to account for these names. (Side note: this change doesn't break anything because the `patched:pack_enabled` test condition didn't exist on this version yet.) ## Backported Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a patched section. **Patched will still load old-style packs.** * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors. * On Fabric, give custom builtin packs better names. ## Backported Changes (for mod developers) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Known Issues * ModernFix's `mixin.perf.resourcepacks` option breaks Patched's resource scanning, causing mod resources to not be suggested in `/patched dump` and `/patched trace`. If you need those suggestions, then set `mixin.perf.resourcepacks=false` in `modernfix-mixins.properties`. * Fabric API breaks Patched's vanilla resource scanning, causing vanilla's assets and data to not be suggested in `/patched dump` and `/patched trace`. This is not something I can fix or work around. ## Breaking Changes * Patched is now multi-version: this means that future bug fixes and features will propagate to all supported versions, not just the latest. With this came some major re-architecturing which **will have broken pretty much any mod with a compile-time dependency on Patched**. In other words, mods that interface directly with Patched's code. Data/resource packs and mods that don't touch Patched's code at all will be perfectly fine. Mods that use (Neo)Forge's IMC feature to communicate with Patched will also be fine. I'm not currently aware of any mods that touch Patched's code, but any that do exist will need to adapt to these changes to work with the new version(s). * Patched (the library) has been updated to version 2.0.0. This will almost certainly impact anyone touching the library (or the mod) directly. One can read about the changes [here](https://github.com/EnderTurret/Patched/releases/tag/v2.0.0). * **Removed full Quilt support**. There is now only partial Quilt support in the Fabric version of the mod. It'll apply patches from data packs and resource packs but not from mods. (There aren't any Quilt exclusive mods that contain patches anyway.) If you do need patches from mods to apply then consider migrating to Fabric instead. ## New Features * Added the `/patched trace <file>` command (also works with `/patchedc`), which allows "tracing" the trail of patches/overrides applied to a specified file. This can be used to find out whether a given patch is *actually* applying to a file without needing to read through a (possibly massive) json file from `/patched dump file`. As a bonus, it'll list the overrides of files that have had no patches applied. For example, did you know that NeoForge replaces the bucket recipe? (I already did, but maybe you didn't — and now you can know all that and more with this command!) * Added absolute paths and placeholders. See also the updated path documentation [here](https://github.com/EnderTurret/PatchedMod/wiki/JSON-Paths). * Packs with dynamic patches no longer need a file in the namespaces they're targeting for their patches to apply. One can now get rid of their `_dummy.json` files, if present. ## New Features (for mod developers) * On Fabric, custom test conditions and data sources can now be registered using `ObjectShare`. See the documentation for details. ## Backported Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new test types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Changes * Patches dumped using the wrong-sided command (e.g. `/patched dump ...` on a patch in `assets`) will now dump normally rather than cryptically failing. * Fixed errors about malformed or missing dynamic patches being logged with more detail than they should (and only once). * The "Applying patch ... from ..." and "Built PatchTargetManager ..." messages are no longer logged by default, as they're usually not necessary (and add a lot of noise to the logs). If you need either for whatever reason, you can turn them back on by adding `-Dpatched.debug` to your JVM arguments. * Patched now names packs using the format from 1.20.1 and up. In other words, instead of `<folder name>` it's `file/<folder name>`, instead of `Default` it's `vanilla`, and instead of `Programmer Art` it's `programmer_art`. This allows data/resource packs using the `patched:pack_enabled` test condition to work on 1.19.2 and 1.18.2 without needing to account for these names. (Side note: this change doesn't break anything because the `patched:pack_enabled` test condition didn't exist on this version yet.) ## Backported Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a patched section. **Patched will still load old-style packs.** * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors. * On Fabric, give custom builtin packs better names. ## Backported Changes (for mod developers) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Changes * Fixed patches not being detected from data/resource packs that contain overlays.

## Changes * Fixed patches not being detected from data/resource packs that contain overlays.

## Changes * Ported to 1.21.11.

## Changes * Ported to 1.21.11.

### Changes * Fix a crash on 1.21.6 when running any of Patched's commands.

### Changes * Fix a crash on 1.21.6 when running any of Patched's commands.

### Changes * Inter-patch application order has been reversed, aligning it with expectations. Previously, if you had two packs A and B which both contain patches modifying the same part of the same file, then whichever pack came first (i.e. bottom of the resource pack screen or first in the data pack list) would win. In other words, patches are applied in order of highest to lowest priority. This is generally undesirable behavior because it means you can't write a data pack that modifies a mod's patched-in world gen changes *without placing the data pack below the mod in the data pack list*. Now patches are applied in order of least to highest priority. **This is a breaking change for anyone relying on the previous order**. However, the vast majority of people will not be affected by this change as it requires a situation like the earlier example, which is not very common.

### Changes * Inter-patch application order has been reversed, aligning it with expectations. Previously, if you had two packs A and B which both contain patches modifying the same part of the same file, then whichever pack came first (i.e. bottom of the resource pack screen or first in the data pack list) would win. In other words, patches are applied in order of highest to lowest priority. This is generally undesirable behavior because it means you can't write a data pack that modifies a mod's patched-in world gen changes *without placing the data pack below the mod in the data pack list*. Now patches are applied in order of least to highest priority. **This is a breaking change for anyone relying on the previous order**. However, the vast majority of people will not be affected by this change as it requires a situation like the earlier example, which is not very common.

## Changes * Fix server-side resource reloads (via the `/reload` command) breaking dynamic patches * Fix a potential error when using the `patched:registered` test condition on 1.21.4

## Changes * Fix server-side resource reloads (via the `/reload` command) breaking dynamic patches * Fix a potential error when using the `patched:registered` test condition on 1.21.4

## Changes * Fix data generation crashing on 1.21.3.

## Changes * Fix data generation crashing on 1.21.3.

## Changes * The version number now includes the platform. For example, `7.3.1+1.21.1` is now `7.3.1+1.21.1-neoforge` (corresponding to the platform it was built for). This means that modders depending on the mod via Modrinth's maven do not need to use a version number like 'EddDSwpM'. The names of each file have also changed slightly to reflect this.

## Changes * The version number now includes the platform. For example, `7.3.1+1.21.1` is now `7.3.1+1.21.1-neoforge` (corresponding to the platform it was built for). This means that modders depending on the mod via Modrinth's maven do not need to use a version number like 'EddDSwpM'. The names of each file have also changed slightly to reflect this.

## Changes * The version number now includes the platform. For example, `7.3.1+1.21.1` is now `7.3.1+1.21.1-neoforge` (corresponding to the platform it was built for). This means that modders depending on the mod via Modrinth's maven do not need to use a version number like 'EddDSwpM'. The names of each file have also changed slightly to reflect this.

## Changes * The version number now includes the platform. For example, `7.3.1+1.21.1` is now `7.3.1+1.21.1-neoforge` (corresponding to the platform it was built for). This means that modders depending on the mod via Modrinth's maven do not need to use a version number like 'EddDSwpM'. The names of each file have also changed slightly to reflect this.

## Changes * The version number now includes the platform. For example, `7.3.1+1.21.1` is now `7.3.1+1.21.1-neoforge` (corresponding to the platform it was built for). This means that modders depending on the mod via Modrinth's maven do not need to use a version number like 'EddDSwpM'. The names of each file have also changed slightly to reflect this.

## New Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. ## New Features (modder-facing) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. ## Changes (modder-facing) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. Test conditions registered the old way will still work.

## New Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. ## New Features (modder-facing) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. ## Changes (modder-facing) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. Test conditions registered the old way will still work.

## New Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. ## New Features (modder-facing) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. ## Changes (modder-facing) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. Test conditions registered the old way will still work.

## New Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. ## New Features (modder-facing) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. ## Changes (modder-facing) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. Test conditions registered the old way will still work.

## New Features * Patches can now be applied to tags/sounds json/blockstates(?)/etc. or so-called "merged files". These only work for files defined *in the same pack*. That is, you cannot patch a tag defined by Minecraft (although you could patch your own contributions to it). This opens up the possibility for configurable tags, among other things. ## New Features (modder-facing) * Added the `paste` patch type, which allows 'pasting' arbitrary code-defined data in json files. The intended purpose of this patch type is to make it possible to get config values into otherwise-unconfigurable things like biomes. For example, making a feature's spawn rate configurable without needing data packs. See the documentation and `SingleDataSource` for more information. * On (Neo)Forge, mods may now use IMC (InterModComms) to register data sources (for the `paste` operation) and test conditions (for `test` patches with a `type` field). See the documentation for details. ## Changes (modder-facing) * Custom test registration has changed — they are now registered using `Patched.registerTestCondition()` and `Patched.registerSimpleTestCondition()`. Test conditions registered the old way will still work.

## Features * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. ## Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. ## Changes (for mod developers) * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Features * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. ## Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. ## Changes (for mod developers) * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Changes * Fixed a crash when using the Programmer Art resource pack. (This was caused by a missed change from Fabric API.) This does not affect the Forge build, and shouldn't affect Quilt either (it already has this change).

This update backports just about everything added from `5.1.0+1.20.4` to `7.1.1+1.21.1`. It also introduces a few new changes and features, which will be ported over to `1.21.1` shortly. ## Backported Features * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new `test` types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Backported Changes * **The Patched metadata in pack.mcmeta files has been modified** to reflect Mojang's changes to pack metadata sections. In short: `patched:has_patches` is no more, and instead there's a `patched` section. **Patched will still load old-style packs.** ## New Features * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. ## New Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. ## New Changes (for mod developers) * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

This update backports just about everything added from `5.1.0+1.20.4` to `7.1.1+1.21.1`. It also introduces a few new changes and features, which will be ported over to `1.21.1` shortly. ## Backported Features * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new `test` types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Backported Changes * **The Patched metadata in pack.mcmeta files has been modified** to reflect Mojang's changes to pack metadata sections. In short: `patched:has_patches` is no more, and instead there's a `patched` section. **Patched will still load old-style packs.** ## New Features * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. ## New Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. ## New Changes (for mod developers) * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

This update backports just about everything added from `5.1.0+1.20.4` to `7.1.1+1.21.1`. It also introduces a few new changes and features, which will be ported over to `1.21.1` shortly. ## Backported Features * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new `test` types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above ## Backported Features (for mod developers) * The patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. * Patched now supports reading its metadata from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`quilt.mod.json`/`mods.toml`! ## Backported Changes * **The Patched metadata in pack.mcmeta files has been modified** to reflect Mojang's changes to pack metadata sections. In short: `patched:has_patches` is no more, and instead there's a `patched` section. **Patched will still load old-style packs.** ## New Features * Added a new `test` type: `patched:pack_enabled`, which allows checking for the existence of data/resource packs. See the documentation for details. ## New Changes * Rewrote Patched's primary mixin for better compatibility with mods that cause re-entrant resource queries, such as Tiny Skeletons. ## New Changes (for mod developers) * Patched's library sources are now included in the mod's sources jar. * Patched's internals (or most of them) are now in an `internal` package, rather than spread out all over the place. This will break code using or mixing into these internals, but you shouldn't be doing that anyway.

## Changes * Support using a `RegistryOps` in the datagen code.

## Changes * Support using a `RegistryOps` in the datagen code.

## Changes This is mostly a modder-facing update, adding two things. First, the patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. Second, Patched now supports reading its metadata block from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`neoforge.mods.toml`! See the recently added section in the 'Installation' document for the exact syntax.

## Changes This is mostly a modder-facing update, adding two things. First, the patch datagen stuff now supports `Codec`s in all of the methods taking `Object`s, and also now allows providing an alternate `Gson` for serialization in the `Object` versions. There's also been some minor javadoc improvements in that area. Second, Patched now supports reading its metadata block from the loader-specific mod metadata files! This means that modders can finally ditch their `pack.mcmeta`s and move this data to their `fabric.mod.json`/`neoforge.mods.toml`! See the recently added section in the 'Installation' document for the exact syntax.

## Changes * Updated to 1.21. * The Fabric build no longer *requires* Fabric API. However, running without Fabric API will prevent mods' patches from being applied, and will cause Patched's client commands to be unavailable. (These features require Fabric API's resource-loader and command-api modules, respectively.)

## Changes * Updated to 1.21.

## Changes * Updated to 1.20.5.

## Changes * Updated to 1.20.5.

## Features * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new `test` types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above See also the updated documentation for details on all of these. ## Changes * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a `patched` section. **Patched will still load old-style packs, for now.** * Fabric: fixed mixins that broke with semi-recent (mid-January) changes to Fabric API. * NeoForge: updated mod metadata for semi-recent (late-December?) FML changes

## Features * Added the `include` operation, which allows effectively including the contents of a patch inside another patch. This is intended to reduce patch duplication. * Added "patch targets" (also called "dynamic" patches), which allow applying a single patch to any number of files. * Added two new `test` types: * `patched:registered`, which allows testing for the existence of something in a registry * `patched:item_registered`, which is a simplified version of the above See also the updated documentation for details on all of these. ## Changes * **The Patched metadata in `pack.mcmeta` files has been modified** to reflect Mojang's changes to pack metadata sections over the past several updates. In short: `patched:has_patches` is no more, and instead there's a `patched` section. **Patched will still load old-style packs, for now.** * Fabric: fixed mixins that broke with semi-recent (mid-January) changes to Fabric API. * NeoForge: updated mod metadata for semi-recent (late-December?) FML changes

## Changes * Port to NeoForge 1.20.4.

## Changes * Updated to latest 1.20.2 Fabric API.

## Changes * Try to avoid crashing the game if an "early loading" error occurs. * Fix crash on NeoForge ≥20.2.65.

## Changes * Update to 1.20.2. There is not currently a Quilt version because QSL does not appear to support 1.20.2 yet. Do not try to use the Fabric version on Quilt; it won't work.

## Changes * Update to 1.20.2. There is not currently a Quilt version because QSL does not appear to support 1.20.2 yet. Additionally, Forge has been dropped in favor of NeoForge on 1.20.2+ -- the latest 1.20.1 build should work on Forge 1.20.2, but will likely not work on 1.20.3 and higher. Forge will remain supported on 1.20.1 and below. Note: the NeoForge sources jar doesn't exactly match the real source code as the common mixins needed `remap = false` added in order to build (NeoForge 1.20.2 removed mod reobf). This doesn't affect other platforms.

## Changes * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors.

## Changes * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors.

## Changes * Fix packs that take advantage of Minecraft's filtering causing Patched to throw countless errors.

## Changes * On Fabric (and theoretically also Quilt), give custom builtin packs better names.

## Changes * On Fabric (and theoretically also Quilt), give custom builtin packs better names.

## Changes * On Fabric (and theoretically also Quilt), give custom builtin packs better names.

## Changes * Made the mod avoid crashing if its `FilePackResources` accessor fails to apply. In particular, this change allows the mod to run on 1.20.2 without anything breaking (except for the list commands on `.zip` data/resource packs).

## Changes * Made the mod avoid crashing if its `FilePackResources` accessor fails to apply. In particular, this change allows the mod to run on 1.20.2 without anything breaking (except for the list commands on `.zip` data/resource packs).

## Changes * Made the mod avoid crashing if its `FilePackResources` accessor fails to apply. In particular, this change allows the mod to run on 1.20.2 without anything breaking (except for the list commands on `.zip` data/resource packs).

Backported all of the changes from 1.19.2 <=> 1.20.1: ## Features * Leveraged patch audits in file dumping. This means that you can now easily see who changed what (via patches; file replacements have no such indicators). * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively. * Implemented the `patched:mod_loaded` condition, with support for testing against specific mod versions. * Implemented basic datagen support for patches. ## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. * Updated to Patched 1.3.0 (up from 1.0.0). * Patches can now patch other patches. * Only parse obvious json files as json, and other optimizations (like not unnecessarily reading files). ## Bug Fixes * Fixed patches from mods not actually being applied. * Properly expand mod loader "group" packs to have one pack per mod in commands. * Fixed listing patches of `.zip` packs not working properly. * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen.

Backported all of the changes from 1.19.2 <=> 1.20.1: ## Features * Leveraged patch audits in file dumping. This means that you can now easily see who changed what (via patches; file replacements have no such indicators). * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively. * Implemented the `patched:mod_loaded` condition, with support for testing against specific mod versions. * Implemented basic datagen support for patches. ## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. * Updated to Patched 1.3.0 (up from 1.0.0). * Patches can now patch other patches. * Only parse obvious json files as json, and other optimizations (like not unnecessarily reading files). ## Bug Fixes * Fixed patches from mods not actually being applied. * Properly expand mod loader "group" packs to have one pack per mod in commands. * Fixed listing patches of `.zip` packs not working properly. * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen.

Backported all of the changes from 1.19.2 <=> 1.20.1: ## Features * Leveraged patch audits in file dumping. This means that you can now easily see who changed what (via patches; file replacements have no such indicators). * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively. * Implemented the `patched:mod_loaded` condition, with support for testing against specific mod versions. * Implemented basic datagen support for patches. ## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. * Updated to Patched 1.3.0 (up from 1.0.0). * Patches can now patch other patches. * Only parse obvious json files as json, and other optimizations (like not unnecessarily reading files). ## Bug Fixes * Fixed patches from mods not actually being applied. * Properly expand mod loader "group" packs to have one pack per mod in commands. * Fixed listing patches of `.zip` packs not working properly. * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `2.x.x` to allow better differentiation between builds from past and future major versions (this change has also been applied to the latest 1.20.x build). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `2.x.x` to allow better differentiation between builds from past and future major versions (this change has also been applied to the latest 1.20.x build). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `2.x.x` to allow better differentiation between builds from past and future major versions (this change has also been applied to the latest 1.20.x build). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `3.x.x` to allow better differentiation between builds from past major versions (and will likely be bumped again if `1.20.2` includes breaking changes). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `3.x.x` to allow better differentiation between builds from past major versions (and will likely be bumped again if `1.20.2` includes breaking changes). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

## Changes * The version format has been modified to comply a bit better with Semver and allow mods to actually depend on the mod. The version has been bumped to `3.x.x` to allow better differentiation between builds from past major versions (and will likely be bumped again if `1.20.2` includes breaking changes). * Updated to Patched 1.3.0, bringing with it mainly one change: patches can now replace the root document. * Patches can now patch other patches. * More optimizations to patching file I/O. In particular, we don't try to read a file if no one is trying to patch it. * The `patched:mod_loaded` test condition now supports testing against specific mod versions. * There are now two new subcommands for `/patched[c] dump file ...`: `raw` and `unpatched`, for dumping the comment-less patched file and for dumping the file without applying patches, respectively.

### Changes * Backport Quilt support to 1.19.2.

### Changes * Moved to a multi-loader workspace, like the 1.20 version. * Backported the following changes: * Only parse obvious json files as json, theoretically improving performance. * Properly expand mod loader "group" packs to have one pack per mod in commands. * Fixed listing patches of `.zip` packs not working properly. * Fix not applying patches from Fabric mods. * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen (untested, but should work).

### Changes * Moved to a multi-loader workspace, like the 1.20 version. * Backported the following changes: * Only parse obvious json files as json, theoretically improving performance. * Properly expand mod loader "group" packs to have one pack per mod in commands. * Fixed listing patches of `.zip` packs not working properly. * Fix not applying patches from Fabric mods. * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen (untested, but should work).

### Changes * Add Quilt support.

### Changes * The mod now uses a proper multi-loader workspace instead of one branch per loader. * Also we're now publishing source jars. * Patched now only tries to parse obvious json files as json. * This should slightly improve load times. * Side note: this was supposed to be the case from the beginning, but then I noticed the code for it had no usages... * "Group" packs are now expanded in the commands, meaning e.g. instead of a "Fabric Mods" or "mod_resources" pack there's instead a pack for each mod. * Fixed listing patches of `.zip` packs not working properly.

### Changes * The mod now uses a proper multi-loader workspace instead of one branch per loader. * Also we're now publishing source jars. * Patched now only tries to parse obvious json files as json. * This should slightly improve load times. * Side note: this was supposed to be the case from the beginning, but then I noticed the code for it had no usages... * "Group" packs are now expanded in the commands, meaning e.g. instead of a "Fabric Mods" or "mod_resources" pack there's instead a pack for each mod. * Fixed listing patches of `.zip` packs not working properly.

### Changes * Updated to 1.20.

### Changes * Updated to 1.20.

### Changes * Fix not applying patches from other Fabric mods.

### Changes * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen.

### Changes * Fixed packs not showing up in `/patched list packs` if they were added using the data packs section of the create world screen.

### Changes * Updated to 1.19.3.

### Changes * Updated to 1.19.3.

### Changes * Fixed patches from mods being completely ignored. * This means that mods can actually patch things now.

### Changes * Bumped Patched library dependency to 1.2.1 (up from 1.1.1). * See also its changelogs [here](https://github.com/EnderTurret/Patched/releases/tag/v1.2.0) and [here](https://github.com/EnderTurret/Patched/releases/tag/v1.2.1). * Leveraged patch audits in file dumping. * This means that you can now easily see who changed what (via patches; file replacements have no such indicators). ### Internal Changes * [Breaking Change] Made exposed utility classes `final` and made some internal code package-private. * Made Forge/Fabric code more similar to each other. * Properly marked internal code as internal.

### Changes * Bumped Patched library dependency to 1.2.1 (up from 1.1.1). * See also its changelogs [here](https://github.com/EnderTurret/Patched/releases/tag/v1.2.0) and [here](https://github.com/EnderTurret/Patched/releases/tag/v1.2.1). * Leveraged patch audits in file dumping. * This means that you can now easily see who changed what (via patches; file replacements have no such indicators). ### Internal Changes * [Breaking Change] Made exposed utility classes `final` and made some internal code package-private. * Made Forge/Fabric code more similar to each other. * Properly marked internal code as internal.

* Updated to 1.19.2 * Updated to Patched 1.1.1 * Added support for "custom test conditions" * Implemented the `patched:mod_loaded` condition * Implemented basic datagen support for patches

* Updated to 1.19.2 * Updated to Patched 1.1.1 * Added support for "custom test conditions" * Implemented the `patched:mod_loaded` condition * Implemented basic datagen support for patches