Build Options and Platform Settings

Introduction to Technical Project Configuration

Throughout previous modules, you programmed jumping mechanics, precise collision systems, basic artificial intelligence, graphical user interfaces using the Draw GUI event, and a complete playable loop for our retro 2D platformer. However, a video game does not consist solely of its internal logic; for a project to be perceived as a polished, professional, and release-ready product, it requires impeccable technical configuration. Up to this point in your learning journey, clicking the 'Play' button compiles a temporary test build that runs inside a standard window with generic parameters, often displaying the engine's default icon, a basic window title, and display settings that may not do justice to your game's pixel art aesthetic.

The pre-release preparation phase requires carefully configuring Game Options. In this lesson, you will learn how to define your game's formal identity through metadata (official name, version, author info, copyright notices), establish strict control over visual scaling to prevent pixels from distorting or blurring, embed custom multi-resolution icons across standard OS sizes, and design a clean startup experience using splash screens and intro rooms. Furthermore, we will break down the two main build targets provided by GameMaker: the Virtual Machine (VM) and the YoYo Compiler (YYC), understanding when to use each and how the Configuration Manager allows you to seamlessly toggle between development and production builds without manually modifying your source code.

The Game Options Panel: Structure and Project Metadata

In GameMaker, the command center for build and packaging settings is the 'Game Options' window, accessible via the gear icon located in the top workspace toolbar or through the Asset Browser. When you open this window, you will notice a hierarchical division into two primary sections: 'Main' (shared global settings) and platform-specific options (Windows, macOS, Ubuntu, HTML5, Android, iOS, consoles, and others depending on your installed export modules and active subscription).

The 'Main' section establishes the project's foundation. This is where the game's unique identifier, data synchronization order, and universal memory parameters are defined. However, the platform-specific tabs—such as the 'Windows' tab for desktop projects—are where you configure the metadata that operating systems and digital storefronts (such as Steam or itch.io) use to catalog and display your executable application.

Resolution, Scaling, and Graphical Fidelity Settings

One of the most common pitfalls for novice developers when exporting a 2D platformer is neglecting window graphics settings and scaling methods. If you designed your sprites with a pixel art aesthetic at a low native resolution—for instance, an internal resolution of 480x270 pixels scaled up to Full HD (1920x1080) monitors—improper graphics settings can distort the crisp edges of your characters or blur background tiles.

Inside the 'Graphics' tab of your target platform (such as Windows), GameMaker provides several switches and selectors that fundamentally alter the rendering pipeline:

1. Interpolate colours between pixels: This checkbox enables hardware bilinear filtering. For modern high-definition games featuring vector graphics or high-resolution 2D art, this option smooths jagged edges. However, for our retro pixel art platformer, this box MUST BE UNCHECKED. When disabled, GameMaker uses nearest-neighbor sampling, preserving razor-sharp edges and crisp pixel boundaries without unwanted blur.

2. Scaling: Here you can choose between 'Keep aspect ratio' and 'Full scale'. 'Keep aspect ratio' is the universally recommended option for almost all games. If a user's monitor aspect ratio differs from your game's native ratio (for example, an ultrawide 21:9 display or a 4:3 legacy screen compared to your 16:9 native canvas), GameMaker automatically adds uniform black bars (letterboxing or pillarboxing) along the margins, preventing your sprites from stretching horizontally or vertically.

3. Synchronize with vertical blank (VSync): Checking this option locks the game's refresh rate to the monitor's refresh rate (typically 60 Hz, 144 Hz, etc.). This completely eliminates horizontal screen tearing, which occurs when the GPU frame buffer swaps frames midway through a monitor scan. In a side-scrolling platformer with continuous camera motion, enabling VSync or managing it via code is crucial to ensuring silky-smooth background panning.

4. Window options: You can choose whether the game launches in fullscreen mode ('Start Fullscreen') or windowed mode ('Allow the player to resize the game window'). If you allow players to resize the window freely, enabling 'Keep aspect ratio' is essential so the viewport scales proportionally without breaking your visual composition.

