3.0.1 (Fishing Fix)

What's Changed

• Fixed all items acquired through fishing getting timestamped. by @dmccoystephenson in #211

Full Changelog: 3.0.0...3.0.1

Food Spoilage 3.0.0 (Overhaul, Fixes, RPKit Integration)

Note

When upgrading from a pre-3.0.0 version of the plugin, the config.yml will need to be deleted in order to get this version to work.

What's Changed

• Migrate to gradle by @alyphen in #186
• Fix package names by @alyphen in #187
• Fetch bstats from gradle by @alyphen in #188
• Refactor services by @alyphen in #189
• Use plugin logger for logging by @alyphen in #191
• Refactor commands by @alyphen in #192
• Apache 2.0 License by @dmccoystephenson in #193
• Add further event coverage & improve existing listeners by @alyphen in #194
• Non-Edible Item Spawn Fix by @dmccoystephenson in #195
• Fixed all crafted items getting timestamped. by @dmccoystephenson in #198
• Fix shift clicking resulting in loss of items, closes #197 by @alyphen in #199
• Store food expiry in the item's persistent data store by @alyphen in #200
• Made only edible items get assigned timestamps in the Block Cook Listener. by @dmccoystephenson in #201
• Switched over to using ISO_OFFSET_DATE instead of ISO_OFFSET_DATE_TIME. by @dmccoystephenson in #202
• Made rotten flesh not spoil. by @dmccoystephenson in #203
• Add RPKit integration by @alyphen in #205
• Parse errors are no longer logged to the console. by @dmccoystephenson in #206

New Contributors

• @alyphen made their first contribution in #186

Full Changelog: 2.1.1...3.0.0

Food Spoilage 3.0.0 Alpha Release - June 17th, 2022

What's Changed

• Switched over to using ISO_OFFSET_DATE instead of ISO_OFFSET_DATE_TIME. by @dmccoystephenson in #202
• Made rotten flesh not spoil. by @dmccoystephenson in #203

Full Changelog: 3.0.0-ALPHA-6-9-2022...3.0.0-ALPHA-6-17-2022

Food Spoilage 3.0.0 Alpha Release - June 9th, 2022

Note

Servers updating from pre-3.0.0 will need to delete their config.yml and restart the server to regenerate it.

What's Changed

• Non-Edible Item Spawn Fix by @dmccoystephenson in #195
• Fixed all crafted items getting timestamped. by @dmccoystephenson in #198
• Fix shift clicking resulting in loss of items, closes #197 by @alyphen in #199
• Store food expiry in the item's persistent data store by @alyphen in #200
• Made only edible items get assigned timestamps in the Block Cook Listener. by @dmccoystephenson in #201

Full Changelog: 3.0.0-ALPHA-5-25-2022...3.0.0-ALPHA-6-9-2022

Food Spoilage 3.0.0 Alpha Release - May 25th, 2022

Note

Servers updating from pre-3.0.0 will need to delete their config.yml and restart the server to regenerate it.

What's Changed

• Migrate to gradle by @alyphen in #186
• Fix package names by @alyphen in #187
• Fetch bstats from gradle by @alyphen in #188
• Refactor services by @alyphen in #189
• Use plugin logger for logging by @alyphen in #191
• Refactor commands by @alyphen in #192
• Apache 2.0 License by @dmccoystephenson in #193
• Add further event coverage & improve existing listeners by @alyphen in #194

New Contributors

• @alyphen made their first contribution in #186

Full Changelog: 2.1.1...3.0.0-ALPHA-5-25-2022

Food Spoilage 2.1.1 (Config Initialization Fix)

What's Changed

• Fixed config.yml not getting properly initialized upon startup. by @dmccoystephenson in #185

Full Changelog: 2.1...2.1.1

Food Spoilage 2.1 (Ponder Integration, Project Reorganization)

What's Changed

• Spoilage By Day by @dmccoystephenson in #180
• Reorganized the project. by @dmccoystephenson in #182
• Further project reorganization. by @dmccoystephenson in #183
• Ponder Integration by @dmccoystephenson in #184

Full Changelog: v2.0...2.1

Note

This version of the plugin doesn't work due to an error with config initialization.

Food Spoilage v2.0

Changes in Food Spoilage v2.0

• Undead_Zeratul overhauled some parts of the plugin, cleaning up the code.
• Undead_Zeratul fixed spoiled food always resulting in one food, rather than the number of items that spoiled.
• Integrated bStats into the plugin in order to collect usage data.
• Created an EventRegistry class to handle the creation of the EventHandler classes.
• Caibinus fixed players being able to remove timestamps from Wheat by crafting Haybales and then crafting Wheat from the Haybales.
• Caibinus fixed players being able to remove timestamps from Melons by crafting Melon Blocks and then crafting Melons from the Melon Blocks.
• Removed the Creation Date from timestamped items.
• Added the /fs timeleft command.
• Updated the plugin.yml and /fs command with no arguments to include other authors.
• Renamed the StorageManager class to ConfigManager.
• Overhauled the ConfigManager class to be a lot more like Medieval Factions
• Callum fixed the version not getting updated in Config.yml upon a version mismatch.
• Callum implemented a caching system for looking up food spoilage times.
• Incremented the version to v2.0 because for some reason the timestamps of existing food don't match the new system and there is a high chance of spoilage before reaching the expiration date for food items.

Food Spoilage v1.10-beta-1

Changes in Food Spoilage v1.10-beta-1

• Undead_Zeratul overhauled some parts of the plugin, cleaning up the code.
• Undead_Zeratul fixed spoiled food always resulting in one food, rather than the number of items that spoiled.
• Integrated bStats into the plugin in order to collect usage data.
• Created an EventRegistry class to handle the creation of the EventHandler classes.
• Caibinus fixed players being able to remove timestamps from Wheat by crafting Haybales and then crafting Wheat from the Haybales.
• Caibinus fixed players being able to remove timestamps from Melons by crafting Melon Blocks and then crafting Melons from the Melon Blocks.

Food Spoilage v1.9

Changes in Food Spoilage v1.9

• This plugin now uses a config.yml instead of .txt files for configuration.
• Config.yml now gets created if there isn't one.
• If save files from pre v1.9 are discovered, they will be loaded in and then saved in the new format. This means values you've changed before should transfer over.
• If there is a version mismatch, the config.yml will be saved as config.yml.old and a new config.yml with default values will be created.