[Unsupported] ⚡ Custom Advancement Messages ⚡ | JSON | HEX |

Version 1.0.4.2 Added: - Support for 1.17. Fixed: - The plugin registering as a legacy plugin on 1.13+ servers. Changed: - Cleaned up the format of /cam debug. - Version checker no longer checks on snapshots.

Version 1.0.4.1 Fixed: - Data being saved to the advancementMessages file instead of the data file. [96d5b30] Removed: - Stray debug message. [8d55fca]

Version 1.0.4.0 Added: - The ability to disable sending messages for players in certain gamemodes. - The ability to disable messages in certain worlds (supports regex matching). Changed: - Updated the API link for the update checker. - Debug command now uses paste.insprill.net. This version contains config.yml changes. You can view them here: https://www.diffchecker.com/YCWAcR94

Version 1.0.3.0 Added: - Support for custom advancement names! Note: Some comments have been added to the advancementMessages.yml file explaining how the new feature works. You can see them here.

Version 1.0.2.0 Added: - Ability to add custom 'defaults'. This way you can group up certain advancements with the same message, without having to copy-paste it a thousand times. Removed: - Defaults based on advancement category. You can use the new custom ones to re-create this feature. Note: The advancementMessages.yml has been updated. You can view the changes here.

Version 1.0.1.1 Fixed: - Seemingly random error. (from root/ recipe advancements which don't send messages anyways).

Version 1.0.1.0 Added: - Options to change message for each Minecraft category. ( reference to update advancementMessages.yml). Changed: - Disabled advancements now require the full key, not just the name. - Plugin name is shortened to 'CAM' (this almost means the data folder is 'CAM'). - Don't add all 'root' & 'recipe' advancements to advancementsMessages file. (makes the file much much smaller as they were disabled internally anyways).

Version 1.0.0.0 Changes: - Enabled update checker.