Essentially what the title says. When calculating the position of the ghost tetromino, the code checks from the bottom point, and works it's way upwards until it finds the lowest point the tetromino slots in, without considering what is above it. The tetromino can then move downwards until it reaches the ghost. This series of oversights in my code caused this issue.
The moves are largely still moves that could be made in a normal game of tetris, just requiring rotation or sideways movement before placing. Due to how late I am in development, and the deadline being soon, I will be leaving this in the game (due to the time requirement of rewriting a major portion of code).
Essentially what the title says. When calculating the position of the ghost tetromino, the code checks from the bottom point, and works it's way upwards until it finds the lowest point the tetromino slots in, without considering what is above it. The tetromino can then move downwards until it reaches the ghost. This series of oversights in my code caused this issue.
The moves are largely still moves that could be made in a normal game of tetris, just requiring rotation or sideways movement before placing. Due to how late I am in development, and the deadline being soon, I will be leaving this in the game (due to the time requirement of rewriting a major portion of code).