I didn't think of this during review. We would like the most likely height to be 1, but since generateTowerHeight always adds 1 to the height, the most likely height right now is 2. We should wrap around 0 instead.
Wait, I can't read. The current code is fine!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.