Link to nodes movement until release

[acero-ad]

Godot Version

4.2.1

Question

Hi! Im practicing developing a game that is the classic game were you move a bar and hit a ball to break bricks that are above it. Like arcanoid but with a ball, I dont remember the games name.

I have a player scene that has the bar(player that you control) and the ball scene in too. The idea is that i want to start the game having the ball “on top” of the bar and while the bar moves the ball stays “sitcking” to it untill I press Space. The space part i do it with a signal but im not able to see a way to keep the bar and the ball together until the Space is pressed. I can imagine this can be done keeping the ball inside the player node as a child, but i feel this is not a player child but and independent node that is going to not need to be related with the player but react to the player.

How can i link both nodes so they stay moving together until they Space is pushed?

Edit1: As is said in the first comment the ball is a RigidBody2D

Thank you very much! This is my first post so feedback is welcome, especially if im doing something wrong.

[zdrmlpzdrmlp]

first you need to determine what type of node will this ball be
it looks like it has to be rigidbody2d for me,
if it’s rigidbody2d, then you can use freeze function and make it as a child of the player, and when you pressed SPACE, it will unfreeze the ball and you can add “push” power to it after reparent it back to world space

here someone done it in 3d, it’s “sticking” to player when the player is holding the ball

Weird error when reparenting, but only when player is looking in a certain direction?

extends CharacterBody3D var pickup=false const SPEED = 5.0 const JUMP_VELOCITY = 4.5 @onready var camera = $Camera3D const SENSITIVITY = 0.1 @onready var pickup_position = $Camera3D/Pickup @onready var world=$".." var ball: RigidBody3D var cooldown = 1.0 # Get the gravity from the project settings to be synced with RigidBody nodes. var gravity = ProjectSettings.get_setting("physics/3d/default_gravity") func _ready(): Input.mouse_mode = Input.MOUSE_MODE_CAPTURED func _input(event): if e…

sadly the project file now is now deleted on this post, so you cant test it right away

[acero-ad]

Thanks for your answer.
The only issue i see is that i feel the ball should not be a players child, I see them as independent objects that should not be hanging one from the other.

Maybe im wrong and my programming experience with other languages and other environments is pushing me in a different way that is not the correct one.

[zdrmlpzdrmlp]

becoming a child of a node is basically made them follow what the parent’s Transform is
since you want the ball to keep moving according to player position, then you can just make it as a child of the player and the ball has to be following the player around

reparenting isnt a big issues, it’s just basically 1 line of code now with the .reparent() function

[acero-ad]

Ok, I think that the ball could start being a players child and once its moving reparent it to the main scene. That should work.

I answered you before you added that last part.

Is reparenting a good practice?

[zdrmlpzdrmlp]

there’s a best practices guide in the documentation, one of the pages mentioned about reparenting the player node before changing scene, so you dont have to keep instantiating each new player for every new scene, but i never read it’s a bad practice

[acero-ad]

Perfect, I am right now reading the good practice docs. I will get there haha

Thank you, i will see if im able to make it work and mark your first answer as the solution.!