Merge branch 'Xiao-MoMi:dev' into dev

common-files/src/main/resources/resources/internal/configuration/fix_client_visual.yml

@@ -3,22 +3,40 @@
 items:
   minecraft:string:
     client-bound-data:
-      components:
-        minecraft:block_state:
-          attached: 'false'
-          disarmed: 'false'
-          east: 'true'
-          north: 'true'
-          powered: 'true'
-          south: 'true'
-          west: 'true'
+      $$>=1.20.5:
+        components:
+          minecraft:block_state:
+            attached: 'false'
+            disarmed: 'false'
+            east: 'true'
+            north: 'true'
+            powered: 'true'
+            south: 'true'
+            west: 'true'
+      $$fallback:
+        nbt:
+          BlockStateTag:
+            attached: 'false'
+            disarmed: 'false'
+            east: 'true'
+            north: 'true'
+            powered: 'true'
+            south: 'true'
+            west: 'true'
   minecraft:note_block:
     client-bound-data:
-      components:
-        minecraft:block_state:
-          instrument: harp
-          powered: 'false'
-          note: '0'
+      $$>=1.20.5:
+        components:
+          minecraft:block_state:
+            instrument: harp
+            powered: 'false'
+            note: '0'
+      $$fallback:
+        nbt:
+          BlockStateTag:
+            instrument: harp
+            powered: 'false'
+            note: '0'
 # For the client to determine if a beacon can activate, it needs the beacon_base_blocks tag to render the beam.
 # This allows custom blocks (like note blocks) to work as beacon bases.
 # However, whether the beacon actually grants potion effects depends on the block's real tag (server-side check).