@Darkhog and @guzzungo: I had some performance issues when i tested with FF 11.0 even tough I have an i7 processor. The collision detection seems to be causing the troubles. I probably should have put a comment saying "works best in Chrome" instead of "Chrome only"
Thanks for all the reviews and comments so far. I really had fun creating it and seeing that some people enjoy playing it is awesome! Definitely encouraging me to continue making games.
I loved it! My favourite thing is your green travelling companion. Somehow he makes the game twice as good. Watching what he does makes the journey less tedious. The performance was flawless - pure 60fps, everything worked perfectly. Keep up the great work!
@Raptor85: Hit detection and sound are buggy in FF. getImageData() seems to cause troubles and HTML5 audio seems to suck in general (no browser supports looping without a sh* delay at restart as of now). I will use flash for audio until browser vendors start fixing this.
For collision detection I calculate overlap of the bounding boxes of 2 sprites and then check pixel values of both sprites in that overlap. If two pixels at the same point have alpha > 0 => collision. This works perfectly fine in Chrome but not in FF.
When I do the collision detection FF sometimes returns undefined for pixel values I check and my condition gets undefined==undefined and you get a ghost collision. Easy fix but I didn't test on FF for the compo so I noticed only after it. Hence the "Google Chrome/Chromium only".
I love this kind of game. It'd be nice if you used the same button for starting and restarting, though; I couldn't remember to hit r and ended up having to refresh.
Nice looking game. I do feel the controls could be a bit more responsive. To me it felt like the sliding would "pump". Like the timer on that button couldn't quite keep up.
@quixotic-project, @volando, @basspenguin: Unfortunately I didn't get around to implement catching the E-coli and create multiple levels with more diversified game play :(
I really wish the movement animations weren't fixed-time. If you hit an action key at the wrong time, it'll often go for long enough to ruin the next move, and the next, and then you're dead.
@Rectifier: They aren't fixed-time but they are unfortunately not very much in sync with the speed-up of the game so it gets more frustrating the more it speeds up.
Played in FF12 on a quadcore i5, no real problem spotted it worked very well.
As I often say to my fellow members of the Construct2 community when making the controls of a game, think about azerty keyboards. The current configuration is such that to jump I have to press the key under "S". For this peculiar game, it's no big deal, for games making full use of WASD it's really bothering. Just a nugget in your way, think about those kind of issue ;)
Else the game works as intended and the mechanic has already been tested/not that original.
I liked the twist on the lead character modifying the state/position of some obstacles though, it adds to the challenge.
Comments41
hit detection is a little wonky, probably my only complaint, kept hitting things i was clearly well past or dodged well before.
For collision detection I calculate overlap of the bounding boxes of 2 sprites and then check pixel values of both sprites in that overlap. If two pixels at the same point have alpha > 0 => collision. This works perfectly fine in Chrome but not in FF.
When I do the collision detection FF sometimes returns undefined for pixel values I check and my condition gets undefined==undefined and you get a ghost collision. Easy fix but I didn't test on FF for the compo so I noticed only after it. Hence the "Google Chrome/Chromium only".
As for getImageData() speed FF seems to have troubles: http://www.mikethetike.com/2011/05/html5-canvas-using-and-optimizing-context-getimagedata/
I do feel the controls could be a bit more responsive. To me it felt like the sliding would "pump". Like the timer on that button couldn't quite keep up.
A very simple game but basically fun.
Gonna try to go for it at the next LD.
Good job :)
As I often say to my fellow members of the Construct2 community when making the controls of a game, think about azerty keyboards.
The current configuration is such that to jump I have to press the key under "S".
For this peculiar game, it's no big deal, for games making full use of WASD it's really bothering. Just a nugget in your way, think about those kind of issue ;)
Else the game works as intended and the mechanic has already been tested/not that original.
I liked the twist on the lead character modifying the state/position of some obstacles though, it adds to the challenge.