Yoke is the fourth co-op game in our TwozyGames Originals lineup, and the one that divides the thing you are actually playing. There is one body on the field. One of you owns its left and right, the other owns its up and down, and neither of you can borrow the other's. We wrote the code, so this guide can tell you exactly what the game is measuring — including why the most common way to lose is not being slow, but being busy.
Two axes, two distances
Both axes run at full speed at the same time, so a diagonal costs nothing extra. That single rule is the whole strategy layer, because it means the two of you travel by a different measure of distance depending on whether you agree.
Push together and the trip takes as long as the larger of the two gaps — the sideways one or the up-and-down one. Take it in turns, one axis at a time, and the trip takes the two gaps added together. Over random target placements that is 1.44x the travel time on average and exactly twice as long in the worst case, which is any target sitting on a perfect diagonal from you. Nothing about that is tuned; it is simply what the two ways of moving cost. Agreeing is not the polite option, it is the fast one.
The failure that looks like movement
Now the part that catches every new pair. Two targets are live, one carrying each of your numbers. You want yours, your partner wants theirs, so you drive your axis at your target and they drive theirs at theirs. Both of you are pushing. The body is moving at full diagonal speed. And it arrives at a spot where there is no target at all.
It has to. Your keys only ever close the sideways gap to your target; theirs only ever closes the up-and-down gap to theirs. So the body heads for the point that shares your target's column and your partner's row — a place neither of you was aiming at, and neither of you was doing anything wrong on your own. If the two targets sit in opposite corners, that pair of perfectly reasonable decisions banks nothing at all. Pick one target, both drive it, then swap.
Letting go is not yielding
The obvious way to give in is to stop pushing and let your partner have the body. It does not work, and it is worth understanding why before you spend a wave on it.
A target is only reached when the body lines up on both axes. If you release your axis, that axis simply stops where it is, and your partner's target stays out of reach unless it happens to sit level with wherever you left the body. Over random placements that is true about one time in ten. Driving your partner's target instead reaches it every time. Conceding a target is an action, not the absence of one.
The ring is a fraction, not a clock
Each target's countdown is set from the time a pair moving perfectly would need to reach it, plus a fixed grace of about three quarters of a second. Far targets therefore start with more seconds than near ones, and the ring on screen shows the fraction remaining rather than the seconds.
That has a practical consequence when you are comparing the two: two rings drained to the same point do not have the same time left, and the far one is usually the healthier of the pair. When both are getting short, the one to save is normally the near one — not because its ring looks worse, but because it is the cheaper errand and buys the other some of the trip back.
Order is most of the game
Because the clocks are set from distance, you are almost never asked whether you can reach a target. You are asked whether you can reach both before either runs out, and that is decided by which one you take first. From the middle waves onward, the order alone decides the outcome in more than half of the placements we measured — the same two targets, saved or lost depending on nothing but the sequence.
So say the order out loud and say it early. And say the target rather than the direction: "top left" tells your partner where to push and why, while "left" is half a plan and they will spend their axis on the wrong errand. The waves are not neutral about this either — as they go on, the game deliberately places the two targets in opposing quadrants more and more often, so the calls get sharper rather than merely faster.
One tiebreak worth agreeing on in advance: a wave needs four of each colour, so whoever is further behind on their four should win the ambiguous calls. A seventh amber is worth nothing while azure is sitting on two.
Solo is a different job
Alone you own both axes, on WASD or the arrow keys, with the same waves and the same clocks. Nothing has to be agreed, so solo is where you learn how much time a ring really gives you and how much ground a diagonal covers. It is a good half-hour. It is not the game the design is about, which only exists when the two halves of one body want different things.
The short version
- Diagonals are free. A route that keeps both of you pushing beats the one that looks shorter.
- Both of you pulling at your own target sends the body where neither target is.
- Yielding means driving your partner's target, not releasing your keys.
- Rings show a fraction, not seconds — the far target usually has more time than it looks.
- Decide the order out loud, and name the target rather than the direction.
- Whoever is behind on their four wins the close calls.
If you like this one, the rest of the co-op shelf is in the best co-op browser games, and games to play with your partner covers the ones that do not turn into a reflex contest.
