Environment Installation and Configuration

2. Code Editor and Feather Configuration

'Feather' is one of the most significant components for any programmer in GameMaker. Feather is the intelligent real-time static code analysis and autocomplete system built into the engine. It acts as an advanced spell and grammar checker that continuously analyzes your GML scripts, warning you of uninitialized variables, incorrect function calls, incompatible data types, and non-existent resources before you compile the game.

To configure Feather properly, navigate down the preferences tree to the 'Feather Settings' category:

- **Enable Feather:** Make sure this box is checked. If you are working on a computer with extremely limited specs (older processors or less than 4 GB of RAM), Feather may demand CPU resources; only in such extreme cases is it advised to disable it. - **Severity Levels:** Feather classifies alerts into three levels: 'Message' (stylistic messages or minor suggestions), 'Warning' (warnings about potentially problematic code), and 'Error' (critical syntax errors that will prevent compilation). Leave this setting on its default mode to receive valuable educational suggestions while learning to write clean code. - **Naming Rules:** Feather helps you maintain an orderly convention in your project by recommending standard prefixes (for example, requiring sprites to start with 'spr_', objects with 'obj_', and sounds with 'snd_'). You can enable or disable the strictness of these warnings according to your learning pace.

Next, head to 'Languages' -> 'GML Code' within the editor preferences. Here we will adjust ergonomic writing options:

- **Default Scripting Language:** GameMaker allows working in two modes: GML Code (traditional text writing) and GML Visual (block-based visual programming using actions and nodes). In this course we will focus primarily on **GML Code**, as it is the industry standard offering maximum flexibility, readability, and development speed. Set this parameter to 'GML Code' so that every new event or object you create initializes directly with a pure code editor. - **Tab Size:** A value of 4 spaces is recommended to facilitate reading hierarchical blocks (blocks delimited by curly braces { }). - **Auto-closing of brackets and quotes:** Enable automatic closing of brackets ({}), parentheses (()), and quotes (""). This prevents one of the most recurring syntactic errors among novice programmers: forgetting to close a structure before compiling.

3. Storage Paths, Performance, and Backups

One of the gravest mistakes beginners make is failing to pay attention to the physical location where their projects and temporary files are stored. GameMaker writes and deletes thousands of temporary files per minute during the debugging phase (local test compilation).

Review the following parameters under 'General Settings' -> 'Paths':

