Puzzle Arc

Quick overview

You mostly spend your time rotating curved arc pieces until their endpoints line up and form valid connections. The game frames this as Liora repairing order inside the Temple of Reflections, but the actual tasks are concrete: make the arcs connect in the correct order without leaving broken ends.

Each level is self-contained and built around the same set of interactions: rotate an arc, move an arc, and check whether the connections you created match what the stage expects. Some stages behave like a single continuous route puzzle, while others feel closer to assembling multiple smaller links that must be placed in a specific sequence.

The main pressure comes from information control. You can preview connections by holding, and you can reveal a clue with a hint button, but both are meant to be used sparingly rather than constantly.

Full controls breakdown

Tap/Click (Rotate): Selecting an arc and tapping/clicking rotates it in place. In practice, most pieces have a small number of meaningful orientations, so rapid rotation is usually faster than trying to reason out the final angle from the start. When a piece has asymmetric endpoints, one wrong rotation can look “almost correct,” so it helps to rotate until the endpoints visually match the neighboring sockets.

Drag (Move / connect): Dragging is used both for repositioning pieces and for building the intended chain of connections. On layouts where the arcs are already placed but misoriented, dragging tends to be minor. On layouts that present loose segments, dragging is the main way to assemble the route before fine rotation work.

Press and hold (Preview / reset segment): Holding is the game’s confirmation tool. A preview typically highlights or indicates which endpoints are currently compatible, which is useful when two arcs look aligned but are actually off by one step. The same hold action can also reset a segment depending on context, which matters if you have created a knot of partial connections and want to undo just that local area without restarting the entire stage.

Hint button (Light icon): The light icon reveals a clue. Hints are limited, so they function best as a verification step (for example, confirming a single critical arc orientation) rather than a full solution. If you spend a hint early on a low-impact piece, later stages with tighter layouts can feel much harder than they need to.

Menu / pause: The pause/menu control is mainly for stopping mid-stage. If a level requires several precise adjustments, pausing is also a way to avoid accidental inputs on touch screens, especially when the arcs are tightly spaced.

Level and stage progression

Progression is based on introducing constraints gradually. Early stages usually have fewer arcs and fewer ambiguous placements, so rotating pieces until they “click” into a sensible route works reliably. These first levels also teach the visual language: what a valid endpoint looks like, how close an almost-correct connection can appear, and how the preview responds to a correct link.

Mid-game stages tend to increase difficulty in two common ways. First, the board becomes denser, so a single arc can appear to match multiple neighbors depending on rotation. Second, the intended order of connections matters more, which leads to situations where you can form a clean-looking local connection that blocks the global solution.

A noticeable spike usually happens once the game starts mixing fixed arcs (that can only be rotated) with movable arcs (that must be dragged into place). At that point, solving becomes less about rotating everything until it matches and more about choosing which pieces belong to which section of the route. Runs on these levels often take 3–5 minutes because you spend time testing placements, previewing, then correcting one mistaken segment.

Later stages commonly hinge on one or two “key” arcs: pieces that look generic but have endpoints that only fit in one location once the rest of the chain is correct. If you are stuck late, it is often because one key arc is sitting in a plausible spot that is not actually valid for the full route.

Strategy and tips that actually help

Start by finding forced connections. Edges and corners typically have fewer neighbors, so an arc placed near a boundary often has only one or two orientations that can possibly work. Locking those down reduces the number of false matches in the middle of the board.

Use the hold preview as a test, not a crutch. A good pattern is: rotate or place two or three pieces, then hold to preview and confirm whether the chain still behaves consistently. If you preview after every single rotation, you will spend more time checking than solving. If you never preview, you can build a long chain that fails due to one early mistake.

When movable pieces are involved, group by shape before worrying about rotation. Even without explicit labels, you can usually separate arcs into broad types (tight curves, wide curves, near-straight segments). In many stages, the wide curves are the only pieces that can bridge larger gaps, so placing them first reduces guesswork.

• If a level has one obvious “start” or “anchor” node, build outward from it instead of assembling in the center.
• Rotate pieces in place until you see a matching endpoint shape, then drag only when you are confident the piece belongs in that region.
• Save hints for the moment you have two competing plausible solutions; a hint is most valuable when it eliminates a branch.

A practical rule that comes up often: if two neighboring arcs both seem to fit, the correct pairing usually keeps the overall route smooth rather than creating an abrupt S-turn. The game’s layouts tend to reward continuity, and sharp reversals are frequently a sign you are connecting the right endpoints in the wrong order.

Common mistakes and how to avoid them

The most common mistake is solving locally and ignoring the global chain. You can form several correct-looking micro-connections that leave a single unmatched endpoint somewhere else. If you reach a point where only one endpoint is “wrong,” do not keep rotating random pieces; instead, trace the route back to the last junction where you had a choice and reconsider that decision.

Another common issue is overusing resets. The press-and-hold reset function is helpful, but if you reset a segment every time it looks messy, you lose information about what did not work. It is often better to deliberately break one connection at a time and see what changes in the preview rather than wiping the entire local structure.

Players on touch screens often mis-drag when arcs are close together. The symptom is that a piece rotates when you meant to move it, or it moves a neighbor instead. If that keeps happening, pause briefly between actions and use smaller, more deliberate drags; the layouts with dense clusters are usually the same ones where a single wrong move can scramble multiple partial connections.

Finally, hints get wasted on early-stage uncertainty. If you are stuck in the first minute of a stage, it is rarely because you need a hint; it is usually because you have not identified the forced edge/corner placements yet. Hints pay off more after you have reduced the board to two or three plausible configurations.

Who this works for

This is a good fit for players who like spatial logic puzzles where the main action is manipulating pieces rather than searching for hidden objects or reacting quickly. The decisions are about orientation, adjacency, and order, and the game expects you to notice when a connection is visually plausible but structurally wrong.

It also suits people who prefer steady problem-solving over score chasing. There is no need for fast reflexes, but there is a real requirement to keep track of what you have already tested, especially in stages where multiple arcs have similar curvature.

Players who dislike trial-and-error may bounce off the mid-game, because some stages are easiest when you test two competing chains and use preview to confirm which one behaves correctly. On the other hand, if you like puzzles where the final solution looks clean and inevitable once it is in place, the later temple stages are built around that kind of payoff.

Quick Answers

How do I know if an arc connection is actually correct?

Use press-and-hold to preview the connection state. If two endpoints only look aligned but are not meant to connect, the preview feedback usually fails to confirm that link or shows the chain breaking at that point.

When should I use a hint?

Use a hint when you have narrowed the level to a couple of plausible configurations and need to eliminate one. Spending hints at the start tends to confirm pieces you could have solved by checking edges and forced placements first.