Fight logs

Twelve recorded fights reconstructed as turn tables across the semester, marked on whether a reader can replay the fight from the table alone

Due: 14 May 2027 · Weight: 20%

A running log rather than a piece of work you start near the end. You build one table a week, all semester, and hand in the whole spreadsheet once.

What you hand in#

One spreadsheet, twelve sheets, one per teaching week.

Each sheet is a table with a row per action: actor, command, target, and the round or tick it landed in. Above the table, the recording’s name and the timestamp you started from, so a marker can open the same footage.

Below it, a short list of the rows where the turn order surprised you, one sentence each saying which rule explains it.

The capability it tests#

Week 1’s, exactly: diagramming who acts, in what order, and naming what the game had to decide to make that happen. Nothing later is examined here — a week 9 sheet is marked the same way as a week 1 sheet.

What changes across the semester is the fights, not the standard. By week 8 you are logging a break gauge and a stagger window, and the table still has to let somebody else replay it.

Marking bands#

Strong. A marker closes the recording, reads your table top to bottom, and can say at every row what else could have acted and why it didn’t. The surprise list names real rules — a priority bracket, a rank cost, a tie order — and at least one entry admits you had the order wrong the first time.

Adequate. The tables are complete and accurate, and a reader can follow what happened but not always why that actor and not another. Surprises are noted but explained loosely, or only in the weeks where the answer was easy.

Weak. Transcription. Rows read “Tidus attacks” with no state alongside, so the table records the fight without reconstructing it. Missing sheets, or a surprise list that is empty for twelve weeks — nobody reads twelve fights without being wrong once, so an empty list means you weren’t checking.

When it’s due, and what happens before#

The deadline is at the top of this page. One hand-in, at the end.

The sheets themselves are due weekly in the sense that the following week’s session assumes the previous one is finished — week 2 builds its counter model against the table you made in week 1. Falling behind costs you the session, not marks, but the sessions are where the tables get better.

Bring the running spreadsheet to any session and it will be read. A table looked at in week 3 is worth more to you than the same table looked at in week 13.