WorldRulesManage

- Need to regenerate the configuration files in localRules.

- Need to regenerate the configuration files in localRules.

6.6 Remove redundant code and optimize! - Remove redundant code, now wrl reload speed is 100%. - If it has been updated and the configuration file is not frequently modified, you can ignore this update. WorldRulesManage 6.5 Performance Optimization and New Features! - Added the keepInventory game rule in globalRules. - Added animals, monster, and ironGolem options in the creatureSpawn rule in globalRules. - Optimized the listener logic: events already intercepted by globalRules no longer process localRules events, because once intercepted globally, handling locally is unnecessary (previously both were processed). - Improved the speed of /wrl reload and restarting the plugin when modifying the config.yml configuration file. - Added a keepInventory listener toggle option in config.yml. - Optimized the configuration file examples and descriptions. Some configuration items had spelling errors; we will not directly correct these, because if the old configuration is not cleared after an update, functionality may break. - Added soft dependencies for the plugin: [PlaceholderAPI, Multiverse-Core, LuckPerms, PlayerPoints, CMI, CMILib, Essentials]. New features and code refactoring! - Added many features—too many to describe in detail. - Optimized performance and introduced multithreading; previously used YAML, now switched to Java data types. - Added support for automatic internationalization; currently only English and Chinese are supported, as the author doesn’t have time to translate into every popular language. - Supports more customizable title-based notifications. - Each world’s rules are stored in a separate YAML file, so there’s no worry about overly long configuration lines. - Other features are left for you to explore."

A new fatalInjury option has been added under playerDamage (default: disabled). It does not prevent fatal damage (e.g., falling from a great height, /kill, etc.). Note: If you do not need the fatalInjury feature, you can ignore this update or update without making any changes. If you are upgrading from v5.2 to v5.3, simply add fatalInjury: true under playerDamage. A configuration example has been provided below.

   playerDamage:                                        # -> Prevent players from taking damage (e.g., no hurt or knockback)
      enable: true                                      #    Enable or disable
      fatalInjury: false                                #    Will not prevent fatal damage (e.g., high fall, /kill, etc.)
      message: "&cYou cannot be harmed in this world!"  #    Message shown when blocked (supports PlaceholderAPI). Comment or remove to show nothing.

Kind Reminder: If version 5.0 already meets the needs of your server, you may ignore this update! WorldRulesManage v5.1 adds support for using whitelist/blacklist in blockBreak and blockPlace to restrict the breaking and placing of specific blocks. Additionally, you will need to update the blockBreak and blockPlace sections in your configuration file. A configuration example has been provided in the update log.

blockBreak:
  message: "&cYou are not allowed to break blocks in this world!"
  type: WHITELIST
  list: []

blockPlace:
  message: "&cYou are not allowed to place blocks in this world!"
  list: []

Major Update: WorldRulesManage 5.0 Updating to this version requires deleting the previous configuration files and regenerating them. Now supports customizing messages for each world's rules individually. A new option to block entity spawning has been added to the global rules. World-level global rules now support always keeping the weather clear. Finally, the core logic has been optimized.