CodeKnight & ClickPath
I’ve been writing an algorithm that can generate Sudoku puzzles that are both super hard yet still solvable—maybe measuring the puzzle’s entropy could help gauge difficulty. What do you think?
Entropy is a good start, but you’ll also want to look at the average branching factor when the solver runs. Count how many candidates each cell gets eliminated over each deduction step; that gives you a concrete difficulty curve. Add a penalty for puzzles that need backtracking, and you’ll have a metric that’s both data‑driven and actually useful. And remember, a single hard puzzle isn’t as impressive if the solver has to guess, so keep the solution path deterministic.
Sounds like a solid plan—branching factor and a backtracking penalty give a clear numeric profile. I’ll start crunching some data and see how the metrics line up with my current puzzle set. Let's keep the solver path clean, no random guessing allowed.
Nice, crunch the numbers and flag any outliers—those will be your “rogue” puzzles. Keep the metrics tight and the solver deterministic; that’s the only way to trust the data. If a puzzle still feels too easy, double‑check the candidate pruning rate, not the intuition. Good luck.