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.

Three reasons to be going after the treasure:

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.

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.

If you've had your fill of games where you play as elephants and blue hedgehogs, this might be for you.

...and I haven't advertised this the best, but it's coming.

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.

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

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.

How it started vs. How it's going.

The character-puppet thing ended up being the basis for the boss designs instead of the Robot Maid herself.

I could salvage it, but I'd think adding a mode where bosses fight each other is a bit too extra.

I made an up-to-date trailer for Terry's Treasure Trouble!

You know, in case it wasn't clear what kind of game this is.