修复部分情况下配置未加载的问题

common-files/src/main/resources/config.yml

@@ -145,14 +145,36 @@ resource-pack:
 
 item:
   # [Premium Exclusive]
-  # Make custom-model-data and item-model clientside by default
+  # Makes custom-model-data and item-model client-side by default.
+  #
+  # This provides several benefits. For example, you can update model values
+  # dynamically without causing inconsistencies for players' existing items.
+  #
+  # The main drawback is that plugins relying on custom-model-data for item
+  # identification will not work correctly, as this data is not present in
+  # the server-side item stack.
+  #
+  # You can override this global setting per item using the
+  # client-bound-model option.
   client-bound-model: true
-  # Add a <!i> tag on custom name and lore
+  # When enabled (recommended), this option adds both custom-model-data
+  # and an item-model to optimize client-side rendering.
+  #
+  # If disabled, the system falls back to using only custom-model-data.
+  # You can override this behavior by setting the item-model option
+  # on a per-item basis.
+  #
+  # This option only works if your resource pack supports 1.21.1 or below
+  always-use-item-model: true
+  # Since Minecraft renders lore text in italics by default, you can
+  # optionally prefix any lore with <!i> to remove the italic formatting.
   non-italic-tag: false
-  # Determines when to trigger the item updater
-  # This feature may incur some performance overhead. Please do not enable it unless necessary.
-  # Correct use case: When you designed incorrect weapon attributes and need to update the values for items already held by players.
-  # Wrong use case: When you want to update an item's name and lore to a newer version (In this case you should use client-bound-data instead of the item updater)
+  # Defines the trigger condition for the item updater.
+  #
+  # Warning: This operation is performance-intensive. Enable only if needed.
+  #
+  # Purpose: Reserved for correcting faults on existing player items.
+  # Not intended for updating names/lore; use 'client-bound-data' for those changes.
   update-triggers:
     click-in-inventory: false # this option won't work for players in creative mode
     drop: false
@@ -175,29 +197,31 @@ equipment:
     humanoid-leggings: minecraft:trims/entity/humanoid_leggings/chainmail
 
 block:
-  # This decides the amount of real blocks on serverside. Requires a restart to apply.
-  serverside-blocks: 2025
+  # This decides the amount of real blocks on serverside. You should only consider increasing this value when your server state is insufficient.
+  # It is recommended to increase it by 500 each time. This option requires a restart to apply.
+  serverside-blocks: 2000
   # Enables the sound system, which prevents the client from hearing some non-custom block sounds and improves the client experience.
   sound-system:
     enable: true
-  # In Adventure Mode, players need the correct tool to break custom blocks.
-  # Vanilla clients DO NOT recognize custom block IDs (e.g., craftengine:note_block_0).
+  # Adventure mode requires correct tools to break custom blocks.
+  # Vanilla clients cannot recognize custom block IDs (e.g., craftengine:custom_100).
   #
-  # - When ENABLED:
-  #   - Players can break custom blocks if their tools can mine their VANILLA EQUIVALENTS.
-  #     Example: A tool for "note_block" can break "craftengine:note_block_0".
+  # ENABLED:
+  # - Tools that can break vanilla equivalents also break custom variants.
+  #   Example: A "note_block" tool breaks custom blocks based on note blocks
   #
-  # - When DISABLED:
-  #   ⚠️ WARNING:
-  #   - Server MUST list ACTUAL CUSTOM BLOCK IDs in item's `can_break` component.
-  #   - Sending custom IDs (e.g., craftengine:note_block_0) to vanilla clients WILL CRASH THEM!
-  #   ✅ Solution:
-  #   - Use `client-bound-data` to safely sync custom block data to clients.
+  # DISABLED:
+  # ⚠️  Server MUST specify SERVERSIDE CUSTOM BLOCK IDs in item's `can_break`.
+  # ⚠️  Sending custom block IDs to vanilla clients WILL CAUSE CRASHES!
+  # ✅  Recommended: Use `client-bound-data` for safe client synchronization.
   simplify-adventure-break-check: false
   # Similar to the option above, but designed for block placement
   simplify-adventure-place-check: false
-  # Whether plugin should predict the next block to break
-  # This can help improve mining experience to some extent at the cost of performance
+  # Uses raycasting to predict the player's next block break,
+  # enabling pre-calculation of mining speed attributes.
+
+  # Enables block break prediction.
+  # Enhances mining responsiveness with moderate performance cost.
   predict-breaking:
     enable: false
     interval: 10

common-files/src/main/resources/resources/default/configuration/templates.yml

@@ -933,7 +933,7 @@ templates#block_states:
           resistance: 1200.0
           burnable: false
           fluid-state: water
-      distance=7:
+      distance=7,persistent=false:
         settings:
           is-randomly-ticking: true
   # trapdoor block