If you have the heart-jump and you jump into a heart, when you hit the ground you lose the heart-jump. It happens every time for this heart:
It feels very much like a bug, even though I realise that it is required for some puzzles. Could you make it so that this only happens for the last heart you touched? I.e. for all other hearts jumping into it with the heart-jump will let you keep the heart-jump when you touch the floor.
I do see what you mean, and I'm not convinced I do use this in a significant way for any of my puzzles. When I get the chance I'll have a look into whether changing this is feasible/desirable.
Also I don't like the pixel-handwriting font; it's very hard to read.
I'm pretty set on achieving a hand-written look of some kind here, but again I do see what you mean. I'll have a look and see if there's anything I can do to improve legibility without disrupting the aesthetics.
Other than that though, I love this!
Glad to hear it
Ah, I tried the proper game after finishing the practice, but they seemed identical to me. In retrospect I may have just clicked on the wrong button. This was a charming little game. I'll be interested to see if anyone manages to complete it without dying!
Yeah, they *are* identical until you die and/or finish, so you equally might just have not died yet. I'm certainly interested on seeing if anyone takes on the challenge/manages it. I tried hard to balance things so that such a completion isn't unfeasible, but will be pretty taxing.
If it helps to spur anyone on I've managed to get all the way down to the very bottom and back out without dying (though I then messed up one of the easier screens). A true completion is definitely possible!
It seems like the easiest way to accomplish this would be to write/use a program to simulate the precise sequence of keystrokes needed to complete the game. You might call that "cheating" but that amount of effort would still show dedication, no?
That would require some devotion certainly.
Honestly though I think it'd be easier to complete it tool-free than to write the tool. In particular syncing up the input precisely enough would be a little challenging. I'm more than happy to be proved wrong though.