Closed Nico-Mayer closed 1 year ago
You are using it correctly!
It still outputs a list of moves for an already-solved cube because the solver is not that smart. It simply follows an algorithm that produces a solved cube, regardless of the initial state. It also doesn't attempt to produce a minimal/optimal solution. This means its solution sequences are quite long. While I originally planned to implement a better solver, I never got around to it and there are other libraries which produce much shorter and/or optimal solutions anyway.
First and foremost, great job! I have a question about the solver. I might be missing something here, or I could be using it incorrectly. In the example below, I input an already solved cube. My confusion is why the solver is generating a solving sequence for a cube that's already solved. Shouldn't the solver's "moves" array be empty in such a case?
Code:
Output: