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.

The next update may be full of bugs.

...moths, mostly.

Playing around with the title is only the start of a title sequence.

The best way to let everyone play with whatever controller they want is to let players test it out, reconfigure it, and let them test it again.

...it's a bit messy, since this is a game that should support two players.

Can you tell what needs to be fixed on this screen?

...and if you noticed, is it worth fixing?

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.

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.

Coming soon to another update.

Lemme get some work done with it first, then we'll talk.

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.