Sorry for the inconveniet. This bug happened when I almost lost the game on the 2.0.0 > 2.0.1 update (I had to rework all changes from a backup and this was still there...) Will be fixed on V2.0.2 that's comming in a few days
