**General**
- When using Mega Engine, follow the format objPlayer instead of obj_player for consistency. Use this camelCase in variable names too.
- I didn't come across any comments. I highly recommend commenting your code at least a little; describe what the code under the comment does in one or two sentences, it will help if you come across a bug and have to revisit the code.

**Create event**
- Don't use ``alarm_set``, it is harder to read and unnecessary. Just use ``alarm[0] = 120;`` instead of ``alarm_set(0,120);``
- While on the topic of that alarm_set line: it's good practice to put a space inbetween function arguments. ``alarm_set(0, 120);`` is easier on the eye than ``alarm_set(0,120);``, specially when the arguments get complex. The same goes for operations: use ``x + y`` instead of ``x+y``. It also applies to assignments: use ``variable = 1;`` instead of ``variable=1;``. It applies to a lot of things actually, but I can't list them all; it should feel natural. Note that I also made this mistake in some places in Mega Engine, but I have since learned this is not the way to go.
- Those manual array assignments look ugly, and are really unnecessary. You could replace all those lines with the following code:

```Javascript
for(var i = 0; i <= 21; i++)
{
    black[i] = false;
    send[i] = false;
}```

As a general guideline, don't use manual array assignments if you have over 3 indexes.

**Alarm 0**
- Because of some stupid design decision YoYoGames made, the game always starts with the same random seed. What this means is that you will always get the same pattern if you just use choose; but only if no other random functions have been called before it, so it's consistent yet inconsistent at the same time. You probably want to make it completely random; to create a random seed, use ``randomize();`` before calling ``choose`` or any other random function.
- You could remove the switch/case statement in favor of a calculation to make it shorter... but that would get complicated, so I can't hold it against you.

**Alarm 1**
- In the switch/case statement, you always call black[x] with x being the number from the case. Instead of all that, you could just write ``black[global.blobs] = true;`` above the switch line.
- You don't want to write extra code on the line you end a statement, aka the line with }. Leave that line alone, and continue below it. You can, however, write ``else`` (or ``else if <condition>``) on this line if you want. On that note, it's probably easier to read if you leave an empty line between your statements:

```Javascript
if condition
    // do something

if otherCondition
    // do something else```

instead of

```Javascript
if condition
    // do something
if otherCondition
    // do something else```

- Minor thing, but image_xscale cannot be 1 and -1 at the same time. Thus, you could have used ``else if image_xscale == -1`` (notice the added else) to save Game Maker some processing power.

**Alarm 2**
- Has the "don't write code on the } line" problem, but clean aside from that!

**Step**
- That's too many blacks for one line. It may be a little more complicated, but this would look a lot cleaner:

```Javascript
var canContinue = true;
for(var i = 0; i <= 21; i++)
{
    if black[i] == false
    {
        canContinue = false;
        break;
    }
}

if canContinue == true
{
    // Do the image_xscale things
}```

I can see why this may not be your first thought, and it may be too complicated for what it's worth. Just saying it's cleaner, but your solution works too.

- Instead of using ``x = 216``, try making it more obvious how you got this number. In this case, ``x = room_width - 40`` would make it more obvious.

**Draw**
- I'm not going to lie... this looks really ugly. There is no easy fix, but you can try something like this:

```Javascript
xx[0] = -41; yy[0] = 40;
xx[1] = -24; yy[1] = 40;
// etc...

for(var i = 0; i <= 21; i++)
    draw_rectangle(x + xx[i], y + yy[i], x + xx[i] + 17, y + yy[i] - 16, false);```

This doesn't have the exceptions for image_xscale == 1/-1, but you can add these in the for-loop.