Tetromino Rotates Into Another Tetromino

[amolgorithm]

Seems that a tetromino piece overlapped on another tetromino after rotation into it (image attached below). Basically, when the tetromino was rotated, part of it overlapped another tetromino nearby and "merged". I would presume that this is because of the boundaries bug/error that is mentioned in #5. However, it did serve as useful cheat code for me to prevent reaching the top by merging tetrominoes to save some space 🙂.

[BeornG]

if anyone want to fix this you need fix collision and wrapping issues in the moveleft, movedown, moveright and rotate function