- Bumped the datapack format
- Removed support for MC 1.20
- Added compatibility for the new pack versioning format
- Changed the datapack in-game description to reflect the changes made in 1.21.9 snapshots
- Modified the files to make datapack compatible with 1.21.9 snapshot
- Bumped the datapack format
- Bumped the datapack format
- Updated item components to the new 1.21.5 format
- Bumped the datapack format to make it compatible with Minecraft 1.21.4
- Updated recipe keys to reflet changes made in 1.21.2
- Updated recipe component types to reflect changes made in 1.21.2
- Bumped the datapack format
Know issue: Installing CMCA can cause some issues with Roughly Enough Items (REI) mod (tested on 1.21.3 with REI 17.0.789), as it might stop showing chainmail armor and have problems to find the recipe. Although, all datapack's features works perfectly fine, so it's the error on the REI side.
- Changed the project icon
- Changes to "Cover me with chains" advancement:
- Moved "Cover me with chains" advancement to Minecraft's story advancement line
- Changed the amount of experience given for "Cover me with chains" advancement from 25 to
- Changed the title's and description's color and formating of "Cover me with chains" advancement
- Removed the "root" datapack advancement since no longer needed.
- Minor improvements to the datapack's files and it's formating
- Minor changes to the recipe unlockers
- Merged all version in one file
- Now you unlock the recipes by obtaining chains, instead of using the recipe for the first time.
- Made the datapack compatible with MC 1.21
- Changed the colors of advancements titles and descriptions so it's easier to read on advancement screen
- Modified all recipes to be compatible with new standard
- Crafting chainmail armor will now give you
Sturdy chainmail armor. This armor pieces are a little bit better than iron one because chains are made from 1 and 2/9 of ingot.
- Changed advancement's description color to
greenfromlight_greenI have no idea why it worked on 1.20.2 during testing, but when I was working on port to 1.20.5 I've seen that it's the problem.
Initial release