Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

I'm sorry about the frustration you had to go through, but I thought I made it clear that the rabbit double jump and the duck can glide (fall slower). If you mean there is a problem with collisions and they literally just go through the ground, I haven't had any similar bugs while testing the game myself. Did it lag or run slower when the problem happened? Can you possibly send a screenshot? You can try the windows/mac build or a different browser.
Sorry to hear that you had problems. Thank you for taking the time to try the game!

Edit: My bad! I've fixed a bug that may have resulted in the mentioned bug. Ironically, it could only happen in certain levels including the first.

(4 edits) (+1)

Sorry if that wasn't clear. I wasn't complaining about the controls. It did take me a bit to understand about the glide, but that was because it was several retries before I could even jump with the duck. I was talking about a collision bug.

I went back and recorded a demo of it - I hoped I could find some sort of pattern to it, but I couldn't. If there's any way I can help debug this, let me know and I'll see what I can do - but I don't see a reliable reproduce yet - aside from, in my case, playing the game. You'll see here several attempts, of which only one actually works (and I deliberately jumped the duck into the pit on that one to try again to confirm that the next attempt failed).

Pardon the low quality, I don't screen record a lot of area captures like this, and didn't want to spend time trying to figure out the settings.

Running Chrome under Windows 11 if that helps/matters.

As I suspected, it's because the game is running on low FPS. I didn't use a physics engine for the game, but rather made a simple AABB collisions instead (checking if the rectangles intersect). What happens is that since the framerate is low, the time difference between each two frames becomes large and subsequently the character moves a bigger distance each frame compared to someone playing to 60 FPS. I thought I would fix it before by limiting the minimum FPS to 20FPS (the game will just hang if you are playing at lower than 20FPS). For now, you can play the desktop version if you want. If not, fortunately fixing this is a matter of changing some numbers really and I will look into it later. Thank you for taking the time to record the video. I really appreciate it. Have a nice day!

PS: Nowadays, Edge runs faster than chrome and uses less ram. Besides having to change the search engine, I had no problem switching the browser at all. Maybe you should try playing it on Edge instead. 

(+1)

Alright, maybe I'll give it  shot on Edge later then, to see if it runs better there, thanks.

I have considered switching to Edge since it's supposed to be much better on battery life too - but since I use a Macbook, a Linux desktop, a Windows laptop and an Android phone and like to have bookmark/history/etc sharing, Edge has been a tough sell.  Somebody really needs to standardize some browser profile protocol that you can sync to arbitrary cloud storage.