Light Blizzard
THIS GAME IS MADE FOR TRIJAM 270 AND IS MADE IN 1 HOUR 40 MINUTES
Its getting cold outside and it is not going to get warmer.
Stay in the suns radius to keep warm. Leave and freeze.
While your out there why not get rich?
Arrow keys to move. If you cannot move it at first press the screen once.
This game is meant to get somewhat hard so please don't complain.
Don't freeze and have fun.
Comments
Log in with itch.io to leave a comment.
Hey, I'm probably being stupid but using the arrow keys I can't seem to move fast enough at the start to stay in the yellow.
Thanks for letting me know, i have now tested this on my laptop instead of my main computer and for some reason it moves faster on laptop, im assuming its because its a smaller screen. If i continue this game i will fix this error. If you have a computer let me know what happends and what you think :)
I was playing on my main pc so idk what could be causing the difference. I guess it could be something to do with monitor dimensions rather than size. Let me know if you fix it tho and i will give it another try :
THE GAME IS FIXE
Thanks to contributors we have been able to fix the game. Let me know what you think and if it just so happens that it doesn't work for you :)
Hey, just read this! This is one of my favorite games of the jam. You might wanna check out this tutorial for frame interpolation with Construct3; it could be the source of the bug. (Basically, motion as a function of game loop iteration is unpredictable, so we scale it as a function of time passed. Hope that makes sense!)
Thanks for the compliment and feedback. I highly appreciate your attempt of trying to find the bug. If possible and it’s totally up to you could you try to explain further and a little bit simpler of what it is and what to do if you know of course, I would be really grateful. I’m just asking for future notice so I know how to fix it. Thanks a lot and I’m glad you enjoyed the game 😊
Sure. The few-sentence explanation is:
In your main loop, calculate how many milliseconds passed since the last iteration (in pseudocode, time() - time_last). Call this value delta. Then, for everything that moves, multiply the *magnitude/increment of movement* by delta, (rescaling by some constant to taste. Set this constant to 1 divided by what delta is on your machine — not delta itself, but the hardcoded value).
If the WHY doesn’t really make sense at first, that’s okay. The more you implement it, the more it’ll make sense, until it’s readily intuitive. But if you’re still curious, here’s an ancient thread with people explaining it in simple terms.
THE BUG HAS BEEN FIXED
Thanks to your help and contribution i have fixed this bug.
I thank you sincerely :)
Fun and challenging litttle game. Could have more sfx or vfx for the final polish, but it was fun