Why does my condition trigger when the value should be negative?

Printing y_pos inside the loop makes the behavior easier to see because you'll observe it decreasing for a long time before the integer reaches its limit. A debugger may appear to show normal behavior simply because you're only inspecting the early iterations or pausing before the overflow occurs. If you want to test a reversed direction, make sure the termination condition is reversed as well, rather than leaving the loop unconditional.

Your comparison itself is behaving correctly. Starting at 20 and subtracting 5 means the value will never become greater than or equal to 200 during normal execution. The problem is that `while (true)` never stops, so the program continues modifying the value long after it has passed the position you care about. Use a meaningful loop condition or stop when the ball reaches the ground, for example by checking whether y_pos is still within the simulation range.

The loop is infinite, so y_pos keeps decreasing forever. Eventually it goes below the minimum value representable by a signed int. In C++, signed integer overflow is undefined behavior, but on many systems it appears to wrap around from a very negative number to a very large positive number. Once that happens, `ball.y_pos >= ball.ground` becomes true and you see the large output. Add a stopping condition to the loop and print y_pos on every iteration if you want to observe the transition.