He's coming back. ...but just this once.

I felt some mechanics were underutilized, so I'm making an expansion.

...more or less just a side quest and extra dungeon. No more than that here.

Coming who-knows-when.

Okay, I'm testing out the HTML5 version again.

The crash is consistent with the one level, and one enemy spawning around that location: this guy.

Time to figure out why...

EDIT: I suspected the Magnet Crusher, but it's likely this guy.

I was considering releasing the expansion today, but then I found a lot of bugs I should've spotted in the original build, and I made the minimap do extra stuff for said expansion.

Don't worry, it'll be out by tomorrow night.

Oh, no, not again.

At least it's just the player character, but still...

EDIT: It's just her collision box being different for the Hurt frames. Easy to fix. Her sprites all have different collision boxes to keep her ability to duck.

Yes, according to Game Maker, there IS a difference between randomise() and randomize(). randomize() gets you zero, guaranteed, with HTML5.

I would blame it on them, but I can adjust.

The HTML5 version was actually running buttery-smooth.

...and then it locked up on THIS screen for no apparent reason. 4th level. Even the music continued to play when I switched windows on this screen.

There may be limits to HTML5 I don't understand yet.

Importing again.

It may say there are 20 warnings, but 18 are about "__cam" and two are about "array_length_1d", related to ye olde depth system.

...well, I don't know if I should be worried about either at the moment.

Just a reminder. It's coming on the 16th, assuming nothing goes wrong.

I realize some players just want to play the game and see the story, while others may actually want to use those revival items, so here's a little compromise for you all.

Also, yes, I NEED to put on that "Pro" flag everywhere.