Skip to main content

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

the answer is roughly 200-250 depending on if you are counting empty lines for readability. this comes primarily from having to rush to figure out how to make a few different mechanics work together, and also recently discovering event buses, and growing overzealous with them and not thinking fully about what really needs to be bused and what does not. I already have tons of ideas for how to optimize things, which i plan to do upon completing it.

I did think people might find it funny/sickening to hear of the amount of code i used to make a player run in four directions, pick up an item, push a block, and climb over a wall. i look forward to having some optimization time after this is all over. Every failure is a part of the journey towards future success though, or something wise sounding like that. i think. maybe...

(+1)

was gonna say "holy stuff thats a lot of code" then took a look at my code and saw 300 lines of repeated variables and things I could have done with loops lmao

yeah, it happens tho. i think especially with a jam we are just trying to make things work and there's time for optimization later. plus you had some really complicated stuff going on with your character and especially that last scene so i feel like there's probably more going on there that's justifiable compared to my little dude who picks up a radish and eats it, and sometimes pushes a block.