:GetChildren() Acting Weird?

Help and Feedback Scripting Support
, ,
1

So I am making a tower defense game and I came across this problem.

The zombie I am using will not go to the correct location for some reason? It goes through a for loop that goes through the waypoints. It uses the number to name it and that works just fine, but the problem is that it instantly moves towards the second waypoint, why does it do this?

Script inside the zombie:

local human = script.Parent.Humanoid

local waypoints = script.Parent.Parent.Parent.Waypoints

for point = 1, #waypoints:GetChildren() do
	human:MoveTo(waypoints[point].Position)
	human.MoveToFinished:Wait()
end

script.Parent:Destroy()

image
The waypoints are where the zombie moves. And the mobs folder is where the zombie is located.

image
image1127Ă—526 35.9 KB

This is the prototype map I made. The red parts are waypoints. THEY ARE NAMED CORRECTLY.

The zombie is moving to the second waypoint.
https://i.gyazo.com/e4707c1fff853335d6af39a91517fb0c

2

Tried naming them by maybe “A” or “B”?

Always could try using ipairs too since it sorts through the array returned in order.

3

Still does the same thing the number names do. It just ignores the first one.

4

Something like this would return the array in numeric order,

for i, v in ipairs(game.Workspace.Folder:GetChildren()) do
	print(v.Name)
end

Output:
image

Like, I said you could probably make ipairs work.

5

Completely randomized names, and it still is returned in the order it is in the folder.
image

6

Try this,

local human = script.Parent.Humanoid

local waypoints = script.Parent.Parent.Parent.Waypoints:GetChildren()

for i, v in ipairs (waypoints) do
	human:MoveTo(waypoints[v].Position)
	human.MoveToFinished:Wait()
end

script.Parent:Destroy()
7

I also used ipairs, it just skips 1 for some reason.
Also that script wouldn’t work, “v” is the part, indexing it to the parent makes no sense.

8

No, v is the part found in the folder, but it doesn’t matter anyways if ipairs didn’t work for you.

9

I even made it so it destroys the part when traveled to, and it instantly destroyed 1 and 2 completely skipping 1.

10

That is what I said, please listen.

11

I’m pretty sure it is actually doing it in the correct order just always skipping the first part? Which is odd, tried renaming them to like, “2”, and “3”, or is it always the first one.

12

Always the first one. For some reason.

13

Have you tried three or more parts?

14

Yes. There is currently 8 parts.
image

15

It routes to each one in order skipping 1?

16

Okay, so I figured out something weird. It destroys the 1st part no problem, but does not move to it, but the other parts are moved to just fine.

17

Change point to = 0,

local human = script.Parent.Humanoid

local waypoints = script.Parent.Parent.Parent.Waypoints

for point = 0, #waypoints:GetChildren() do
	human:MoveTo(waypoints[point].Position)
	human.MoveToFinished:Wait()
end

script.Parent:Destroy()

Try that.

18

I’m not sure if you can start point at 0, so. but worth a shot, what you said is really funny and that shouldn’t just be skipping 1 at all.

19

It does not work, unfortunately.

20

The zombie does everything but walk to the 1st part, it does acknowledge it but doesn’t walk to it.