Hey there, you can just ignore the error, it's not relevant for the later stages of the game. It's an 0.2.0 error, so it has already been fixed in 0.2.1 :)
