How today works
TODAY
THURSDAY — Scripts / Behavior
You are working in Folder 4 of the weekly Google Form on the right pane.

Move to Folder 4 — Scripts (Behavior). Fill 1-how-the-game-begins.md and 2-win-and-lose-triggers.md. Add Interactive Elements with + new Interactive Element — one file each answering what it is, how it looks, what it does, what causes it. Minimum 5. Copy Folder 4 back to the form.

  • The weekly form on the right stays open all week. "Edit your response" is how you reopen it — same URL every day.
  • The commit rule: if it works in the tool, copy the matching folder back into the matching form folder and submit.
  • Exit ticket today. A pop-out appears in the last part of class with the link. Every item is required; no makeup.
🎮 OPEN THE TOOL
Open MuggsOfVibes →
Paste from the form. Compile. Commit back.
📝 HOW THE FORM ON THE RIGHT WORKS
  • Click Submit at least once — autosave only starts after your first Submit, and Submit is what generates your "Edit your response" link.
  • To keep working, click Edit your response — same URL every day, same form, your writing is still there.
  • Mr. Muggivan can only see submitted work. If you never submit, your writing is invisible when it is time to review or grade. Submit early, submit often.
🚨 GOOGLE FORMS LOSING YOUR WORK??
Autosave has been dropping paragraphs. Move your writing to a Google Doc you own — same spec, same paste in and out of MuggsOfVibes.
🛟 Make my backup doc →

Today's job

Build FOLDER 4 — SCRIPTS (Behavior) today.

Two lead files first: 1-how-the-game-begins.md and 2-win-and-lose-triggers.md.

Then Interactive Elements. Each is a single file that answers four questions in one paragraph: what it is, how it looks, what it does, what causes it to do that. Add more with + new Interactive Element. Minimum 5.

Every verb needs a when. Real triggers:

  • A key press — "when the left arrow key is pressed"
  • A click — "when the Play Again button is clicked"
  • A timer — "every 16 milliseconds," "on a timer"
  • A collision — "when the ball hits a brick"
  • A boundary — "when the ball reaches the top"

One working component first. Usually the player's own input — the paddle sliding, the character moving, the button clicking. Get one right; if there's time, add another.

When it works, click Copy on the FOLDER 4 header, paste back into the form. Your project's file tree is now complete.
MISSING WORK FROM LAST WEEK…?

Behind on any of last week's classwork forms? Click a tab, catch up right here. Each tab opens the live form for that day — pick the one you missed, fill it in, submit.

If a form is blank, that day's URL has not been wired yet. Ask Mr. Muggivan for the link.

Exit ticket

Checking the window …

View

This is your project's repo. Edit your response any time this week — every save is a commit. Only your email is required; everything else is optional.

Thu Sep 24 — Folder 4 — Scripts (Behavior) · The student's writing is what guides the code creation.