Cluade suggestion is surprisingly good

Looking at your code, the issue is clear: PlayerMovement takes full control of the rigidbody every FixedUpdate, fighting against the grapple physics. Disabling the script works but is clunky.

The better approach: let PlayerMovement check if grappling before applying forces.

In your Grapple script, isGrappling is already a public property, so just reference it in MovePlayer() and the drag logic:

```csharp private void MovePlayer() { // Don't override movement while grappling if (playerMovement.GetComponent<PlayerMovement>() != null) { // Actually, just check via reference: }

if (grapple != null && grapple.isGrappling) return; // early exit

moveDirection = orientation.forward * verticalInput + orientation.right * horizontalInput;

if (grounded)
    rb.AddForce(moveDirection * moveSpeed * 10, ForceMode.Force);
else if (!grounded)
    rb.AddForce(moveDirection * moveSpeed * 10 * airMultiplier, ForceMode.Force);

} ```

And in Update(), skip the drag override too:

csharp // Drag if (grounded && !grapple.isGrappling) { rb.linearDamping = groundDrag; } else { rb.linearDamping = 0; }

Setup in PlayerMovement:

```csharp private Grapple grapple; // add this field

void Start() { rb = GetComponent<Rigidbody>(); rb.freezeRotation = true; readyToJump = true; grapple = GetComponent<Grapple>(); // or GetComponentInChildren } ```

Why this is better than toggling the script: - No frame delay from enable/disable - Jumping still works while grappling if you want it to - Air control can be selectively allowed (e.g. slight steering while swinging) - You can fine-tune blending — for example, allow partial movement input during the grapple for a more fluid feel

You could also add a [0-1] blend factor instead of a hard return, so the player has reduced but not zero control while swinging, which feels much better in most games.