About to switch from doing StatusAilments as a simple Enumeration to doing StatusAilments as a case class hierarchy, so that I can generalize all the Moves that have a chance to cause a status Ailment
After changing StatusAilment from Enum to case classes... seem to be working without too much difficulty or pain
Implement the StatusCauseStatusAilment abstract class and then adapt all existing relevant Moves
Created a BattleStatusManager and start adding private data structures and useful functions; incorporate into abstract class StatusCauseStatusAilment so that I'm only writing code that I need to use