thank you everyone for solving! I did something (perhaps needlessly?) fancy for this one using "roping". i had a quick search in the forum to see how often this concept has been discussed but didn't see much, so i should probably provide an explanation of it too:
- Code: Select all
+-------+-------+-------+ +-------+-------+-------+
| . . . | A A A | . . . | | b b b | A A A | c c c |
| A A A | . . . | . . . | -> | A A A | c c c | b b b |
| . . . | . . . | . . . | | c c c | b b b | a a a |
+-------+-------+-------+ +-------+-------+-------+
+-------+-------+-------+ +-------+-------+-------+
| . . . | B B B | . . . | | c c c | B B B | a a a |
| A A A | . . . | . . . | -> | A A A | c c c | b b b |
| . . . | . . . | . . . | | b b b | a a a | c c c |
+-------+-------+-------+ +-------+-------+-------+
when looking at a band or stack, if two minilines contain triples with either entirely the same, or entirely different clues, the whole band/stack will become "roped", meaning that every miniline within the tier will contain predictable triples
- Code: Select all
+-------+-------+-------+ +-------+-------+-------+ +-------+-------+-------+
| 5 . . | . . . | . . 3 | | b b b | c c c | a a a | | . . . | . 9 9 | 9 9 . |
| . 3 2 | . . . | 7 8 . | | a a a | b b b | c c c | | 9 . . | . 9 9 | . . . |
| . . . | 1 2 3 | . . . | | c c c | a a a | b b b | | 9 . . | . . . | 9 9 . |
+-------+-------+-------+ +-------+-------+-------+ +-------+-------+-------+
in this puzzle r123 are nearly roped, but the positions for 9 in these rows could not be placed in the same letter group
after determining roping isnt possible here, there is an easy elimination:
-1r2c1 lcstte
might be an idea worth further exploration, but this is all i could come up with for now