Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

Well, I finally got here :D

Graphics:

Cute, like the style. Every encounter looks awesome, extra points for unexpected seal :D Only minor thing: Effect of ship touching water during lane change looks off, specially when ship is on top of lane dividers. Mask on that effect would be nice touch.

Sound:

No complains. Damage sound is cute :D

Gameplay:

I hated those levels in BattleToads, still dont like them. So I’m a bit biased here.

Biggest issue is the fact that I can’t really tell if ship is going to get past obstacle or get hit by it. Probably skill issue.

One time after encounter just ended I got hit by multiple obstacles. Seemed really unfair, some safe zone after encounter would be great.

Speed at beginning of game felt way too slow, specially after restarting few times.

Contols:

Mostly fine, but occasionally keypresses didn’t register or even registered wrong way. That’s sad. Probably caused by mouse click during encounter or just after main menu.

Overall:

Solid, but not really my kind of game. Didn’t finish (failed 5 times at normal difficulty, so probably skill issue)

Bonus points for open code, got answeres to most of my confusions.

(+1)

*hides* Ah.. that water ripple effect is part of the actual boat asset so... yup now you say that, that /would/ have been a good idea to do it that way. XD

Yeah, given more time I think we could have worked out a way to have a "gap" in obstacles just before and after the encounters, so it's not unfair, because I also got done in by hidden rocks etc. on some of the larger encounter sprites when testing.  Also on twiddling dials on the initial speed and the speed ramp up values is something we could have refined a bit more with time to make it feel nicer.

I think another person I've just answered also pointed out the input issue was due to using the mouse during, and we didn't catch that in testing because we were using pure gamepad or keyboard inputs when testing (and not the mouse) so yeah that was our oversight in testing input.

Thanks for playing and your detailed feedback, we appreciate it!