Game-Maker: Sandbox Edition Guide

Working on a game

Opening a game lists every kind of file on the left, even the ones you have none of yet, and shows the selected file’s editor on the right. Changes are saved as you go (Ctrl+S saves at once). A game opened with Look inside is read-only: ✎ Edit a copy above the editor makes a copy you can change.

Checking a level

In a map, 🩺 opens the Level check: a bot plays the scene, tries every move from every place it can stand, and shows where it went and what players would mind (traps, dead ends, prizes in view but out of reach, and more), each with why it matters and the part of The Ultimate Owner’s Guide about it. Many have a one-click ✨ fix. ▶ Play and record adds your own play to the picture. On the start scene of the .GAM, ☑ Before you upload… is a checklist that ticks itself where the check can tell, and 🤖 Make a walkthrough… has the bot play the whole game, to watch or save as an MP4.

The DOS player and cards

The .GAM also has ▤ DOS player, to change the stand-alone DOS player’s own words, colors, frames and timings screen by screen (drag them on its preview to move them) and the extensions of its files, as 1990s authors did with a hex editor. 📝 Instruction card… and 🪧 Level card… write the game’s instructions, or a level’s name, goal and hint, from a few lines of yours and the game’s own keys.

Your own AI

✦, beside the open file’s name, opens the Assistant: an AI you set up yourself (⚙ Settings → AI setup…, with Ollama on your computer or an OpenAI key) that can look at the game, change it, run the Level check and suggest what to do next. Every change can be undone, and you can have it ask first or only look. An AI app on your computer that speaks MCP can do the same: choose Use an AI tool on this computer instead (MCP)… in the Assistant.

Open this in the Guide · Game-Maker: Sandbox Edition