If you're having trouble with a variable not storing the value you think it should, add a couple of show_debug_messages to your statement and find out where it changes. Maybe you'll see that the platform doesn't disappear, it just teleports off screen and it will make troubleshooting that much easier. Code for window message:showmessage ('Text'string+(variable))Code to output to console:showdebugmessage ('Text'string+(variable)). Now, in your compiler window you'll see a feed of the platform's x and y coordinates at every step.

Do you have a platform that disappears when it collides with something? Add this to your step code: show_debug_message( 'Platform x: ' + string(x) + ', y: ' + string(y)) Debugging is one of the most important skills in coding, and GM comes with a variety of tools to help you. nicognito Member 3 Thanks, actually I found out that this was a bug in the Mac IDE (which is still a beta I guess). This is the number one most useful tool for troubleshooting (imho). 2 It's displayed in the 'Output' tab in the IDE. This function will create a custom debug message that is shown in the compiler window at runtime. The easiest one is to hover over the variable name in code.

I've noticed a lot of posts lately that could really benefit from show_debug_message. While the game is paused, you can inspect the values of variables in a few different ways. I am one of those developers, whose main tool for debugging is print messages sprinkled all over the code, so wrapping GameMaker’s showdebugmessage() in something short and sweet like Log() is a must.

Show debug message gamemaker