pydirectinput.move(0, -50*100) doesnt work

[SirPigari]

this is my code:

if running:
check_key(binds["wall"])
for _ in range(4):
check_key(binds["place_build"])
move_mouse(80 * sensitivity, 0)
time.sleep(0.12)
move_mouse(5, -50 * sensitivity)
check_key(binds["cone"])
check_key(binds["place_build"])
check_key(binds["floor"])
check_key(binds["place_build"])
move_mouse(0, 50 * sensitivity) # Move mouse up by 50px
check_key(binds["floor"])
check_key(binds["place_build"])
check_key(binds["cone"])
check_key(binds["place_build"])
move_mouse(0, 50 * sensitivity) # Move mouse down by 50px
move_mouse(0, 50 * sensitivity) # Move mouse down by 50px again

the move_mouse is:

def move_mouse(x, y):
pydirectinput.move(x, y)

the for loop runs only one and then it doesnt move (the loop continues but it doesnt move)

[beefyi6]

pydirectinput uses Windows SendInput, which frequently fails when coordinate values exceed the range of a 16-bit signed integer or when the underlying driver expects absolute rather than relative positioning. Are you seeing the same behavior if you replace pydirectinput.move with pydirectinput.moveTo using calculated absolute coordinates to bypass potential overflow issues in the relative movement calculation?