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
Name the next decision, not only the rhythm
Mayo Lumberjack uses left-or-right chopping with branches and banded logs that take two hits. For a practice sequence, record the next visible branch, the side you chose, and whether a banded log changes how long that choice lasts. A repeated rhythm may stop matching the trunk when an extra hit is needed. Slow the review down to the individual decision that became unclear.
Use a rescue action deliberately
The documented whirlwind is a resource to spend when the tree becomes tricky. Before an attempt, choose a cue that would make you use it and note the chapter and kit you are testing. Keep a rescue decision separate from a claim that an upgrade guarantees a successful run. Stars, coins, and saved progress belong to the game; this worksheet records your reasoning without reading or changing a save.
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: In an imaginary branch sequence, a banded log requires a second hit before the trunk advances. The player records that state and checks the next branch again instead of blindly alternating. A whirlwind cue is written before the next attempt so the review can compare the intended decision with the actual response.
Try it here · No account needed
Your working notes
This worksheet does not send your writing to Mayo Lumberjack, 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 Lumberjack. 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.