ВЕРСИИ (11)

- Add curios compatability fixes from the 1.20.1 branch. - Optimizations and refactor to make things more side safe.

Remove relics attunement configuration that was used for testing.

Fix Curios Compatability Fix UI Bug

- Added new config options - Tags can now be used in the apply_to_items list. - Changed default attunement slot attribute to 20. You can now update the base attunement attribute in the configs to whatever you want though. - UI Updates. - Small fixes / refactoring.

Add config to allow players to pickup items attuned to other players. Defaults to off.

Added apply_to_items to .json options. Fixes from static code analyzer.

BREAKING CHANGES! You should start a new world with this update. From here on out there should be no more breaking changes. You can now define an attunement on an itemstack by itemstack basis. This allows you to make a single itemstack attunable with its own levels and enhancements that is unique only to that item. This will override any datapack configurations for that item type. This can be done by defining a datacomponent when you create the item, eithers with /give, advancements, recipes, or loot tables There is now a chance parameter that can be included in the attunement configuration datapack or override component. This value can be set between 0.000 and 1.000. Attunements that are not set to 1.0 (the default) now have a chance of being attunable, which will be determined the first time you put the item into the Attunement Nexus. If you set `"chance": 0.2` then the item only has a 20% chance of being attunable. When you try to place the item into the Attunement Nexus for the first time it will be determined if it is attunable or not. This is a 1 time check, and if it fails that item will never be attunable. Major refactor and simplification of certain parts of the code.

Initial 1.21.1 Neoforge release

Initial release for 1.20.1 Forge

Initial Modrinth Release