Game states not saved in autodeploy of test environment about marugoto

[interrogator]

first, priority for this isn't really very high, it's not realted to live system, and is not a bug.

We have the option of saving/deleting the player states when we import, and we tend to delete them to avoid errors that come from breaking changes. the problem is, we can't easily know in autodeploy if the latest changes break the game structure, so i guess we delete to be on the safe side.

so, either we don't remove player states, which will cause errors that won't occur on live system, or we continue doing as we have been. my suggestion would be to leave things as is, but if you want we can change this and introduce some errors if you really prefer. @martindusinberre please decide :)

also sorry for not noticing these issues, as i said before, it's just because we were getting potentially hundred emails from github every day...

[martindusinberre]

@interrogator No worries at all about not noticing these issues! I'm happy to follow your advice and leave things as they are. So I'll close this for the time being. Thanks, Martin