Start Building
Guides / GameMaker Studio / GameMaker Studio Introduction: What is GMS and Why Use It?

GameMaker Studio Introduction - What is GMS and Why Use It?

GameMaker Studio sits in a sweet spot between no-code tools and full programming engines.

You can build complete 2D games with a visual editor and simple event logic, but you also have a real scripting language (GML) when you need precision and performance.

In this chapter you will:

  • Understand what GameMaker Studio is and where it fits in the game engine landscape
  • See the kinds of games and teams it is best suited for
  • Learn what you need installed to follow the rest of the guide
  • Get a quick tour of the editor so the later chapters feel familiar

By the end you should know whether GameMaker is a good fit for your next project and feel confident continuing to the hands-on chapters.

What GameMaker Studio actually is

At a high level, GameMaker Studio is a 2D-focused game engine that gives you:

  • A visual editor for rooms (levels), sprites, objects, and timelines
  • An event system that lets you react to things like create, step, collision, and input
  • A scripting language called GML for custom logic
  • Multi-platform export options for desktop, web, and consoles (with appropriate licenses)

Compared to engines like Unity or Godot, GameMaker focuses on:

  • <strong>Fast iteration for 2D games</strong>
  • <strong>A gentle learning curve</strong> for people new to coding
  • <strong>A tight, opinionated workflow</strong> rather than a toolbox for every possible use case

If you want to build a high performance 3D shooter, GameMaker is not the right tool.

If you want to ship polished 2D action games, platformers, roguelikes, or arcade titles with a relatively small team, it is an excellent choice.

Who GameMaker Studio is for

GameMaker is a strong fit if you are:

  • A solo developer who wants to move from prototypes to a complete 2D game
  • A designer or artist who is comfortable with visual tools and wants to ease into code
  • A small team that values simple workflows over maximum engine flexibility
  • An educator looking for an approachable engine for teaching game dev fundamentals

It is less ideal if:

  • Your project is heavily 3D or relies on complex custom rendering
  • You require deep low level control over engine internals
  • You want to reuse the same engine for many very different genres including large scale 3D

For most 2D indie projects, GameMaker’s trade-offs are pragmatic and productivity friendly.

What kinds of games people build with GameMaker

Examples of game styles that match GameMaker well:

  • Side-scrolling platformers and metroidvanias
  • Top-down action games and twin stick shooters
  • Turn-based tactics and RPG style battles
  • Arcade style score chasers and endless runners
  • Puzzle games with grid or physics based mechanics

Many successful commercial releases have shipped on GameMaker, which means:

  • The engine is capable of production quality work
  • There is an existing knowledge base, tutorials, and patterns to learn from

In later chapters you will build small prototypes that mirror these categories so you can reuse the patterns in your own projects.

What you need installed before continuing

To follow this guide you should have:

  • A reasonably recent version of GameMaker Studio installed
  • A machine that can comfortably run the editor and export small projects
  • A text editor is optional, but useful if you like editing GML outside the built in editor

You do not need:

  • Prior programming experience beyond basic comfort with a keyboard and mouse
  • Art, audio, or design skills — we will use simple placeholder assets where needed

Later chapters will call out any extra requirements such as export modules or platform specific tools.

First look at the GameMaker Studio interface

When you open GameMaker Studio and create a new project, you will see a layout similar to:

  • A <strong>resource tree</strong> on the left that lists sprites, objects, rooms, and other assets
  • A <strong>main workspace</strong> in the center where editors open in tabs
  • Context specific panels for properties, layers, and timelines

Conceptually you will spend most of your time:

  • Creating or importing sprites that define how things look
  • Defining objects that hold logic and respond to events
  • Placing those objects into rooms that act as levels or screens
  • Writing GML in event handlers to define game rules

You do not need to memorize every panel now.

The goal of this chapter is only to give you enough orientation that the later step-by-step instructions feel natural rather than overwhelming.

How this guide is structured

This GameMaker Studio guide follows a W3Schools-style, chapter-based structure:

  • <strong>Beginner chapters</strong> focus on basic navigation, objects, events, and simple GML
  • <strong>Intermediate chapters</strong> introduce collisions, UI, saving data, and project structure
  • <strong>Advanced chapters</strong> cover performance, larger project organization, and multi-platform builds

Each chapter is designed to be a short, focused lesson you can complete in about 5–10 minutes.

You will always:

  • Learn one clear concept
  • Apply it in a tiny example
  • See how it connects to future chapters

In the next chapter you will create your first simple project, explore the resource tree in more detail, and add a few objects so you can see the full “edit, run, tweak” loop in practice.