Here. It's my ZAGE announcement. I've been planning this for a while. Also, since I'm doing this to announce the level-up update, I might as well make it fun.
You can actually find this sequence in-game, but it'll require a certain code.
Next up
The next update may be full of bugs.
...moths, mostly.
Part of the expansion involves a cute little fight right here. ...in space for no apparent reason.
...too bad it won't be as epic as the final boss, but still...
Just a reminder. It's coming on the 16th, assuming nothing goes wrong.
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.
Can you tell what needs to be fixed on this screen?
...and if you noticed, is it worth fixing?
Since certain elements of GM Studio 1, including ye olde "score" and "lives" variables, were deprecated in later versions, I reworked the score system while making them global.Score and global.Lives instead.
Now getting a million points can be done.
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.
Oh, no. They're stuck. I'M stuck. The only thing that could be doing this within reason should be collision physics.
Pretty sure the GM Studio 1 build doesn't do this, but the current Game Maker build does.
0 comments