Maybe then next time, I can play around with Fullscreen, but the main challenge would then be ensuring that all assets do not get blurry or become "lo-res" (I know it's pixel graphics, but still) for bigger screens.
For the mini games, I really wanted to have some progression, initially. Like each body-part would have three levels, so there would be a total of 9 levels.
But like you said: time and design constraints forced me to make a decision and I decided to have only one level per body-part.
:D
For the mini games, I really wanted to have some progression, initially. Like each body-part would have three levels, so there would be a total of 9 levels.
But time and design constraints forced me to make a decision and I decided to have only one level per body-part.
The music restarting at every body part is a small bug but I think having it continue playing would have been better.
The way it's programmed is that there is only one music track for all the body parts level, one track for the body-map and one track for the intro/outro.
And whenever you select a body part level, that music track gets played from the start, and ideally it should loop.
So, the flow is: intro -> body-map -> part-level -> body-map -> part-level -> body-map -> part-level -> outro
HOWEVER (:P)
I agree with you on the "continue playing would have been better" part; but sadly I could not find any appropriate long-playing track and I wanted to have the rain track play whenever the player would transition back the body-map scene.
I resorted to spam-clicking after the first try haha.
I believe this is what the specialists in the industry call "emergent gameplay" (insert Spongebob rainbow meme here) :P :D, but yes, even when I was playtesting, I would spam-click that level :D
