Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Check out mine if you can put it in the schedule. It is a bit short, so it should not take too much time. :)

https://itch.io/jam/metroidvania-month-23/rate/2582691

EDIT: Now I see you are the dev who made Barn of Duckness. Great game, I enjoyed it greatly! :D

(+1)

Haha thanks a lot! I actually have you on my list already. I saw that it's written in C and uses emscripten to make web builds. I've made a very simple game using C++ and SDL and I also used emscripten to make the web build, so I'm excited to see what you are able to accomplish because I had a really tough time trying to implement continuous collision. I'll play your game as soon as I finish the few that are higher up on my list!

Collision resolution was indeed a nontrivial problem to solve, but I find it satisfying when I finally manage to solve that kind of problem. 

My solution was to simply incrementally move the player, pixel by pixel (first horizontally, then vertically) and check for collisions in each iteration. Also, in the collision resolution I gave the highest priority to pushing up, then to pushing along x axis and lastly to pushing down. That was in order to make the player movement mechanics less frustrating to the player in most cases (i.e. player has a greater chance of "squeezing up" instead of unintentionally/unexpectedly hitting the head when trying to make a jump).

(+1)

That's pretty similar to how I approached the issue. It worked absolutely fine until i started making the platforms tile-based. Then I add some really undefined behavior that I never got around to fixing.

Interestingly, for me, this is what actually solved problems with tile-based colliders. I guess the difference in outcomes comes from some other details of implementations.