- **Default Project Location:** Determines the root folder where your video games will be created. **Golden rule of security:** Never place this folder inside continuous cloud synchronization services like OneDrive, Dropbox, Google Drive, or iCloud Drive with direct sync enabled. These services lock files on disk when attempting to sync them in the background at the same time the GameMaker compiler tries to write to them, causing fatal compilation errors ('Permission Denied' or 'File Access Error') and even irreparable project corruption. Save your projects in a dedicated local folder (for example, 'C:\GameMakerProjects\') and perform manual backups or use professional version control systems like Git. - **Automatic Backups:** Go to the section corresponding to project backups. Verify that the 'Enable Automatic Backups' option is enabled and set a prudent interval (between 5 and 10 minutes). This will ensure that in the event of a power outage or unexpected operating system shutdown, lost work is kept to a minimum.

Verifying the Execution Environment (Target Manager)

Once you have saved your preferences by clicking 'Apply' and 'OK', you will return to the main GameMaker interface. Before proceeding to create or manipulate any files, you need to verify that the engine has the correct output Target configured.

In the top right corner of the main GameMaker window, you will see a circular icon that resembles a target or bullseye. This element is formally known as the **Target Manager**. Clicking on it opens a context menu with three critical columns:

1. **Platform:** Indicates the operating system or ecosystem you will compile for. For free version users on Windows, the default option will be 'Opera GX' or 'Test' (which uses the local test virtual machine). With standard licenses, you will also have 'Windows', 'macOS', or 'Ubuntu'. For our local development practices, make sure your native desktop platform or local test mode is selected. 2. **Output:** Determines the type of technical compilation. There are two modes in GameMaker: 'VM' (Virtual Machine) and 'YYC' (YoYo Compiler). The **VM** option compiles the project almost instantly, packaging the code to be interpreted by the engine's virtual machine; it is the mandatory and optimal mode for daily development, debugging, and rapid learning. Meanwhile, **YYC** translates GML code directly into native C++ and uses heavy external compilers (like Visual Studio on Windows or Xcode on Mac), offering higher performance at the cost of significantly longer compilation times. 3. **Device / Configuration:** Allows selecting the test device (defaulting to 'Default') and variable configuration (defaulting to 'Default').

💡 For the entire initial journey of this course, always keep the output set to 'VM' mode. Compiling in VM mode takes mere seconds, allowing you to immediately test every change you make to the game.

Troubleshooting Common Initial Issues

During installation and first startup, technical issues may arise caused by restrictive operating system settings or interference with other programs. Below are the three most common problems and their documented solutions:

- **The IDE freezes on a white or black screen upon startup:** This is usually due to a conflict between the UI's graphics engine hardware acceleration and the computer's graphics card drivers. The immediate solution is to update your GPU's graphics drivers (NVIDIA, AMD, or Intel). As an emergency alternative, you can force the IDE to render via software by adding the `-disable_gpu` parameter to the GameMaker executable shortcut in Windows.

- **Antivirus blocking error during compilation:** Certain antivirus solutions detect executables temporarily generated by GameMaker in the system's temp folder (`%TEMP%` or `AppData\Local`) as false positives because they are created and deleted within seconds. To resolve this, add the GameMaker installation folders and your dedicated project folder to your primary antivirus or Windows Defender exclusion list.

- **Runtime download failure due to proxy or firewall:** If your connection is behind a corporate or university network, or has a strict firewall, Amazon AWS download domains (where Opera hosts compiler modules) may be restricted. Ensure your firewall allows unrestricted traffic on ports 80 and 443 for the main `GameMaker.exe` executable.

Practical Activities and Exercises

Complete the following three practical exercises to consolidate your environment setup before moving on to direct asset manipulation in the next lesson.

Exercise 1: Identity and Runtime Status Verification

**Objective:** Confirm that authentication was successful and that the engine has a functional and updated version of the local Runtime. **Instructions:** 1. Launch GameMaker and look at the top right corner of the main window. 2. Locate your Opera username or account identifier certifying you are logged in. 3. Open the top menu: `File` -> `Preferences` -> `Runtime Feeds` -> `Master`. 4. Observe the list of available and installed Runtime versions. **Verification criteria:** At least one version with a checkmark icon or bold text must appear in the Runtime list, indicating it is installed locally on your hard drive (`Status: Installed / Active`). If none appear installed, click the download button next to the latest version on the Master channel and wait for the process to finish before closing the window.

Exercise 2: Ergonomic Customization and Feather Activation

**Objective:** Configure the IDE exclusively for GML Code programming development with smart analysis support. **Instructions:** 1. Open the preferences window (`Ctrl + K` or `Cmd + K`). 2. Navigate to `Feather Settings` and ensure the general `Enable Feather` checkbox is active. 3. Go to the `Languages` -> `GML Code` section. 4. Modify the `Default Scripting Language` option (or default script language when creating new resources), making sure it is set to **GML Code** and not GML Visual. 5. Verify that autocomplete and auto-close options for parentheses and braces are enabled. 6. Click `Apply` and then `OK`. **Verification criteria:** When clicking `Apply`, the bottom bar must not display error messages, and preferences must be saved persistently. When reopening preferences after restarting the software, modified checkboxes must retain the values you assigned them.

Exercise 3: Local Working Directory Setup on Disk

**Objective:** Establish a secure root folder in your operating system that does not interfere with cloud sync services or permission issues. **Instructions:** 1. Use your operating system's file explorer and create a folder at the root or in your home directory (for example: `C:\GameMakerProjects` on Windows or `/Users/your_user/GameMakerProjects` on macOS). 2. Inside that folder, create two subfolders named `Projects` and `Backups`. 3. Return to GameMaker, open preferences, and go to `General Settings` -> `Paths`. 4. Set the `Default Project Location` path pointing to the `Projects` subfolder you just created. **Verification criteria:** Open the path in the file explorer and verify that it does not contain the active sync icon from OneDrive, Dropbox, or Google Drive. This check prevents 99% of read/write failures beginners experience when trying to compile their first video games.