'F' → Fullscreen

Build

Copy the template your plan needs to 1-25-artifact. Almost everybody wants template-game.

1
-- 1-25-artifact / main.lua
2

3
-- variables
4

5

6
function love.update(dt)
7

8
end
9

10
function love.draw()
11

12
end
13

14
function love.keypressed(key)
15
    if key == "escape" then
16
        love.event.quit()
17
    end
18
end

Stage 1 — Something on Screen (target: 15 minutes)

The smallest thing from your plan that draws and responds. One shape, moved by the keyboard or the mouse:

1
local x = 400
2
local y = 300
3

4
function love.draw()
5
    love.graphics.circle("fill", x, y, 30)
6
end

Run it. Then copy the folder to 1-25-stage1.

Stage 2 — The Table and Your Function (target: 30 minutes)

Two things, and they are the graded ones:

• The table. Positions, sizes, states — whatever your plan said. The program has to break without it.
• Your function, with parameters, called from more than one place, with a decision and a loop in its body.

Run it. Copy the folder to 1-25-stage2.

If your function has no natural loop in it, draw something in a loop — rings, a row of pixels, a health bar of N segments. That counts and it looks better than the version without.

Halfway Check

Stage 3 — Make It a Thing (target: the rest)

Whatever your plan called for. In rough order of value:

1. An ending — a win, a loss, a timer running out
2. A score or a counter that is correct
3. Something that tells the player what to do
4. Color, size, and spacing that look deliberate

A counter that counts once per event and not once per frame is session 14. If yours is climbing on its own, that is the bug.

Last Ten Minutes — Stop Building

No new features in the last ten minutes. Instead:

• Run it three times and try to break it
• Check every requirement on your plan is actually there
• Check Escape still closes the window
• Delete code you did not end up using
• Make sure the folder you are submitting is the one that runs

Last Twenty Minutes — The Gallery Walk

Leave your program running and go and look at everyone else's. Play at least five. Record three:

Tonight

Written Response: Your Creative Artifact is homework, and it is due on paper at the start of the exam session. You will not have a computer that period.

Checkpoint

• 1-25-artifact runs, and runs from a fresh start
• Something moves or responds to the player
• Keyboard or mouse input works
• A table is used, and the program breaks without it
• Your own function takes parameters and is called from more than one place
• A decision and a loop are inside that function's body
• Escape closes the window
• At least one saved stage folder exists
• Three programs recorded from the gallery walk

Reflection

Answer the following questions before submitting your work.

1. Describe the point today where the program was furthest from working. Say what you did, and whether the plan or the code turned out to be the problem.
2. Did you take the cut you named last session? Explain the decision either way, and say what you would build first if you had another hour.
3. Name one thing you can do now, without looking anything up, that you could not do at session 13. Point at the line in your own program where you did it.

Submit

Submit the whole 1-25-artifact folder. Keep your stage copies, and keep the program itself — you write about it tonight, from memory, with the editor closed.

Activity Complete