Building a solver for a puzzle game nobody had documented

When a game has no published mechanics, you end up reverse-engineering it — and the reverse-engineering is more interesting than the solver. Start by writing down what you observe, not what you assume My first notes were full of guesses: "the drop rate feels like one in ten". Useless.

Source: [Dev.to](https://dev.to/andystanly/building-a-solver-for-a-puzzle-game-nobody-had-documented-4jcf)