LinkedIn | Portfolio | Email | Github
My 'Game in a Day' challenge is where I try to make a game in less than 24 hours! Ideally, I work around 8 hours on a game during one day and call it done. But sometimes, I've spread the hours over a period of days, as long as its under 24 hours. I do try to keep to 8 hours or so though, although I have worked on some projects much longer (but still under 24 hours!).
To get ideas for the challenge, I just ask people for a single word (or use one I'm interested in doing) and build around that. Kind of like how game jams do it, like Three Thing Game at the University of Hull.
There aren't any other rules really; except have fun! I like to start from scratch and use my own code and libraries without using any 'Quickstart' or 'Game Jam' libraries to speed things up. This helps me build a healthy code library of useful stuff! I enjoy the challenge, creativity and the constraints of the challenge and it produces some funny, interesting or rather scuffed results - but it scratches that itch to create for me.
I often try to angle challenge sessions towards working with an unfamiliar technology, like the Mirror networking library for Unity. I find it helps me learn these libraries and technologies quickly.
Total Time: 8.5 hours
Charge up your cast and launch your bobber out into the lake, then drag in fish in a clash of tactics and stamina. Hit the fishes with your bobber to earn score!
- Hold LMB to charge power.
- Release LMB to cast.
- Mouse position determines the direction of cast.
Don't overengineer! I wasted a good two hours trying to whack in coding patterns. Focus on only what matters, no fluff. I spent waaay too long trying to get a line renderer to replace the quick-n-dirty slider. Do not refactor for cleaner code until you need to! I eventually had to get an FSM in to replace the Player switch boolean nightmare.
- Tools: Unity v2022.3.4f1, Visual Studio 2022 64-bit
- Libraries: N/A
- Proj. Mgmt.: Trello
- Design: Miro, Paint.NET for fast mock-up, good ol' paper and pen!