fix: (rotation) unwrap the silent yaw at the packet choke point so AimModulo360 sees no seam jump

The mixin-level continuous-offset attempt is undone by onPacket, which rewrites every outgoing rotating packet as packet.rotation = currentRotation (the engine may hold a wrapped [-180,180] yaw). Grim then sees a ~360 seam jump and flags AimModulo360. Apply the unwrap here, the single send choke point for both the Modern and Legacy engines: send the yaw as the shortest continuous offset from the last yaw the server received (serverRotation + angleDifference), so the packet delta is always <= 180 and never a seam jump.

Author: opZywl

src/main/java/net/ccbluex/liquidbounce/utils/rotation/RotationUtils.kt

@@ -967,7 +967,12 @@ object RotationUtils : MinecraftInstance, Listenable {
         }
 
         currentRotation?.let {
-            packet.rotation = it
+            // Send the yaw as the shortest continuous offset from the last yaw the server received, so
+            // the packet delta is always <= 180 and never a ~360 seam jump (GrimAC AimModulo360). The
+            // engine may carry a wrapped [-180, 180] yaw internally; the wire must stay continuous like
+            // vanilla's accumulating yaw. This is the single choke point for both rotation engines.
+            val continuousYaw = serverRotation.yaw + angleDifferences(it, serverRotation).x
+            packet.rotation = Rotation(continuousYaw, it.pitch)
             // The network tail hook releases post-move actions only after this packet actually sends.
             PostRotationExecutor.markRotationPacket(packet)
         }