A free decision log for a focused practice session, based on the game’s documented mechanics.
Published October 15, 2026 · Programming Securely · Original exercise with illustrative examples
Compare immediate collection with a special
The documented board supports adjacent swaps, matches of three, and different specials from larger shapes. Before a practice move, name the current ingredient goal and compare one direct collection with one possible special. Do not assume the largest-looking match is best for the current recipe. Write down the visible alternatives before making the move so a later cascade does not make the original choice look more obvious than it was.
Track the mixer as a separate resource
Following the displayed ingredient order charges the mixer, and a charged mixer clears a selected row without a move. Record whether the mixer was charged and what a selected row would contribute to the visible goal. This exercise is about explaining a decision from the board you see. It does not simulate falling pieces, predict a cascade, or establish an optimal solution for a seed.
Compare one decision in the build you actually use
Record the version, stage, controls, and relevant kit or resource state before comparing attempts. Change one decision when possible and write the actual response separately from your prediction. A useful practice note explains what you learned and what is still unclear. Public release availability and platform support remain as stated on the homepage; this worksheet does not launch the game, connect an account, read cloud saves, or submit a score.
Worked example
A small situation to try
Illustrative exercise: On an imaginary board, a player sees a direct ingredient match and a four-piece match that could create a line special. They note the recipe goal and remaining moves, then describe which choice they would test and why. After the move, they record the actual cascade separately from their prediction.
Try it here · No account needed
Your working notes
This worksheet does not send your writing to Mayo Candy, save it to an account, or store it in your browser. Notes are cleared when you leave or reload this page. Download a text copy if you want to keep them.
Identify the exact situation and version you intend to review.
Describe the information visible before the decision.
Write your intended action and why you chose it.
Separate the observed result from your prediction and choose one next question.
What to do next
Use what you learned
Check the homepage’s controls and current availability before a practice session.
Keep the version and relevant setup beside your observation.
Return to the product for its current features and availability. This independent worksheet changes no account data.
About this guide
Published by Programming Securely for Mayo Candy. Product descriptions are checked against this project’s documentation. Examples are fictional and are kept separate from observed product behavior. The worksheet helps you prepare a note; it does not replace the product’s current documentation.
For a correction, use the product’s contact or support link on its homepage and name this guide and the passage that needs review.