Moving KinematicBody2D to mouse is going wrong?

EpicDankDude

So basically, here is the code I have:

extends KinematicBody2D

func _process(delta: float) -> void:
	_moveToMouse()

func _moveToMouse():
	var direction = get_global_mouse_position() - position
	move_and_slide(direction)

And I have a little ColorRect as the sprite and Collision Box but the square doesn't go where the mouse is, instead it's like a couple meters behind it or something. Here is a video:

Why is it doing this and also, how would I make it collide with everything but the tile map?

I've sort of fixed it by using the code shown below but I don't want it to move and slide... well I do but I want it to go faster.

extends KinematicBody2D

func _ready():
	position = Vector2(0, 0)

func _process(delta):
	var direction = get_local_mouse_position()
	move_and_slide(direction)

EpicDankDude

[deleted]

cybereality

The code works for me. You probably have a weird offset in the center point of the sprite.

EDIT: Originally suggested local mouse position, but that was not the answer.

EpicDankDude

@cyberreality just edited the post, this works kind of but I have to use move and slide but if I just use position = get_local_mouse_position() then it freaks out and like goes all weird. I want to use move and slide too but is there a way to make move and slide faster?

cybereality

Sorry, I just tried to code and it works. Look inside all the children of the nodes and make sure they are centered properly. Usually you want all children to be at 0, 0 and only the parent has a position change.

EpicDankDude

The top most node (parent) is a node2d that contains a KinematicBody2D with all the stuff in it

cybereality

You can make it faster by multiplying by a speed.

var speed = 2.5
move_and_slide(direction * speed)

EpicDankDude

Woah, the cube freaks out so badly that if I try to take a screenshot, it looks normal in the screenshot.

cybereality

@EpicDankDude said: The top most node (parent) is a node2d that contains a KinematicBody2D with all the stuff in it

Right. So make sure all the children of the KinematicBody2D are centered and don't have any transforms (position or rotation). If you need to alter the position, only the KinematicBody should move. The sprite or graphic needs to be at zero.

cybereality

Yeah, I'm not sure if that speed thing will work, it could get wonky when close to the mouse (unless you check for this and stop moving).

EpicDankDude

it could get wonky when close to the mouse That's exactly what happens, but how would I check for that and stop moving it? I tried a solution that added a move distance variable and if statement which works... well... uh... 2% of the time. Sometimes it'll stop but if the mouse moves away there is like a 99% chance it'll go to the mouse and avoid that limit.

Megalomaniak

Don't forget to pass the process delta to the function and also multiply by it so as to avoid speed being frame-time dependent.

EpicDankDude

@Megalomaniak Oh how do I do that? I forgot.

EpicDankDude

Also can you try to help me with this?

Megalomaniak

Something along the lines of

extends KinematicBody2D
export var speed = 2.5

func _ready():
    position = Vector2(0, 0)

func _process(delta: float) -> void:
    _moveToMouse(delta)

func _moveToMouse(delta_time):
    var direction = get_global_mouse_position() - position
    move_and_slide((direction * speed) * delta_time)

As for the mouse proximity thing, one idea is to define a state variable for the node to be either in movable state or not and only move when it's state is movable. What your criteria will be for it to switch that logic depends on the needs of your specific game.