SET the Perimeter
(Published on 28. August 2022, 18:28 by EricRathbun)
- Normal Sudoku Rules apply.
- Normal Killer Cage rules apply.
- Digits separated by a black dot are in a 1:2 ratio. Not all dots are given.
- Gray lines are Palindromes which read the same frontwards and backwards.
- Digits separated by a knight's move in chess do not repeat.
The puzzle can be played here:
Hope you enjoy the puzzle. Comments appreciated.
Solution code: Row 3
Comments
on 20. February 2026, 03:40 by EricRathbun
added link
on 19. February 2026, 17:38 by snuuba
Dedided to give my brain a break after yesterdays 5 star monster. Not sure why such low rating, I quite enjoyed it. Many thanks for sharing.
Response from Eric:
snuuba, this must have seemed easy after the last one you did.
CtC link:
https://sudokupad.app/e6wwwqvv9a
on 15. December 2024, 02:06 by PinkNickels
It's interesting how puzzle difficulty has changed over the last two years. This is a 2*, but it took me under 6 minutes. Not bragging, just saying this would be a 1* today. The community as a whole has gotten so much better at solving in the last two years, it's incredible.
---
Response from Eric:
I agree. The Sudoku community has improved at solving puzzles, even with the challenges of new rule sets being introduced.
__________
Thanks for the response. I wonder if we are getting enough new folks into the hobby. Obviously, the emergence of CtC on YouTube had a huge impact on new solvers (myself included), but I'm sure the rate of new solvers has decreased quite dramatically. I hope the number of solvers and setters doesn't start to decrease.
on 25. February 2023, 12:06 by Aphyrus
Very nice, thank you :-)
---
Response from Eric:
Glad you liked it, Aphyrus.
on 15. November 2022, 14:44 by chain.reader
This was good, I too thought I'd need set but just after colouring I ended up not using the set at all.. it became much easier near the end *after* I remembered the Knights move restriction :/
---
Response from Eric: chain.reader, yes the puzzle turned out to be easier than I intended with SET not being needed, however as you experienced it would be quite difficult to solve without using the knight's move restriction. I could definitely see myself doing that. :)
