NJL64 Use global_position, not position.

    xyz I tried. I didn't get any different results. The enemy node continues to rise slowly into the air when entering the Area2D body even if I type global_position.

    • xyz replied to this.

      NJL64 I tried. I didn't get any different results. The enemy node continues to rise slowly into the air when entering the Area2D body even if I type global_position.

      body.global_position = $EnemyContainer.global_position

      Does that put the enemy at the position of the container?

        xyz Unfortunately, no. I tried that even before I opened up this discussion. I tried it just now to be double sure, and still same result. Enemy rises vertically upward to no limit. I even tried swapping which ones specify global_position.

        • xyz replied to this.

          NJL64 Well you need to set velocity to zero.

            xyz How should I go about doing it if body.velocity is already assigned a value? I'm not sure what you mean.

              NJL64

              body.velocity = Vector3(0,0,0)

                NJL64 How should I go about doing it if body.velocity is already assigned a value? I'm not sure what you mean.

                Who assigned it?

                  xyz I did. I changed it from "body.velocity = body.position.direction_to($EnemyContainer.global_position) * body.speed" to "body.velocity = 0", but that didn't do anything.

                  kkkkkkabc The collision number? Who's? What number should I change it to? Do you mean the mask/layers?

                    kuligs2 That causes an error. I'm not sure how it fixes the problem I'm trying to solve either. Also it's a 2D project. You can't use Vector3, right?

                    I'm not sure how setting velocity to 0 fixes the issue or how to implement that, where to put it, or who's velocity. Sorry, I'm just kind of confused.

                    • xyz replied to this.

                      NJL64 I'm not sure how setting velocity to 0 fixes the issue or how to implement that, where to put it, or who's velocity. Sorry, I'm just kind of confused.

                      Set body.velocity to zero. Since body.velocity is a vector, you need to set it to zero vector value as @kuligs2 suggested, not to scalar 0 value. If you're in 2D it needs to be Vector2(0, 0) or Vector2.ZERO. Once you have that sorted out, assign the container's global_position to body.global_position. Eliminate all other code that messes with body's velocity or position (global or local).

                      Doing the above should result in enemy being glued to the position of the container. This is a simplified version of what you ultimately want to achieve but in coding we often first implement a simpler version of the solution (sorta like a rough sketch), make sure that it works properly, and then proceed to gradually upgrade it into more finessed versions.

                      So first do the simple gluing, make sure that it works and that you understand how and why it works.

                        xyz Okay. Thanks for clarifying! I'm gonna take your advice and see what I can do.

                        This makes the body stop and remain still where it is when making contact with the Area2D:

                        This, makes the body fall through the floor:

                        Maybe, I'm misunderstanding.

                        *I can see I posted the wrong screenshot for the first pic. Sorry.

                        • xyz replied to this.

                          NJL64 Yes,collision layer/mask is what caused to rise.The collision number of different objects can be set to different.

                            NJL64 Maybe, I'm misunderstanding.

                            Your question was "How do you make one node follow the position of a node from another scene?". What this has to do with areas?

                              xyz That's just how the code is called. "bottom_checker" is the Area2D. It's connected with the "body_entered" signal.

                              When the enemy/object enters the Area2D body, that's when the code to have the enemy node (body) move in to the container node ($EnemyContainer) and stay there is called. That's what I'm trying to figure out.

                              It's not the Area2D that's the problem (I think). When it makes contact with the enemy, the code is called, but it's the code in my function that I'm struggling with.

                              I apologize if I'm not communicating myself well. 🙁

                              • xyz replied to this.