Journal Entry 1

Activity:
- came up with an idea for my game about firefighting
- implemented basic movement
- implemented prototype of spreading fire

Notes:
When brainstorming ideas for my project-C I was intrigued by a firefighting theme. Then I thought about what could distinguish this game from other firefighting games and I came up with the idea of you playing as a shark, in some kind of motorised tank, that needs water to survive.  With this water becomes a resource you have to carefully manage. You need to spend water to extinguish fires but you also need to keep some water to survive. Water from your tank is evaporating, so you need to act quickly and cosider if you want to risk and extinguish one more fire, costing you precious water and therefore time before your next refill or play it safe. I'm also thinking about making the water refilling a interesting decision, where for example how much water you take with yourself determines how quickly you're moving.

I decided that top down perspective would fit a firefighting game the best. I set up a script for top down player movement and I setup a fire prefab, which randomly spreads.
When implementing the movement I encountered a problem where collision with walls didn't work properly and the player sometimes even clipped through walls. I solved this problem by using rigidbody.MovePosition instead of directly changing the transform position.
When I made the fire spread completely randomly and independetly from each other the fire would't spread far and instead only became "denser" and also didn't stop spreading so the game would crash from having too many objects. I solved these problems by giving each fire object a cap at how many times it can spread and also destroying fire object when they spawn atop another fire object.

The game will be called Shark Spark.

Invested hours:
- coming up with the idea and mechanics for the game: 1 hour
- setting up character movement and collisions: 1 hour
- implementing the spreading fire: 2 hours