How to Fix Runtime Errors in Gamemaker Studio 2

There are many different types of errors Gamemaker can throw at you, but most it’s most likely you got a runtime error. In Gamemaker, when you get a runtime error, a big white window will appear, showing some valuable information about the issue.

Runtime errors are typically laid out like so:

_______________________________________________
###############################################
FATAL ERROR in
action number [x]
of [event with error]<Ctrl> Key
for [object of event with error]:

[error type]
at [error position]
###############################################
-----------------------------------------------
stack frame is
gml_Object_[object with error]_[event with error]
(line [line number with error])

The first thing you’ll want to do is to go to the event which has the error, and look at the line number in that event. Check and see if anything is wrong. Is something spelled incorrectly? This is the most common reason for runtime errors.

If you see any red exclamation point icons (), you should hover over those with your cursor and it will tell you what’s wrong on that line.

If there are no red exclamation point icons, you should also check if there are any yellow triangle icons (). Likewise, hover your mouse over those icons if they are present.

In most cases, finding and fixing these little icons will do the trick. However, sometimes it’s not this straightforward. Certain error messages will have a negative value as the “action number”. These values can be used to pinpoint the exact nature of the error and what it refers to the following values possible. Below is a table of each value and what it refers to:

Additionally, Gamemaker provides us developers with an entire list of all possible errors as seen in this article (thanks, Gamemaker!). Below is the entire list of possible errors: