next »

[SirNiko]

I really like this game, so I've taken the liberty of trying to break it for you. Here are my results:

If the player attacks the rose on the first floor from the right while jumping, one of the blocks spawns while the player is inside of it. This freezes the game. I'm guessing that the same thing can happen if the blocks after the dragon spawn over top of the player. For the first screen, I suggest getting rid of the rose altogether and making those first blocks be visible by default. I like the way how you delayed the music, though. Perhaps you should just move the command to start looping the music for when the words "save her!" appear?

When the castle turns sideways (upon rescuing the 'princess') it is possible for the player to move sideways far enough to not teleport to the next section of the tower (where the blue spark turns the tower right-side up). In one run, I pressed left and fell off the screen without teleporting. I was then able to hold right and continue "up" the tower until I passed the second rose. At this point I had to kill the game to exit.

Also, when the screen is sideways, text and and the 'lives' portraits are also turned sideways. This isn't a glitch, but it is unattractive. Given time, you might consider fixing that.

There's nothing to stop the player from being right in front of the dragon when it spawns, so it's probable that the player will be killed suddenly on his/her first playthrough. Possible solutions: lock the player in place (ignore commands for a moment) until the dragon spawns. Start the intro message before the player reaches the dragon, and have the dragon visible before the fight.

It's possible to kill the dragon by standing behind it and stabbing it repeatedly while it's can't fight back. Not a glitch, but probably not intended behavior.

The dragon takes a lot of hits. It'd be nice if there was some visual hint regarding how close the dragon is to death. Adding a life meter, or making the dragon flash red as it gets weaker could do this. This isn't a glitch, but just a suggestion.

During the second part of the tower, you hit a spark to flip upside down, and fall down one of two shafts, one has spikes and one does not. There's a spark to flip right side up here, but there's no reason to hit it. Skipping this allows the player to avoid fighting any of the monsters in the next section. Not a glitch, but maybe unintended behavior.

The next spark (the one that flips you right-side-up before the arrow shooter) can result in the player getting stuck and freezing the game. This only happened one, and it's pretty far in for me to test reliably.

This is a very enjoyable game so far, and I like the concept of climbing the tower. The second half of the tower seems a little more bland than the first half, but this is probably due to time constraints. I'd recommend you work on patching bugs up until the deadline, and afterwards spend some time polishing this up for a final release. This is definitely a game I want to see more of!

-SirNiko

[Aquanoctis]

Thanks for the reply and for testing it for me. I never seem to find as many bugs when I test (probably because I know how to avoid them  ). Glad you liked it.
Deadlines passed now though...I'll probably polish the game up a bit after the compo has ended just to iron out the bugs.

Didn't really turn out how I originally envisioned, the ending section feels a bit empty to me too. Thanks for playing though. 

[Oddball]

Liked: The flipping mechanic, it took me totally by surprise and adds a lot to the game.

Disliked: The lack of checkpoints. I got really far before I died, but when I realised I had to do it all again I decided to leave it.

Conclusion: This is really good. Given checkpoints I would have played this a lot more. You should definitely consider continuing to develop this.