ik

Look at a rig's bones and at what an IK solve is actually doing.

Debugging IK means answering three questions, and none of them can be answered from a screenshot: what are this rig's bones called, where are they right now, and is the chain reaching its target or merely near it.

bones lists a body's bones with their world positions and parents — the names you need before naming a chain, and the positions you measure against when checking a solve from outside the component. Rigs rarely use the word you would guess: the standard humanoid here calls its feet Ankle_L and Ankle_R, with no bone containing "foot" anywhere.

reach reports how far a limb can extend and how far away a point is, both in the same units. A target beyond a limb's reach has no solution — the chain extends straight toward it and stops, which is correct and looks exactly like a broken solver. This is the first thing to check when a solve looks inert.

state gathers every IK component on an entity and reports what each one is doing, so "is anything solving at all" is one call rather than five.