Scripting HelpersARCHIVE
A little piece of Roblox history. Preserved for everyone, one question at a time.Read about the archive →
✓ ANSWER ACCEPTED

part is not a valid member of workspace/model?

i cant figure out for the life of me how this isnt working

wait(3)
script.Parent:MoveTo(game.Workspace.one.Position)
wait(.5)
script.Parent.Jump = true
wait(.4)
script.Parent:MoveTo(workspace.Model.two.Position)
wait(.2)
script.Parent.Jump = true
wait(.7)
script.Parent.Jump = true
script.Parent:MoveTo(workspace.Model.three.Position)
wait(.4)
script.Parent.Jump = true
--script.Parent:MoveTo(game.Workspace.iDests.Dest9.Position)
wait(1)
script.Parent:MoveTo(workspace.three.Position)
wait()
--script.Parent:MoveTo(game.Workspace.iDests.Dest9.Position)
wait(1)
script.Parent.Script:Remove()
--script.Parent:MoveTo(Vector3.new(3.67, 5.7, -13.5))

it outputs: two is not a valid member of Model

2 answers

✓ Accepted answer

You use workspace.Model.two, but you use workspace.one?? Check your explorer to see where you put the stuff.

We can't help you with missplaced objects inside the explorer, as we can't see them.

1 comment

0

I FORGOT TO ANCHOR IT SO IT FELL OFF!! XD

remove isn't recommended, it just sets the parent to nil. Think of it as; Cut, and delete. If you cut an object you're setting it's parent to nil, and if you delete it. It's gone forever.

Remove just sets the parent to nil.

#Why is remove not recommended

:Remove, causes untracked memory. Many developers suffer from untracked memory. Untracked memory can cause game lag, unplayable game, and even shutdowns.

But untrackedmemory is another topic i don't want to get too in-depth on.

This discussion is preserved as it was. New answers, comments, and votes are closed.