So, should "yafsF3" count the ferz-step toward the max range of 3? I tried this on the sandbox and it seems to just lock it up. My feeling is that it should probably count.
There definitely is a bug here, but yafsF3 should mean something entirely different. The rules for range toggling are that any range specs are dropped, and the basic atom undergoes slider <-> leaper conversion. So F3 converts to plain R (and the equivalent R3 would convert to F). So you should get (if it was not buggy) a two-leg move where the first leg is F3, and the second leg is R (with fs deflection, i.e. 45 degrees). That is, 1, 2 or 3 diagonal steps, followed by an unlimited orthogonal slide.
There is no way in XBetza to get a limited range in a continuation leg. Perhaps this is a mistake, as hook movers are not very common. So it might be better to apply a specified range to the final leg, rather than to the first.
Without range toggling (afsF3) the range is taken as the total. But that would not specify where it has to turn the corner; it could be 2xF + W or F + 2xW.
There definitely is a bug here, but yafsF3 should mean something entirely different. The rules for range toggling are that any range specs are dropped, and the basic atom undergoes slider <-> leaper conversion. So F3 converts to plain R (and the equivalent R3 would convert to F). So you should get (if it was not buggy) a two-leg move where the first leg is F3, and the second leg is R (with fs deflection, i.e. 45 degrees). That is, 1, 2 or 3 diagonal steps, followed by an unlimited orthogonal slide.
There is no way in XBetza to get a limited range in a continuation leg. Perhaps this is a mistake, as hook movers are not very common. So it might be better to apply a specified range to the final leg, rather than to the first.
Without range toggling (afsF3) the range is taken as the total. But that would not specify where it has to turn the corner; it could be 2xF + W or F + 2xW.