Arrow Escape

Three arrows, one order

Picture a single row holding three arrows, all pointing right. The one nearest the right edge has open board in front of it, so a tap sends it flying off. The middle arrow was blocked a moment ago, but its lane is clear now, so it goes next. Then the last one follows. Three taps, and only one order works. That is the entire game in miniature. Every level is the same idea scaled up and tangled across rows and columns at once, with arrows pointing four ways instead of one.

The rule underneath: tapping an arrow launches it straight off the board in the direction it points, but only if no other arrow stands anywhere along that straight line to the edge. A blocked arrow just bumps and stays put. So the puzzle is never about which arrows to remove. All of them go. It is purely about order: which arrows can leave right now, and which ones are you clearing a runway for.

Work from the edges in

Read the board like a set of crossing lanes. An arrow pointing right needs its entire row to the right empty; a downward arrow needs a clear column below it. Arrows sitting near the edge they face tend to have the shortest paths, so fire those first, and each departure opens lanes for the arrows behind it. A tidy way to scan: sweep each row for sideways arrows with clear exits, then each column for vertical ones, taking every free move you find. Once the free moves are spent, the board is smaller and a new set of free moves has appeared.

Arrows aimed into the middle of a busy grid are usually the last ones able to leave. Treat the most-blocked arrow as the knot: look at what stands in its lane, then at what blocks those blockers, and you have read the solution backwards. Solving from the stuck end is often faster than hunting forwards. Keep a rough count as you clear, too: watching forty arrows become twenty tells you which region of the board the level actually hinges on, because the stubborn cluster that refuses to shrink is where your ordering problem lives.

A knot, untied

Here is a slightly bigger example. An up arrow sits in the centre with a left arrow directly above it, and the left arrow's row is clear. The up arrow is blocked; the left arrow is not. Fire the left arrow and the column above the up arrow opens, so it leaves next. Now suppose a right arrow elsewhere in the up arrow's row was blocked by that very tile. The moment the up arrow departs, that lane opens too. That is a chain of three where only the first link was free at the start. Real levels hide chains like this everywhere, which is why one careful look at a stuck arrow's lane, then its blocker's lane, pays better than a dozen hopeful taps.

When you are stuck

• Scan the whole line an arrow will travel, not just the tile in front of it. One arrow far across the board is enough to jam the shot.
• When two arrows block each other's routes, find the third arrow whose exit frees one of them, and start there.
• Freed a corner? Re-check every arrow pointing at that corner, because corners clear whole lanes at once.
• If a level feels locked, you probably fired an arrow that should have waited. Note which lane is jammed and free its blocker earlier on the next pass.

Honest talk about brute force

There is no penalty for tapping a blocked arrow, so yes, you can grind through a level by tapping everything over and over: each pass clears whatever has become free, and eventually the board empties. It works. It is also the slow way, and it teaches you nothing you can use when the grids get dense. Later levels pack in so many arrows that a player who reads lanes clears them in a fraction of the taps, and the real reward the game is built around is firing a dozen arrows in one unbroken chain, each departure freeing the next. There is no timer breathing down your neck either way. The tangle is the whole opponent, and beating a level means one thing: every arrow gone, the grid completely empty.