ВЕРСИИ (8)

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md). ## [3.1.0+1.20.1] - 2026.10.02 This update completes some partially implemented features related to diet suite switching, allows diet gain at full hunger, and fixes multiplayer syncing with custom food values enabled. ### Added - Diet suites can now be switched in-game - `/diet suite <player> <suite>` switches the player to another suite - `/diet suite <player>` shows a player's current suite - Food groups in both suites keep their values, while any new groups start at their `default_value` - A player's suite is now saved with the rest of their diet data and persists through death and reloads - If a suite cannot be loaded, players are moved back to the default suite - The `DietApi` methods `getSuite`, `setSuite`, and `getSuites` are now functional, so other mods can read and change a player's suite - Tooltips and eaten food only apply to groups in the selected suite - New server config options: - `defaultSuite` lets the default suite be changed to something other than `builtin` by default - `requireHungerGain` restores the previous behavior where food only increases diet values if it also increases the player's hunger - Added Spanish translation, thanks to [elbuda](https://github.com/elbuda) ### Changed - Foods can now increase diet values even if they don't increase hunger (meaning foods like golden apples and chorus fruit can continuously increase diet values) - The default diet suite now gives Hunger III instead of Hunger IV at high sugars ### Fixed - Fixed food value syncing on multiplayer servers, tooltips on the client should now show the right food values. - Fixed `food_values` files loading in an arbitrary order, they now load like vanilla tags - First, the version of a file from all datapacks is combined in the datapacks' order - `replace` will now discard only lower priority versions of the same file - Values from higher priority datapacks override lower ones - Errored files are now skipped earlier to avoid possibly overriding other files - Fixed some foods having the wrong `food_values` - Farmer's Delight cabbage - Farmer's Delight minced beef - Fixed the wrong error message appearing for an invalid status effect

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md). ## [3.1.0+1.20.1] - 2026.10.02 This update completes some partially implemented features related to diet suite switching, allows diet gain at full hunger, and fixes multiplayer syncing with custom food values enabled. ### Added - Diet suites can now be switched in-game - `/diet suite <player> <suite>` switches the player to another suite - `/diet suite <player>` shows a player's current suite - Food groups in both suites keep their values, while any new groups start at their `default_value` - A player's suite is now saved with the rest of their diet data and persists through death and reloads - If a suite cannot be loaded, players are moved back to the default suite - The `DietApi` methods `getSuite`, `setSuite`, and `getSuites` are now functional, so other mods can read and change a player's suite - Tooltips and eaten food only apply to groups in the selected suite - New server config options: - `defaultSuite` lets the default suite be changed to something other than `builtin` by default - `requireHungerGain` restores the previous behavior where food only increases diet values if it also increases the player's hunger - Added Spanish translation, thanks to [elbuda](https://github.com/elbuda) ### Changed - Foods can now increase diet values even if they don't increase hunger (meaning foods like golden apples and chorus fruit can continuously increase diet values) - The default diet suite now gives Hunger III instead of Hunger IV at high sugars ### Fixed - Fixed food value syncing on multiplayer servers, tooltips on the client should now show the right food values. - Fixed `food_values` files loading in an arbitrary order, they now load like vanilla tags - First, the version of a file from all datapacks is combined in the datapacks' order - `replace` will now discard only lower priority versions of the same file - Values from higher priority datapacks override lower ones - Errored files are now skipped earlier to avoid possibly overriding other files - Fixed some foods having the wrong `food_values` - Farmer's Delight cabbage - Farmer's Delight minced beef - Fixed the wrong error message appearing for an invalid status effect

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG). ## [3.0.2+1.20.1] - 2026.05.18 This is a bugfix update to fix a problem from the previous major update. See the [3.0 Changelog](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md#3001201---20260505) for details about the new features. ### Fixed - Fixed a command permission registration issue that stopped clients from joining servers

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG). ## [3.0.2+1.20.1] - 2026.05.18 This is a bugfix update to fix a problem from the previous major update. See the [3.0 Changelog](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md#3001201---20260505) for details about the new features. ### Fixed - Fixed a command permission registration issue that stopped clients from joining servers

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md). ## [3.0.1+1.20.1] - 2026.05.07 This is a minor update to fix a few problems from the previous major update. See the [3.0 Changelog](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md#3001201---20260505) for details about the new features. ### Added - Drinks and other non-food edible items can now provide nutrition if present in the `food_values` config. Items must use the eating or drinking animation to be considered edible. - Milk buckets now provide protein when data-driven food values are enabled in the config. ### Fixed - Fixed some foods having the wrong `food_values` - Vanilla beetroot soup - Farmer's Delight tomato sauce - Farmer's Delight cabbage - Fixed some typos in the default `food_values` that prevented some modded foods from registering nutrition properly - 10 food items from Corn Delight - 5 food items from Vegan Delight - 2 food items from Cultural Delights

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG). ## [3.0.1+1.20.1] - 2026.05.07 This is a minor update to fix a few problems from the previous major update. See the [3.0 Changelog](https://github.com/pawjwp/diet/blob/1.20.x/CHANGELOG.md#3001201---20260505) for details about the new features. ### Added - Drinks and other non-food edible items can now provide nutrition if present in the `food_values` config. Items must use the eating or drinking animation to be considered edible. - Milk buckets now provide protein when data-driven food values are enabled in the config. ### Fixed - Fixed some foods having the wrong `food_values` - Vanilla beetroot soup - Farmer's Delight tomato sauce - Farmer's Delight cabbage - Fixed some typos in the default `food_values` that prevented some modded foods from registering nutrition properly - 10 food items from Corn Delight - 5 food items from Vegan Delight - 2 food items from Cultural Delights

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/illusivesoulworks/diet/blob/1.20.x/CHANGELOG.md). ## [3.0.0+1.20.1] - 2026.05.05 This update was made by [Pawjwp](https://github.com/pawjwp) to add some clarity, balance, and quality of life features. This will be published on a fork of the Diet mod. ### Added - Tooltips - Each diet group now has a tooltip showing the effects that come from it, in addition to the aggregate tooltip at the top of the screen - Quality view (optional, data-driven) - Adds a system to show the “quality” of a food group to indicate to players what thresholds will provide positive or negative effects. - The quality display can be configured to appear upon hovering over a group bar, by clicking a button in the corner of the Diet screen, both, or neither. - Quality values can be defined for any effect in a diet suite using the `quality` field, which is set to a string containing a hex color code (ex: `"#3FDF3F"`). This value is drawn over that region of the bar whenever the quality view is visible. - Per-food nutrient control (optional, data-driven) - Added a config option that allows nutrition values to be set per-food rather than generated based on tags. When enabled, Diet will reference datapack files at `/diet/food_values` to get food values on a per-food basis. These are used in place of the tag-based ones. - The default datapack has default values configured for ~20 mods, more may be added in the future or upon request. These default values assume decreased drain rate for fruits and vegetables, and greatly increased drain rates for sugars. - Notification system (optional, data-driven) - Adds an optional notification system, customizable from within a diet suite. This is handled through a notification object that can be added to each effect block in the suite. - Fields: - `notification_id` (required) - `message`, uses translation keys and %s will be replaced by diet group name (required) - `notification_sets`, an array of strings used for bulk-muting - `trigger`, what change causes the notification to appear, can be one of: - `enter`, when the player enters the specified threshold (default if omitted) - `rise_into`, when the player enters the specified threshold from below - `fall_into`, when the player enters the specified threshold from above - `rise_through`, when the player enters or passes through the specified threshold from below - `fall_through`, when the player enters or passes through the specified threshold from above - `exit`, when the player leaves the specified threshold - `rise_out`, when the player leaves the specified threshold - `fall_out`, when the player leaves the specified threshold - `all`, when the player enters or exits the specified threshold - `default_frequency`, how many times the notification will appear. A config option sets the default values for when `default_frequency` is omitted. - `always`, notification will appear every time its trigger is met - `once`, notification will appear once and then set itself to `never` - `never`, notification will not appear unless triggered by testing commands - Effects can declare a notification without declaring any attributes or status effects - Notifications appear in chat based on their triggers and frequency. If a notification’s frequency is set to `once`, it will set itself to `never` after being triggered the first time. If a notification’s frequency is set to `always`, it will provide a prompt for the player to mute it (set its frequency to `never`). When clicked, the mute menu opens in chat with the following options: - Mute this, which mutes this specific notification ID - Mute set, which mutes all of the notifications that are part of the selected set - Mute group, which mutes all notifications with the same food group as the current notification - Mute all, which mutes all diet notifications - Clicking one of these buttons runs the new `/diet notifications` command with the appropriate parameters, but these commands can be run by the player to manually adjust their notification settings. The options for the command are: - `/diet notifications list`, which will list the notification defaults and current settings for each individual message ID - `/diet notifications all`, which will change notification frequency for all notifications - `/diet notifications group <group_id>`, which will change notification frequency for everything with the specified group ID - `/diet notifications set <set_id>`, which will change notification frequency for everything with specified set ID - `/diet notifications message <message_id>`, which will change notification frequency for the specified message ID - `/diet notifications options <message_id>`, which will show the mute menu for the specified message ID - `/diet notifications reset`, which will reset all notifications to their configured defaults (this will cause `once` notifications to re-trigger) - An additional new command has been added to manually test notifications. `/diet notify <target> <notification_id>` will trigger the notification with the specified ID. - New config options have been added to the server config: - `notificationsEnabled`, to enable or disable the entire notification system - `notificationsDefaultFrequency`, to set the frequency if the `default_frequency` field is omitted from a notification block in the diet suite - The default diet suite has been updated to include notifications for entering each of its three effects, and a new localization file was created under the “example” namespace to register the messages.

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). This is a copy of the changelog for the most recent version. For the full version history, go [here](https://github.com/illusivesoulworks/diet/blob/1.20.x/CHANGELOG.md). ## [3.0.0+1.20.1] - 2026.05.05 This update was made by [Pawjwp](https://github.com/pawjwp) to add some clarity, balance, and quality of life features. This will be published on a fork of the Diet mod. ### Added - Tooltips - Each diet group now has a tooltip showing the effects that come from it, in addition to the aggregate tooltip at the top of the screen - Quality view (optional, data-driven) - Adds a system to show the “quality” of a food group to indicate to players what thresholds will provide positive or negative effects. - The quality display can be configured to appear upon hovering over a group bar, by clicking a button in the corner of the Diet screen, both, or neither. - Quality values can be defined for any effect in a diet suite using the `quality` field, which is set to a string containing a hex color code (ex: `"#3FDF3F"`). This value is drawn over that region of the bar whenever the quality view is visible. - Per-food nutrient control (optional, data-driven) - Added a config option that allows nutrition values to be set per-food rather than generated based on tags. When enabled, Diet will reference datapack files at `/diet/food_values` to get food values on a per-food basis. These are used in place of the tag-based ones. - The default datapack has default values configured for ~20 mods, more may be added in the future or upon request. These default values assume decreased drain rate for fruits and vegetables, and greatly increased drain rates for sugars. - Notification system (optional, data-driven) - Adds an optional notification system, customizable from within a diet suite. This is handled through a notification object that can be added to each effect block in the suite. - Fields: - `notification_id` (required) - `message`, uses translation keys and %s will be replaced by diet group name (required) - `notification_sets`, an array of strings used for bulk-muting - `trigger`, what change causes the notification to appear, can be one of: - `enter`, when the player enters the specified threshold (default if omitted) - `rise_into`, when the player enters the specified threshold from below - `fall_into`, when the player enters the specified threshold from above - `rise_through`, when the player enters or passes through the specified threshold from below - `fall_through`, when the player enters or passes through the specified threshold from above - `exit`, when the player leaves the specified threshold - `rise_out`, when the player leaves the specified threshold - `fall_out`, when the player leaves the specified threshold - `all`, when the player enters or exits the specified threshold - `default_frequency`, how many times the notification will appear. A config option sets the default values for when `default_frequency` is omitted. - `always`, notification will appear every time its trigger is met - `once`, notification will appear once and then set itself to `never` - `never`, notification will not appear unless triggered by testing commands - Effects can declare a notification without declaring any attributes or status effects - Notifications appear in chat based on their triggers and frequency. If a notification’s frequency is set to `once`, it will set itself to `never` after being triggered the first time. If a notification’s frequency is set to `always`, it will provide a prompt for the player to mute it (set its frequency to `never`). When clicked, the mute menu opens in chat with the following options: - Mute this, which mutes this specific notification ID - Mute set, which mutes all of the notifications that are part of the selected set - Mute group, which mutes all notifications with the same food group as the current notification - Mute all, which mutes all diet notifications - Clicking one of these buttons runs the new `/diet notifications` command with the appropriate parameters, but these commands can be run by the player to manually adjust their notification settings. The options for the command are: - `/diet notifications list`, which will list the notification defaults and current settings for each individual message ID - `/diet notifications all`, which will change notification frequency for all notifications - `/diet notifications group <group_id>`, which will change notification frequency for everything with the specified group ID - `/diet notifications set <set_id>`, which will change notification frequency for everything with specified set ID - `/diet notifications message <message_id>`, which will change notification frequency for the specified message ID - `/diet notifications options <message_id>`, which will show the mute menu for the specified message ID - `/diet notifications reset`, which will reset all notifications to their configured defaults (this will cause `once` notifications to re-trigger) - An additional new command has been added to manually test notifications. `/diet notify <target> <notification_id>` will trigger the notification with the specified ID. - New config options have been added to the server config: - `notificationsEnabled`, to enable or disable the entire notification system - `notificationsDefaultFrequency`, to set the frequency if the `default_frequency` field is omitted from a notification block in the diet suite - The default diet suite has been updated to include notifications for entering each of its three effects, and a new localization file was created under the “example” namespace to register the messages.