Always, Never, Not Sure

Week 6 · October 1 · 50 minutes left

  1. Spark
  2. Pre-production
  3. Production
  4. Playtest
  5. Polish
  6. Ship
  7. Launch

Today you write the class code of conduct for AI.

Not me. You. What a machine should always be allowed to do to your game, and what it should never do.

Key word

Code of conduct
The rules a group writes for itself and agrees to keep. You write this one, so it is yours.

48 left · On your own · Five minutes

On your paper. Just you. Finish each one.

AI should always be allowed to ______ for my game.
AI should never ______ my game.
I’m not sure about ______.

Grades 3–5: the first two. Put your name and today’s date on the paper.

43 left · With the people next to you · Five minutes

Put your lists together.

Disagree? Don’t fix it. Write it down as a disagreement.

Three or four of you. One shared list. You do not have to agree – you have to write down where you don’t.

38 left · The whole class · Argue

The class list.

Always OK

AI may do this for my game.

Never OK

AI may not do this to my game.

We couldn’t agree

Written down honestly, not hidden.

One rule is already in, and it is mine: no personal information into any tool. Ever. Yours or anyone else’s.

38 left · Argue about this

If AI draws your character, is it still your game?

38 left · Argue about this

Is asking AI to fix your bug different from asking it to write your event from scratch?

38 left · Argue about this

Is it different if you ask it for options, or ask it to decide?

38 left · Argue about this

If nobody could tell, would it matter?

38 left · If AI helped make it

If AI helped make your art, saying so in your credits is called attribution.

Whether that is enough is a real argument, and grown-ups are still having it.

Key word

Attribution
Saying what tools and help you used. If AI made your art, say so. It’s honest, and it’s normal.

30 left · Spark Break

Anything from today you want to come back to? Write it down, with where you saw it.
Star it if you want to ask me. I come to you first.

28 left · Studio

Want your score to go up? Your game needs a variable.

Make one number change on screen.

Score, lives, time left, gems collected. Pick one. Make something change it, then press Preview and watch it change.

Key word

Variable
A box with a name that holds a number or a word. Your game’s memory. Score. Lives. Time.

28 left · Studio

First, your folder. What was I in the middle of? What am I doing first today?
Got a number changing on screen? That is spec L2. Circle it and date it in pen.
Starred a spark? I am coming to you first.

Don’t tell me it works. Show me.

2 left · Ratify

This is our code.

Agree with it? Sign it on your way out.

We will read it again in November and find out where it was wrong.

2 left · Spec Check, fast

  1. Pencil on your My Game Contract✓ solid · ~ shaky · ✗ broken
  2. Got a bad answer from the AI today?It goes in your Failure Log.
Before you leave

Contract and today’s paper in your class folder. Folder on the cart. Sign the code.

Your “always, never, not sure” paper stays in the folder. In November you get to see what you thought today.

0 left · Next week

Next week I’m not here.

A substitute, paper work, and one of my favorite things we do all semester.

Star your sparks anyway. I’ll get to every one of them when I’m back.