Skip to main content

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

Wallace.Donegan

5
Posts
A member registered Jan 24, 2018 · View creator page →

Creator of

Recent community posts

(1 edit)

Well its just a shell really. I was not able to keep up with my vision in the time frame. I had plans for hints and indicators, the fish eating part of the bait when you let them get away, all manner of things that could be cool once implemented. I may finish up this project one day but for now i actually learned a lot from the experience and just look forward to trying again on the next Jam.

Edit: Yeah, I am a coder and I get lost in the code and mechanics; often I forget about the rest of the game. 

I have to admit the procedural part was a little but of a cheat. We constructed 20 or so sections about a screen width long, added them to a pool and cloned one at random to pop into place ahead of the player. We didn't' really know how we were going to achieve all this when we started and so the design circled around a few times and left us with a good implementation on the sections. Lack of optimization due to the original design, where each rectangular chunk of 'dirt' was going to be added at run-time, kinda made the end result quite a bit more 'framey' then we had hoped.  If your working on anything procedural I hope this gave you some ideas on how to tackle your own implementation. Thank you for trying our game!

I apologize Keerigan, I failed to focus on optimizing the camera follow code and I believe this broke the game for many players. Thank you for taking the time to try to play though!

I apologize for the poor camera angle. Thank you for playing the game though!