For kids

Make it better

Your first version is never your best version. Here's how to change things, fix things, and never lose your work.

Changing your game

  1. 1

    Use UPDATE

    Pick the UPDATE tab and say what you want different:

    "Make the frog hop higher."

    "Add a score in the corner."

    Press MAKE CHANGE. One change at a time works best. Then test it!

    The MAKE CHANGE button
  2. 2

    Broken? Say so!

    Games break sometimes. Real programmers break stuff every single day; fixing it is the skill. Tell UPDATE exactly what went wrong: "the frog fell off the screen and never came back."

    Out of ideas? The FIXES button looks at your game's code and suggests repairs (IMPROVE and FEATURES have ideas too).

    The FIXES, IMPROVE and FEATURES suggestion buttons
The Update tab in the FuzzyCode editor with a change being requested

The FIX ERROR button

FuzzyCode watches your game while it runs. If the game crashes into an error, the error message pops up in red right under your game, next to a FIX ERROR button.

Press FIX ERROR, and FuzzyCode reads the error and repairs your game. The fix becomes a new version, so you can always look at what changed. If there's more than one error, the button says FIX 2 ERRORS and fixes them together.

The FIX ERROR button next to a caught error under the game preview
FuzzyCode caught an error; one press asks it to fix it.
Secret swipe trick

Some buttons are hiding extra powers! MAKE CHANGE and FIX ERROR are swipe buttons: press and hold one, and four more choices pop out around it. Slide onto a choice and let go to pick it, like FAST CHANGE when you want a quick little edit, or CUSTOM FIX ERROR to tell FuzzyCode more about what went wrong. A normal click always just does the regular thing, so you can't mess it up.

Holding MAKE CHANGE pops out four more choices around it
Be a bug detective: the three shapes of bugs, and the detective loop — what did I expect, what happened, say it exactly, fix one thing and test
The move behind all of it: say exactly what went wrong, fix one thing, test.

Going back in time

Every save makes a version, like a snapshot of your game. If a change made things worse, use the version arrows to step back to when it was good. So go ahead and try something wild.

The version history controls in the editor
Maker secret

Stuck between two ideas? Try both! Make the change, look at it, and jump back if you liked it better before. Going back is free.