💡 Golden rule for pixel art games: Always keep 'Interpolate colours between pixels' disabled. If you need smooth rendering for UI elements while keeping the game world pixel-crisp, you can control filtering dynamically in GML using gpu_set_tex_filter(false) for world rendering and toggling it on selectively when drawing high-res UI elements.

Managing Resolution and Windows via GML

While Game Options configure the application's initial startup state, a polished game should allow players to adjust resolution and switch between windowed and fullscreen modes during gameplay—either via a settings menu (like the one built in Module 8) or through keyboard shortcuts. To manage these behaviors cleanly through GML, we will build a dedicated display controller object.

Create a new object in your project and name it `obj_display_manager`. Be sure to flag it as 'Persistent' so its logic persists across all rooms, and place it in the game's very first startup room (such as the title screen or a bootstrap initialization room).

// ====================================================================
// OBJECT: obj_display_manager
// EVENT: Create
// ====================================================================
// Define the base art design resolution (native to our game)
resolucion_ancho = 480;
resolucion_alto  = 270;
escala_ventana   = 3; // Initial 3x scale -> Resulting 1440x810 window
es_pantalla_completa = false;

// Set the physical operating system window size
window_set_size(resolucion_ancho * escala_ventana, resolucion_alto * escala_ventana);

// Resize the application's internal rendering surface
surface_resize(application_surface, resolucion_ancho, resolucion_alto);

// Center the window on the desktop after resizing
alarm[0] = 1;

// Set the official window title at runtime
window_set_caption("Retro Adventure - Version 1.0.0");

// ====================================================================
// OBJECT: obj_display_manager
// EVENT: Alarm 0
// ====================================================================
// A one-frame alarm gives the OS time to process
// the resize before centering the window on screen.
window_center();

// ====================================================================
// OBJECT: obj_display_manager
// EVENT: Step
// ====================================================================
// Toggle fullscreen with F11 or Alt + Enter
var presiono_f11 = keyboard_check_pressed(vk_f11);
var presiono_alt_enter = (keyboard_check(vk_alt) && keyboard_check_pressed(vk_enter));

if (presiono_f11 || presiono_alt_enter) {
    es_pantalla_completa = !es_pantalla_completa;
    window_set_fullscreen(es_pantalla_completa);
    
    // When returning to windowed mode, restore size and centering
    if (!es_pantalla_completa) {
        window_set_size(resolucion_ancho * escala_ventana, resolucion_alto * escala_ventana);
        alarm[0] = 1;
    }
}

With this code in place, your game maintains strict mathematical control over its rendering surface (`application_surface`). Regardless of how large the monitor is on which the build is launched, internal pixel proportions will never distort or produce unexpected visual artifacts.

Visual Identity: Icons and Splash Screens

A video game's visual identity begins long before the player sees the first frame of gameplay. Whether browsing the installation folder, pinning a shortcut to the Windows taskbar, or waiting for audio and texture archives to decompress into RAM, these visual presentation elements draw the line between a hobby experiment and a commercial release.

Icon Configuration and Requirements (.ico)

Under the 'Images' tab of Windows options in GameMaker, you will find the slot to assign your application icon. On Windows systems, this file cannot simply be a raw PNG or JPEG file; it must be a valid `.ico` container file containing multiple square resolutions with alpha transparency embedded inside. If you only provide a single tiny image (such as 16x16 pixels), Windows File Explorer will stretch it to 256x256 in Large Icon view, producing an unrecognizable, blurry mess.

To generate this file, design your master icon on a 256x256 pixel canvas in your preferred graphics software. Export the artwork as a transparent PNG and use an icon generator or dedicated software (such as GIMP or Aseprite) to pack the required resolutions into a single `.ico` file. When you load it into GameMaker, the engine automatically embeds the resource table directly into the binary executable header during the build process.