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
Dang it. I got the math right.
The real trick now is to optimize it. It's easier to do since it's technically all 2D.
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.
On the plus side, the tile layer ISN'T overlapping, and Draw draws objects.
On the other hand, NOW the tile layer lags during camera movement.
I guess I'd better let everything else lag for consistency (somehow), or fix the lag.
The next update may be full of bugs.
...moths, mostly.
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.
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.
Just a reminder. It's coming on the 16th, assuming nothing goes wrong.
On one hand, I'm getting there. On another hand, "No, I'm not."
Then again, I probably forgot something important about layering the old-fashioned way, and something about using a view as a texture.
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.
0 comments