well the bug has been occurring even before the 0.2 update
Sorry for the inconvenience, this particular instance of the bug was very consistent and unique to 0.2.0, caused by modifications in the draw pile code, it should be fixed in the current versions of the 0.2.0 downloads
