Week 10 · Lab

Lecture theme: Digital media on a dying planet

Construct 3 Against Construct 3

Main question

What happens when we refuse what
the software expects us to make?

Remember the reframe from Week 7

An event sheet doesn't know what a “game” is.
It only knows conditions, actions and states.

The task's own words

Obligatory Task 7

“What you are creating today cannot be a game or gamified in any way.”

Start here

Open the Construct 3 homepage. What does it advertise?

Not this

Not: make a weird game.

Instead: identify one assumption in the software and refuse it.

Possible directions

Possible directions, continued

This is not hypothetical

Case study: Trail Mix

A shipped example of refusing Construct's defaults

Same lens, aimed at your own refusal

The four questions from Week 7 · now on your own work

Fill this in before you build

CONSTRUCT EXPECTS ME TO MAKE: ________________ I AM USING IT TO MAKE: ________________ THE EXPECTATION I AM BREAKING IS: ________________

Connect to the lecture, without forcing it

Does your work need endless accumulation?

Typical games reward

  • MORE
  • FASTER
  • BIGGER
  • HIGHER SCORE
  • MORE ITEMS
  • MORE LEVELS

What if the system values

  • LESS
  • WAITING
  • CARE
  • REPAIR
  • OBSERVATION
  • RETURN / SHARING / REFUSAL

Obligatory Task 7, submission

Construct 3 normally encourages ______. My work instead ______. I made this decision because ______.
Week 10, Construct 3 Against Construct 3
1 /