How to Handle Comparison Clues in Profile Perfect
Comparative clues never hand you an answer — they hand you an order. Learn to read their direction correctly, convert them into sorted lists, and squeeze eliminations out of even a partial ordering.
The direction trap: who is older than whom?
The single most common comparison error is reading the subject backwards. "The clock is older than the lamp" means clock → older, lamp → younger. Your eye wants to flip it; slow down and name the older item out loud before writing anything. A useful physical habit: draw an arrow from the comparative word toward the item that holds the property. "Older than" points at the clock. "Worth more than" points at whichever item the sentence says is worth more. One misread direction corrupts the entire sorted list built on it.
The standard move: build a sorted list
Never solve comparisons one clue at a time inside the grid. Collect every comparison on one axis — say, age — and lay them out as a line on paper: oldest on the left, youngest on the right. Place the clues as arrows between items. The line converts scattered inequalities into visible structure: gaps reveal themselves, and items with only one open slot snap into place. Redraw the list every time a new comparison lands on that axis; the redraw takes seconds and catches order mistakes early.
- One axis, one line — Age, worth and rarity each get their own list. Never merge them.
- Draw extremes first — "Oldest" and "newest" statements pin the endpoints; everything else hangs between them.
- Redraw on every update — A fresh copy of the list catches contradictions a messy one hides.
Partial orders still eliminate
You rarely get a complete ordering, and you do not need one. A partial order is already a weapon: if the clock is older than the lamp and the vase is the newest, the clock and the lamp cannot occupy the newest slot — two eliminations from two clues. Before touching the grid, walk each sorted list and ask for every item: which slots has this ordering already ruled out? Then carry those eliminations into the grid as pencil marks. Partial orders eliminate more than they look like they should.
Watch for deliberate ties
Some boards include two items that share an extreme — two cheapest, two oldest — and the clues will still read naturally. If your sorted list insists every gap is a strict inequality but the grid refuses to close, suspect a tie. The tell: two items that never appear in any comparison against each other, while everything else does. When you find such a pair, treat them as level at the top or bottom of the list and let the other rows decide which is which.
Never mix two axes into one order
The classic self-inflicted wound: assuming the worth order matches the age order. A board where the oldest item is worth the least is a clue, not a default. Each attribute gets its own sorted list, and links between two lists must come from an explicit clue or a confirmed grid cell. If you catch yourself sliding an item along one list because of its position on another, stop and ask which clue authorizes that move. Usually the honest answer is: none.