Stafffall

A note from the workshop

Finding the fireball

How notebook battles, several experiments, and one satisfying throw became Stafffall.

A notebook can contain a whole battlefield

As a child, I drew castles, little people, magic, destruction, and dragons on notebook paper. The drawings were only part of the game. Narration and sound made the action happen; I could change sides or invent a new problem whenever the scene needed one.

In autumn 2026, that memory became a starting point for several game experiments. I tried tactical battles, castles, spells, combinations, and drawing-based ideas. The most immediate discovery was a smaller action. Move a staff and throw a fireball.

What a new player could see

A September play session showed a gap between how I understood the cast and how a new player understood it. Successful throws were enjoyable, but the connection between cursor movement, staff motion, and release speed was unclear. Unexpected falls and repeated restarts got in the way.

That feedback gave me specific design problems. The introduction needed to help a player try the motion, see what affected a throw, and recover from a failed attempt.

What happened between attempts

October's progression work separated an attempt from the longer climb. The first run introduced the action before upgrades. After death, saved progress could preserve the stage and remaining enemies without paying the same rewards twice.

This was a development milestone. A September test had put the game in front of someone outside the development process, and October brought more work on the next attempt. The project page carries the current build and later changes.

This project note was compiled with AI assistance from personal development records. It is a retrospective, rather than a post originally published at the time.

A few places to start