Journal Entry 4

Date: 24/03/26

Activity: Implementing powerup behavior and custom animations

Invested hours: ~2-3h

Notes:

This was like my second time using coroutines, and I was reminded that coroutines are tied to MonoBehaviour, so they need to start on an object that is guaranteed to be persistent - ideally the object they're affecting! That was about the main thing that surprised me though. I've dealt with animations, never used Animation Events before but those were simple enough, same goes for everything else. I took the liberty of using a ScriptableObject to define powerup behavior, which allows for greater flexibility.

Outcome: A collectible powerup with custom behavior & animations.