Added state machine to MatchState for restricting Simulations.

LadyEbony commented 6 years ago

[X] Why is this change required? What problem does it solve? Timer was playing during countdown and game results could theoretically change after the EndEvent but before stage switch. Furthermore, MatchManager was getting too many variables to represent the match's state. This fix addresses it by having "basically global" MatchStateID that represents the current state which can accessed by any script.
[ ] If it fixes an open issue, include the text Closes #1 (where 1 would be the issue number) to your commit message.

What types of changes does your code introduce? Check all the boxes that apply:

[X] Bug fix (non-breaking change which fixes an issue) Timer doesn't decrease during countdown.
[X] Breaking change (fix or feature that would cause existing functionality to change) MatchState now contains a StateID which represents the Match's, well, current state. Accessible. What simulations called in MatchSimulation can be altered based on the MatchStateID.

[X] Describe your changes in detail. The commits and change list kinda explain it all. I'm not a too big of my implementation. Seems a little unclean.

LadyEbony commented 6 years ago

Address requested changes. Check commit for more details. (Forget to mention that I added serialization for MatchProgressionState)

LadyEbony commented 6 years ago

Addressed code style fixes.

HouraiTeahouse / FantasyCrescendo