• Performance improvement
• Although the performance of the plug-in has always been very good, I always believe that there is still much room for improvement. I did this in 3.4 and achieved better results than I expected.
• ① 7,000% increase in serialization speed (tested with 100,000 crops in a single chunk)
• ② Only occupies 8% of the original storage file size
• ③ More efficient scheduler, although 3.3 is also running in multithreading, the thread execution efficiency of the new version has been improved
• Random Tick System
• Now random tick scheduler has been added to the scheduler system. Before, many users hoped that I could make rain able to water the pot and I did this through the random tick system. Moreover, the random tick can also be applied to crops. You can see the differences between them here (Link)
• Support more item Libraries
• Previously, some users wanted to use water bottles and seeds from other plug-ins, which are now supported!
• Richer action system and condition system
• Richer action system makes force tick possible. In the default configuration, we allow players to force the sprinkler to work while sneaking. We convert all the hard coded functions into configurable actions.
• Slime world manager support
• We added official support for slime world manager, which means that the plugin would store the data into slime world format, thus allowing you to sync worlds with MongoDB and MySQL.
• Folia support
• Although itemsadder and oraxen do not officially support Folia, customcrops has been prepared in advance and can be run on folia at any time!
• Improvements in more details
• For example, for servers above 1.19.4, we use text display by default to improve interactions. We introduced more accurate hitbox detection and judgment for adding water to the watering-can. There are many details improved, but I don't think it's necessary to explain them in detail in the update log.
• About upgrading plugins from 3.3 -> 3.4
• I know that users are suffering from the migration plug-in configuration writing to the new version, so you only need to replace the plugin jar to complete the migration of the configuration file and the existing crop data without any other operations. (Link)