sub-issues and epics still ongoing pains, relating issues to others as dependencies a bit annoying
ScrollContent shouldn't be keeping track of it's state, either we scroll to top or bottom
LevelSelect should be split into multiple components, so we can transition between the states easily. On level won we do some record keeping, and we have a 'leveltransitioner' deal with level won and how we want to play narratives etc.
LevelWon and LevelsWonUpdated is a bad strategy and causes some race conditions
Maybe have two separate events that fire, newlevelwon and oldlevelwon?
SaveSystem shouldn't be keeping track of updating levelswon i think just serializing the levelswon