move_toward() function not working properly

dlpantsta

the very simplistic movement code:
velocity.x = move_toward(velocity.x, dir, 50 * delta)

(when pressing left or right dir changes from 0.0 to -1.0 and 1.0)

the problem:
I still cannot figure out why, but in any other case, this code would work just fine. I've debugged and used a lot of prints to try and figure out what it is... But this code from what I can tell isn't even influenced by anything else? Maybe it's just a math thing?
Basically, what is supposed to happen is the character is supposed to move left and right with the direction variable (Input.get_axis("left", "right")) but instead of the value capping when you move left, it instead increases incrementally (not exponentially) without capping. Still, debugged and I proved it hasn't been caused by any external things in my scripts, so I genuinely think it could just be a math issue or something.

any answers are appreciated!!

DaveTheCoder

dlpantsta velocity.x = move_toward(velocity.x, dir, 50 * delta)

What version of Godot are you using?

And on which class are you using it as a method? Vector2, Vector3?

In Godot 4.7, Vector2.move_toward() and Vector3.move_toward() have only two parameters:
https://docs.godotengine.org/en/4.7/classes/class_vector2.html#class-vector2-method-move-toward
https://docs.godotengine.org/en/4.7/classes/class_vector3.html#class-vector3-method-move-toward

dlpantsta

DaveTheCoder Thank you for helping me check! Somehow the issue was something in a function itself, which was really weird considering that once I just placed the same exact code into a different script, it just started working for some reason... Once again, much appreciated!

DaveTheCoder

I found there's also a global move_toward() that has three parameters:
https://docs.godotengine.org/en/4.7/classes/class_%40globalscope.html#class-globalscope-method-move-toward

If you call move_toward() without an explicit receiver, the receiver might be determined by the class of the node to which the script is attached. Maybe that was the problem.

(In the method call foo.bar(), foo is the receiver.)