Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
-1
Instance.new wont anchor?
1 | while true do |
2 | Instance.new("Part", game.Workspace).Name = "Fred" |
3 | game.Workspace.Fred.Anchored = true |
4 | game.Workspace.Fred.CanCollide = false |
5 | wait(1) |
6 | end |
--> Whenever the part is inserted, it will not anchor, but that is only on a "while true do" loop, when I remove the loop, it anchors just fine, but it only makes one?
2 answers
Log in to vote
-1
Because you're making a new part in the Workspace with the same name each time, the game will not know what part you are referencing.
This should fix the problem:
1 | a = 1/0 -- Variable equal to infinity |
2 | for i = 1,a do -- A for loop that will go on forever, like the while |
3 | part = Instance.new("Part",game.Workspace) |
4 | part.Name = ("Part"..i) |
5 | part.Anchored = true |
6 | part.CanCollide = false |
7 | wait(1) |
8 | end |
0
I didn't downvote btw ScriptsAhoy 202 — 9y
Log in to vote
4
That's because you used it's name. The script will find the name, then anchor the part.
Then hen the loop repeats, it'll find the name, the old one, and even though there are 2 of them, it will anchor the one it finds, the first one
1 | while wait(1) do |
2 | local part = Instance.new("Part", game.Workspace) |
3 | part.Name = "Fred" |
4 | part.Anchored = true |
5 | part.CanCollide = false |
6 | end |
You can use the Instance.new as a var, and that's how you would mess with it.
0
This is essentially the same as mine, but this one looks cleaner and his explanation is better. I suggest using this to comprehend instead. RedCombee 585 — 9y