Game Maker is a popular 2D game development tool originally called Animo and developed by Professor Mark Overmars.
Version 1.0 was built some time in 1998-1999 but never released publicly but on the 15th November 1999 Game Maker was officially released to the public with version 1.1.
Only a few details are known about the source code behind Game Maker, but over the years Mark Overmars has hinted at a few things.
Both the IDE and runner were written in Delphi, initially Version 5 1 but that changed to Version 7 in 2004 2
It was later rewritten by YoYoGames with the runner now being written in C++ and the IDE in C#.
Early versions of game maker (1.1->3.3) exported games in .gmr format that required the Game Maker Runner to execute, later versions (4.0+) allowed exporting directly as .exe files (the exe files technically just appended the gmr file data to the end of the actual runner executable).
There were a few decompilers released for specific versions of Game Maker created executables (*.exe):
When each of these decompilers were released to the public they created quite a stir in the community, e.g: First person caught using Game Maker Decompiler? - GameMakerBlog
New versions of Windows have occasionally broken Game Maker executables, these converters are used to upgrade old Game Maker executable files to run on newer versions of windows:
G-Java was an attempt to create a Game Maker Runner in Java to provide cross platform game development and embedded games inside Java Applets. It was never finished and ended up becoming Abandonware.
G-Java was created some time before October 2004 according to the old G-java.uni.cc Website, it later changed to G-Java.com in November 2006. There seems to have also been a G-Java.tk but it was never archived on the Wayback machine.
It was originally written in Visual Basic 6 on top of a GMD parser implemented by VBGamer45 (best known for creating the first Game Maker Decompiler), but the source code for that was apparently lost.
GMbed was software which embedded Game maker executables in websites using windows specific features to embed a window handle (hwnd) into a Java Applet.
Originally it would split apart the Runner part of the executable from the game data part, but this was quickly put a stop to at a request from Mark Overmars 3.
A website was created to make the process as easy as possible GMbed.com which was later hacked by an Indonesian hacking group.
Over the years there have been multiple different file formats used by Game Maker, as the tool was enhanced it required expansions of the format, here are editable formats used in each version:
For the runner formats, it started with .GMR and then moved to a proper executable (.exe) file in Game Maker 4.0+.
Other formats created for Game Maker include:
If you are interested in parsing some of the older Game maker files formats, there are a few Github projects that may be of interest:
Whenever a new version of Game Maker was released there would always be people wanting to continue using a previous version, this was especially the case when Game Maker started charging for more advanced features which were free in the previous version (GM 6.x, GM 7.x), so a few converters were created by the community:
Mark Overmars also released some companion software to Game Maker:
Mark Overmars also released some software unrelated to Game Maker:
Over the years there have been many open source projects that aimed to enhance Game maker in a certain way, from cross platform IDEs such as LateralGM, software to convert games to Java (G-Java) and even multiple open source re-implementations of the Game Maker Runner (ENIGMA).
Many of these projects are available on Github: GameMaker Engineering Archive - GitHub
Game Maker versions 1.1 through 8.0 trace the evolution of a simple 2D game design program into a robust game development engine. Over the course of a decade (1999–2009), features like a full scripting language (GML), DirectX-powered graphics (2D and basic 3D), networking, file I/O, extensibility, and improved editors were introduced step by step.
The software’s version numbering skipped a non-public 1.0 (due to its origins as “Animo”), and each subsequent release brought meaningful enhancements – from the foundational changes in 4.0 to the quality-of-life improvements in 8.0.
Mark Overmars originally developed Game Maker as a program called “Animo” in 1999, intended for creating 2D animations. This version 1.0 was never publicly released – the software was renamed and first launched publicly as Game Maker 1.1 later that year 1. In other words, there is no public Game Maker 1.0; Overmars skipped directly to 1.1 for the debut, reflecting the shift in focus from a simple animation tool to a game creation software 1.
Released on November 15th, 1999, Game Maker 1.1 was the first version available to the public 4. Despite being primitive by later standards, it laid the groundwork for Game Maker’s drag-and-drop game creation approach and included a built-in scripting language (later known as GML) for added flexibility 1. Notable characteristics of version 1.1 include:
Outcome: By early 2000, Game Maker 1.1 had attracted a small user base (reaching about 1000 downloads by February 2000) and demonstrated the potential of Overmars’s approach 7. However, it was clear that many features (graphics acceleration, game packaging, etc.) were yet to be implemented.
Game Maker 1.2 was released shortly after 1.1 (as a “quick” follow-up update) and brought a number of important improvements and new features while keeping the same basic interface 8. Notable changes and additions in version 1.2 include:
Performance and Language Enhancements: Game compilation speed was roughly doubled on low-end computers, and the engine allowed longer code segments, making the GML scripting more practical for larger projects 9. New built-in constants/variables were introduced (e.g. pi, roomwidth, roomheight, and several back_... variables for backgrounds) to give developers more control over game properties 9. Variable naming was also made more flexible (uppercase letters became allowed in variable names) and other minor GML syntax tweaks were applied for consistency.
Backgrounds and Sound Control: Scrolling backgrounds were now supported, allowing developers to have moving background images in their games (a feature not present in 1.1) 8. Additionally, an action to stop a currently playing sound was added, which was especially useful for stopping background music or looping sounds via code or drag-and-drop 8.
Editing and Interface Features: Game Maker 1.2 made the editor more user-friendly. It became possible to copy or duplicate resources – for example, you could duplicate objects, rooms, and sounds – streamlining development 9. A new “object clipboard” was introduced, allowing users to copy and paste sets of actions between objects, which made reusing logic easier 8. Also, keyboard shortcuts were added for common run-time actions (to quickly start, pause, or stop the game during testing) 9.
Miscellaneous Fixes: Version 1.2 also fixed numerous bugs from 1.1. For example, it increased the maximum room speed and the number of objects a room could contain, corrected issues with background image memory handling (small BMP images were now given transparent backgrounds properly), fixed the lastkeypressed value, and resolved cut-and-paste problems in the sprite/image editor 8.
Overall, Game Maker 1.2 significantly polished the initial release by boosting performance, expanding the feature set (especially in graphics and editing capabilities). It set the stage for Game Maker’s evolution, although it still had the same fundamental limitations as 1.1 (no hardware acceleration and no stand-alone game export yet).
Game Maker 1.3 was another incremental update on the 7th January 2000, focused on refining the software further. There is little official documentation on this version’s specific changes, indicating that no dramatic new features were introduced beyond what 1.2 had added. Instead, version 1.3 likely brought additional minor improvements and bug fixes to ensure stability. For example, Overmars continued to tweak the user interface and GML based on user feedback, and possibly added a few more drag-and-drop actions or options.
Importantly, Game Maker 1.3 still operated under the same technical constraints as its predecessors – it did not yet include DirectX support for graphics, nor did it provide a separate game runner or the ability to create stand-alone executables 10. Games created in 1.3 were still run from within the Game Maker environment, and rendering remained in software mode. In essence, version 1.3 was a maintenance release that smoothed out the 1.x line in preparation for more significant changes to come in the next major version.
(By the end of the 1.x series, Game Maker had a small but growing community of users. The continuous 1.1→1.4 updates through 1999–2000 established the core functionality and reliability of the program, paving the way for the more substantial feature jumps in later versions.)
Version 1.4 was the last update of the 1.x series, released toward the end of 2000. Like version 1.3, it was primarily aimed at final polishing and stability. According to community recollections, 1.4 fixed remaining bugs and fine-tuned the features introduced in 1.2/1.3. There were no major new features added in 1.4 – instead, Overmars ensured that the existing features (objects, events, basic GML, etc.) all worked as expected in preparation for a major overhaul with version 2.0.
Notably, Game Maker 1.4 was still limited to the same feature set scope of the 1.x line. It did not incorporate hardware-accelerated graphics or allow standalone game compilation. Like its predecessors, it relied on the user’s PC to run games through the editor, and graphics were drawn without DirectX support 6. Version 1.4 can be seen as the stable culmination of the initial Game Maker prototype—by this point, the software was relatively robust in its original feature domain, and the user base was primed for the more “substantial new features” promised in the next major version 6.
(With the 1.x series completed, Game Maker had proven the viability of an easy, drag-and-drop game creation tool. The stage was set for bigger changes – notably, improved performance and distribution capabilities – in version 2.0 and beyond.)
Released on the 8th September 2000, Game Maker 2.0 was the first major version number change for the software. This update brought a redesigned interface and significant usability improvements, making game development easier and more powerful for users who had outgrown the 1.x features. Key aspects of version 2.0 include:
Improved UI and Workflow: Overmars refined the Game Maker IDE in 2.0, reorganizing how resources (sprites, sounds, rooms, etc.) were managed. The interface became more intuitive than the 1.x series, addressing some limitations of the earlier design. According to later retrospectives, each major release around this time introduced a new file format or layout; Game Maker 2.0 was no exception, likely switching to a new project file structure as part of the overhaul 5. The overall look-and-feel moved closer to what modern Game Maker versions would use, with more dialogs and organizational panels for different resource types.
More Actions and Functions: Version 2.0 added many new drag-and-drop icons and functions to broaden the range of possible game mechanics without coding 5. Users now had access to more pre-built actions for things like advanced object movement, basic drawing, and control structures, which reduced the need to write GML for common tasks. This expansion of the drag-and-drop system made Game Maker more accessible to beginners and allowed more complex games to be made visually.
Continued Script Language Support: The GML scripting language was further developed, although still not as sophisticated as it would eventually become. Version 2.0 continued to support mixing code with drag-and-drop, giving experienced users the ability to do more. However, it still lacked some advanced constructs that would appear in later versions.
No DirectX or EXEs Yet: Importantly, Game Maker 2.0 still did not introduce DirectX acceleration or the ability to compile stand-alone executables. The rendering engine remained software-based (using the Windows GDI), and games were run through the editor or a bundled interpreter rather than truly independent programs 6. These features were on the horizon (DirectX would come in the next version), but in 2.0 the focus was on improving usability and adding content creation features rather than low-level technical changes.
During the year 2000, Game Maker’s popularity started to rise rapidly. By the end of that year, the program had been downloaded tens of thousands of times by hobbyist developers worldwide, thanks in part to the enhancements in version 2.0 and positive word of mouth in online communities 5. In summary, Game Maker 2.0 modernized the tool’s interface and expanded its feature set, making it a more robust platform for game creation. It set the foundation upon which the crucial technical upgrades of versions 3 and 4 would soon build.
On the 23rd November 2001, Overmars released Game Maker 3.0, which was a milestone for the software’s graphics and performance. The hallmark of version 3.0 was the introduction of DirectX support for the first time 6. This had several important effects:
Hardware-Accelerated Graphics: By leveraging Microsoft DirectX (likely DirectDraw at this stage), Game Maker could now render graphics more efficiently. Games ran faster and could use full-screen modes and graphical effects that were not feasible under the old software-based renderer. This was a significant step up in capability, as it unlocked the potential for smoother animations and richer visuals.
Same Feature Set, But Faster: Other than the new DirectX-powered renderer, version 3.0 did not radically change the game creation features introduced in 2.0. The user interface and workflow remained similar, but everything was generally more polished and performant. For instance, operations that previously might have lagged (like drawing many sprites) could now benefit from DirectX’s blitting capabilities. In essence, 3.0 “implemented DirectX for the first time” to boost graphics handling 6, while maintaining the drag-and-drop and GML systems as they were.
No Stand-alone Executable Yet: It’s worth noting that even with DirectX, Game Maker 3.0 still lacked an independent runtime or compilation to EXE. Games were executed via the Game Maker environment (or a packaged interpreter). The ability to create a true stand-alone game file was still not present at this stage, coming a bit later.
Minor 3.x Updates: Following 3.0, a few minor revisions (3.1, 3.2, and 3.3) were released in 2001 to fix bugs and add minor improvements. These updates improved stability and further increased DirectX support, such as verison 3.1 which removed Exclusive mode in favour of DirectX in windowed mode (3.0 was only DirectX in fullscreen mode). Version 3.2 added new room options: more background options, multiple views, and transitions between rooms
Overall, Game Maker 3.x dramatically improved the engine’s under-the-hood performance. The use of DirectX was a turning point that allowed users to create more complex and graphically intense games than before 6.
This helped Game Maker’s community grow even more, as the quality and smoothness of games made in GM started to increase. Version 3.0’s success set the stage for an even more comprehensive overhaul in the next major release.
Game Maker 4.0, released on the 16th July 2001, was a complete overhaul of the software. Mark Overmars rewrote large portions of Game Maker from scratch for this version 6, making sweeping changes to the interface, architecture, and capabilities. Important highlights of version 4.0 include:
Entirely New Interface: The IDE in Game Maker 4 was significantly redesigned. The layout and organization of resources were improved, giving the tool a more professional and user-friendly feel. In fact, the Game Maker 4.3 interface (the final revision of this line) looks very familiar even to users of much later versions – it established the general design paradigm that persisted in subsequent releases 5. This means that by 4.x, Game Maker had a resource tree, event selectors, and editors that resemble those used for years to come.
Introduction of Multiplayer Functions: Version 4.0 was the first to include built-in support for basic multiplayer/networking features. A set of MPlay networking functions was added, allowing simple multi-computer play over a network or the internet. This was a notable expansion of Game Maker’s capabilities beyond single-player games. Although the networking system was rudimentary (suitable for simple games or turn-based exchanges), it demonstrated Overmars’s intent to broaden the engine’s scope.
Standalone Executables (EXE) Export: For the first time, Game Maker could compile games into independent executable files. With version 4, developers were no longer confined to sharing editable project files; they could create a stand-alone Windows EXE for their game and distribute it to others who didn’t have Game Maker. Under the hood, this worked by bundling the game’s resources with a runner program. The new feature was transformative — games made in GM4 could be run like any other Windows program 11. (This capability coincided with the introduction of a separate “game runner” module in the architecture). The addition of EXE output in 4.0 greatly increased Game Maker’s appeal, as creators could publish their games more easily.
Continued DirectX Support: Building on version 3, Game Maker 4 fully embraced DirectX for rendering. The rewrite likely optimized the use of DirectDraw and related technologies even further, making 2D drawing faster and enabling things like smooth sprite rotations and better transparency handling by default. The combination of DirectX acceleration and stand-alone export made GM4-generated games much closer to “real” indie games of the time.
New Icon/Branding: Game Maker 4 introduced a new program icon (a red gear/hammer icon), replacing the icon used in versions 1–3 12. This visually signaled a new era for the software. The red icon design continued to be used through versions 5, 6, and 7 12, indicating that GM4 set a branding precedent as well.
Game Maker 4.x Updates: After 4.0’s release, Overmars issued a few updates (4.1, 4.2 and 4.3) in 2001–2002 to refine the new system. By Game Maker 4.3b (released in 2002), the software was very stable and feature-rich for its generation 5. This period saw frequent updates, a growing library of user-made examples, and even the launch of the first community-made Game Maker magazine 5. The 4.x series firmly established Game Maker’s core design; many long-time users started with version 4.2 or 4.3 and found the experience recognizable even in later versions.
In summary, Game Maker 4.0 was a landmark release. It delivered a modernized, rewritten IDE, support for networking play, and the much-demanded ability to compile games into executables 6 11. The engine had matured considerably, and by the end of the 4.x cycle Game Maker was a robust tool for 2D game development. These changes propelled Game Maker into the “prominence” phase – the user community greatly expanded around this time, thanks in part to the newfound ease of sharing completed games.
Released in April 2003, Game Maker 5.0 built upon the solid foundation of the 4.x series and introduced a couple of notable new features. It also marked a shift in Game Maker’s distribution model from freeware to a shareware/registration model. Key points for version 5.0 include:
External Files and Custom Data: Game Maker 5 added support for using external files in games 6. This meant games could read and write files (such as saving custom data, configurations, or high scores to an external text file) more easily, and could include external resources. This opened the door for more complex game behavior (for example, loading level data from files, or modifiable content). Essentially, GM5 introduced new functions to handle files and perhaps binary data, giving developers more flexibility beyond the fixed resources in the editor.
Timelines: Another major feature in 5.0 was the introduction of Timelines as a resource type 6. A timeline in Game Maker allows the creator to schedule actions to occur at specific steps (moments) during game execution. This is useful for coordinating sequences of events (for instance, scripting a cutscene or orchestrating waves of enemies in a shooter). The timeline editor let users create a list of actions indexed by time without writing code, which was a powerful addition to the drag-and-drop toolkit.
General Improvements: Version 5 continued to improve overall stability and added smaller features. For example, there were likely new actions and functions (taking advantage of the external file capability), and quality-of-life improvements in the IDE. It also kept all the important features from 4.x: DirectX graphics, EXE output, etc., refining them further. By this time, Game Maker was quite feature-rich in 2D game mechanics, so 5.0’s main innovations were about data and structure (files and timelines).
Registration System Introduced: Game Maker 5.0 was the first version that was not completely free. Mark Overmars introduced a registration fee of $15 USD for the software 5. The initial approach was that Game Maker 5 could be downloaded for free, but it would run in a limited mode (with certain advanced features disabled and a nag screen at startup reminding users to register). Users could pay $15 to unlock the full “registered” version. This change was made to support ongoing development, as Overmars had previously only asked for voluntary donations 5. The nag screen (displayed when running the GM5 IDE or when launching games made with the unregistered version) became famous – it showed the Game Maker logo and a request to register 5. Once registered, Game Maker 5 allowed access to all features, which included things like using DLLs and other advanced functions (some of these pro-only features were added in minor updates or were present but locked for unregistered users).
Community Growth: Alongside GM5’s release, 2003 also saw the launch of the official Game Maker Community forums in their modern form 5. This greatly helped users share knowledge, and a surge of new users joined around this time, drawn by Game Maker’s expanding capabilities. Many high-quality example games and tutorials from the community began appearing on the official site during the GM5 era 5.
In essence, Game Maker 5.0 was an evolutionary update that extended the engine’s functionality into new areas like file I/O and event scheduling (timelines) 6. It also marked Game Maker’s transition to a partly commercial product with the introduction of a registration fee 5. Despite some initial community resistance to paying for previously free software, the modest price and the promise of continued improvements kept Game Maker’s user base growing. GM5’s enhancements were particularly welcomed by more advanced users, as they allowed for games with persistent data and more complex scripted sequences.
Game Maker 6.0 was released in October 2004 and represented another major technological upgrade for the engine. The most significant change was a completely rewritten graphics engine using Direct3D (part of DirectX) as the new backend 6. This brought substantial new graphical capabilities to Game Maker:
3D Graphics Functions: For the first time, Game Maker had built-in support for 3D graphics. Using Direct3D allowed Overmars to expose functions for drawing 3D primitives, textured shapes, and basic 3D models. Version 6 introduced a set of GML functions (and possibly drag-and-drop actions) that let users create simple 3D scenes – for example, drawing 3D boxes, floors, walls, and even applying textures to them 5. This was a big change; while GM6 was still primarily a 2D game engine, adventurous users could now experiment with 3D (for instance, making simple first-person or 3D racing games). Many users remember seeing demo projects of 3D spinning cubes and primitive 3D engines soon after GM6’s release.
Enhanced 2D Drawing: Even for 2D games, the switch to Direct3D brought benefits. It made advanced effects easier – alpha transparency (translucency) was supported more smoothly, and sprite rotation and scaling became hardware-accelerated operations 6. Under the previous DirectDraw system, rotations and alpha blending were either not possible or had to be done via slow software routines. In GM6, one could rotate sprites or set their transparency and have Direct3D handle it efficiently, which opened the door to better visual effects in 2D games (like smooth object rotations, fading objects, particle effects, etc.).
Performance Improvements: The use of Direct3D generally improved rendering performance across the board. Games that might have struggled with many objects on screen in GM5 could run faster in GM6 if they took advantage of the new graphics pipeline. Full-screen mode and resolution handling were also improved through Direct3D.
Minor Changes and Fixes: Aside from graphics, GM6 continued to refine other aspects. It likely fixed bugs from GM5 and could have introduced minor features or adjustments in response to the community (for example, improvements to the sound engine or timeline system). The overall workflow of Game Maker remained consistent; the big differences were under the hood.
File Format and Compatibility: Game Maker 6 used a new file format (.gm6) for saved projects, reflecting the engine changes. Notably, games made in GM6 were not backward-compatible with GM5 due to the new features. Overmars included a converter for GM5 -> GM6 projects, but once a project was in GM6 format, it couldn’t be opened in older versions. This was a common pattern with each major release.
Game Maker 6.0’s introduction of Direct3D and 3D capabilities was a headline change widely discussed in the community 56. Although the typical user base continued to make 2D games, they benefited from the enhanced visuals and effects made possible in this version. The inclusion of 3D functions was somewhat experimental but showcased Game Maker’s flexibility. As a contemporary note, 2006 (during the GM6 era) also saw the publication of “The Game Maker’s Apprentice” (a book by Mark Overmars and Jacob Habgood) which used Game Maker 6 to teach game development 5. This further boosted GM6’s profile as an educational and hobbyist tool.
(Game Maker 6 had a lifespan through 2005-2006 with a few minor updates/bugfixes, but no version 6.1 introduced major changes. By late 2006, attention turned to the next version as Overmars began collaborating with a new company to expand Game Maker’s reach.)
Game Maker 7.0 was released on February 28, 2007, and it marked the beginning of the YoYo Games era 6. This version was the first published under a partnership with YoYo Games Ltd., a UK-based startup co-founded by Sandy Duncan, which Overmars joined to help expand Game Maker’s development and global presence 5. Version 7.0 introduced new features and changes both in functionality and in how the product was managed:
Extension Packages: The most touted new feature of GM7 was the ability to extend Game Maker’s functionality through extensions 6. Overmars added a system where users could create and use Extension Packages (.gex files), which bundled custom GML scripts, actions, and resources into a reusable form. This meant that advanced users or third parties could add new libraries of functions to Game Maker without needing built-in support from Overmars. For example, one could create an extension to provide physics engine functions, new particle effects, or integration with external APIs, and then import that into Game Maker. This greatly increased the flexibility of the tool. Essentially, Game Maker became somewhat modular – features could be added via extensions, and Mark didn’t have to hard-code every new idea into the main program. (In practice, many popular community-made extensions emerged after GM7’s release.)
Resource Library Changes: In prior versions, users could create their own drag-and-drop action libraries using a separate program (Library Maker). With GM7 and the extension mechanism, the way custom actions were handled changed. It integrated more smoothly to allow extended D&D actions via packages 6.
Changes in Asset Storage: Game Maker 7 introduced a new format for saving projects (.gmk). One notable change was that sprites, sounds, and other resources could optionally be stored externally (to avoid bloating the main file). Also, GM7 used an encrypted format for its resource packages to deter easy decompilation of game files (starting with version 7.0’s release candidates, game data was encrypted due to concerns over people creating other tools to import .gm6 files (G-Java, LateralGM)) 6.
YoYo Games Integration: With YoYo Games involved, GM7 began tying into online features. YoYo Games launched a website for sharing Game Maker games (the “Sandbox”), and Game Maker 7 had menu links and features that integrated with this service. For instance, it offered easy uploading of games to the YoYo Games website. Additionally, the registration system changed: YoYo Games handled selling license keys, and the software required an internet connection to activate a license (a shift from the old offline registration of GM6). This was a significant change in how Game Maker was delivered – it reflected a more commercial, multi-platform ambition under YoYo Games.
Minor Feature Additions: Besides extensions, GM7 added some other smaller improvements. For example, there were improvements to the sprite and image editors, new actions for particle systems, and better sound format support (GM7 introduced support for .ogg audio files for background music). It also improved the reliability of the new graphics engine introduced in GM6. However, no major changes to the core engine (rendering or physics) were made – GM7’s games ran similarly to GM6’s, with 2D and basic 3D via Direct3D. The emphasis was on extensibility and preparing for future platform support.
Platform and Community Notes: Game Maker 7 was the last version that ran on Windows only (a separate port of GM7 for Mac was eventually created by YoYo Games in 2008, but that was a parallel product). The release of GM7 via the YoYo Games website also coincided with an expanding international user base, since YoYo’s involvement brought marketing and more visibility. Mark Overmars was still the lead developer of Game Maker 7, but now backed by a team.
In summary, Game Maker 7.0 didn’t radically change what you could make with Game Maker in terms of game genre or engine power, but it expanded the software’s openness and infrastructure. With extension support, advanced users could push Game Maker further than before by adding new capabilities on their own 6. And with YoYo Games taking over distribution, Game Maker began evolving from a one-man project into a more professional product. This version set the stage for multi-platform targets and a larger community engagement that would fully manifest with subsequent versions. (Notably, there was a longer gap after 7.0 – it would be about two and a half years before the next version, as YoYo Games focused on community features and planning Game Maker’s future5.)
Game Maker 8.0 (often just called Game Maker 8) was released on December 22, 2009 6. It was the last major version of the “classic” Game Maker line developed with Mark Overmars’s direct involvement. GM8 came after a lengthy gap and delivered numerous improvements to the user experience, though it didn’t drastically change the engine’s underpinnings. Notable features and changes in Game Maker 8.0 include:
Revamped Script Editor: One of the headline enhancements was a completely revamped code editor window for GML scripting 6. The new script editor had better syntax highlighting, auto-indentation, and a more user-friendly interface for writing code. This was a welcome improvement for users who wrote a lot of GML, making the coding experience smoother and more akin to standard programming IDEs. It included line numbers, find/replace functionality, and other conveniences that were lacking or rudimentary in previous versions.
Improved Image/Sprite Editor: Game Maker 8 introduced a significantly improved built-in image editor for creating and editing sprites. The sprite editor got new tools and a better UI – for example, support for alpha transparency editing (RGBA), more drawing tools, and perhaps onion-skinning for subimages/animation previews. This meant users could do more pixel art and image touch-ups directly in Game Maker without needing an external graphics program. The overhaul made it easier to create higher-quality sprites and tiles within the IDE 6.
Import/Export of Resources: GM8 added the ability to import and export resources (sprites, objects, scripts, etc.) between project files 6. This was implemented through a mechanism to save individual resources or groups of resources to an external file and then load them into another project. It greatly facilitated sharing and reusing code or assets. For instance, a user could export a monster object or a script from one game and import it into another without recreating it from scratch. This feature made Game Maker more modular and collaborative.
New Default Font and Minor UI Tweaks: The appearance of the IDE was refreshed slightly – for example, GM8 used a different default font (Calibri) in the interface, which gave it a more modern look compared to the older versions that used MS Sans Serif. There were also new icons for some actions and minor layout adjustments. Overall, the IDE looked cleaner and more up-to-date in GM8. (This version also infamously introduced a new logo for Game Maker – a green circular “G” icon – chosen via a community contest, replacing the long-standing red ball icon 12. The logo change stirred some controversy in the community, but it was purely cosmetic and did not affect functionality.)
Removed Legacy Features: In moving to GM8, some very old/obsolete features were pruned. For example, support for really outdated Windows versions was dropped and certain deprecated functions were removed or changed. This was part of cleaning up the codebase for the future.
Bug Fixes and Stability: After the significant architectural changes in GM7 (with extensions and new file I/O) and the long development cycle, GM8 focused on stability. Many bugs from GM7 were fixed. The extension mechanism was still present, but more integrated. The game runner and executables produced were more stable on modern Windows OSes. Additionally, game performance saw minor improvements in some areas (though the engine was largely the same as GM7’s, aside from the editor upgrades).
Monetization and Editions: Game Maker 8.0 continued the paid registration model. In fact, YoYo Games adjusted the pricing around this time (GM8 Standard was priced around $25). There was still a Lite version available for free with certain features (like 3D and extensions) disabled, and a Pro/registered version that unlocked full capabilities 6. Activation was handled online via YoYo Games accounts.
As the final version developed under Mark Overmars, Game Maker 8.0 was a polished and user-friendly culmination of a decade of development. It did not radically change the types of games one could make (the engine was still 2D-focused with optional simple 3D, and used Direct3D8 for rendering just like GM7). However, it significantly refined the development experience — coding, painting sprites, and managing game assets became easier and more efficient in GM8 6. The community received GM8 very positively; it became a stable workhorse for many hobbyist and educational projects in the early 2010s. (An update Game Maker 8.1 would later be released in 2011 by YoYo Games, primarily to improve Windows Vista/7 compatibility and add minor features, but 8.0 was the last version where Overmars was deeply involved in the design.)
The GM 8.2 Project is an open-source community-driven fork of Game Maker 8.0, aiming to enhance and extend the original software’s capabilities. Hosted on GitHub, the project encompasses multiple repositories focusing on various improvements and new features.
One of the core components is gm82core, a quality-of-life extension that introduces helper functions, precise timing, global variables, and utility constants to Game Maker 8.2. This extension serves as a foundation for many other modules within the GM 8.2 ecosystem. GITHUB
Other notable modules include gm82room, a revamped Room Editor module, and gm82dx9, which provides a DirectX9 interface extension, enhancing the graphical capabilities of Game Maker 8.2.
By building upon the original Game Maker 8.0, the GM 8.2 Project aims to modernize the software, incorporating new features and improvements that cater to the evolving needs of game developers without switching to GameMaker Studio line of products.
Find out more on the official website: GM 8.2 Project
One of the strongest parts of Game Maker was its community, first started on 9th November 2000 and simply called Game Maker Forum (gamemaking.community.everyone.net)13.
Key milestones for the GMC:
| Image | Host | Description |
|---|---|---|
| None | gamemaking.community.everyone.net | Single board simply called Game Maker Forum |
| pub58.ezboard.com/bgamemakercommunity | It then moved to EZboard on the 16th March 2001 | |
| gmcommunity.edgehost.com/forums/ | Invision Power Board v 1.1 on 6th October 2002 but it only lasted until 8th January 2003 due to server problems (so they went back to Ezboard). | |
| forums.gamemaker.nl | Started on 26th October 2003 another self-hosted Invision Power Board v1.3 this one was much more successful and they never went back to Ezboard | |
| gmc.yoyogames.com | Started 8th May 2007 |
The Game Maker Community has now lasted over 25 years!