Error over anchored parts when nothing is anchored

Help and Feedback Building Support
1

so I added some ai to my game using one of roblox’s dummies. I thought that the dummies didn’t fit into my game very well so I rigged up a stone monster, and when I added the script for the ai to the stone monster it had ice physics, I tried solving this for a while and then decided that welding the monsters arm to the dummy’s arm and leg to leg ect. would be a lot easer. I welded everything together and when I hit play I received the following error:

Network Ownership API cannot be called on Anchored parts or parts welded to Anchored parts.

I checked and nothing was anchored, but I added part.Anchored = false in the loop that sets the parts Network Ownership API. And I still got the error, so I unwelded everything and still got the error, even after setting everything to cancollide false and can query false and massless (excluding the parts that were originally the dummy’s) to true I still got the error.

the only things with cancollide set to true, were the dummy’s torso and head (which was exactly like the ai without the monster parts welded to it)

I tried swapping the welds to weld constraints and vice versa but nothing worked. I have no idea why this is happening or if it’s a bug so if you could help then that would be great, thanks!

2

You could try checking if a part is anchored in the loop before setting NetworkOwnership and then printing the name of the part.

Is there a chance you copied the script and pasted it into the workspace, or is the script actually calling parts from somewhere else (not your monster) that are anchored?

Are you absolutely sure you don’t have a weld in between the monster (or one of it’s Parts) and the baseplate? You can check by going to the Model tab and click Show Welds to visually see the welds that are there.

1 Like
3

I found the issue, in the script the server couldn’t keep up with everything so I just had to add wait() so it could catch up a bit and it worked

4

Please mark your post as the solution so others won’t try to keep solving it.
It may help anyone who has the same problem to fix their game in the future.

1 Like
5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.