GetConnectedParts output spam (qPerfectionWelded tools in player backpacks)

So this isn’t my script we’re dealing with, but since it is script related I thought I’d post this here. This may be more fitting as a bug report, if you think so, tell me.

For the past week or so, my output keeps getting spammed with this:

Part Handle is not parented to the Workspace or a WorldModel. GetConnectedParts will not include any other parts.

It does this for every part inside the tool, so the output looks like this:

This comes from the qPerfectionWeld script, I am using it inside tools that are in the starterpack (which means they go into the player backpack), I playtested with tools in the serverstorage, no messages, but when I cut and pasted tools into my player’s backpack, the messages appear.
The tools work fine and are welded properly, but the output spam is really annoying

This used to not happen at all before it started about a week ago.

8 Likes

having this issue to, didnt happen before

3 Likes

I’m having this issue as well all of a sudden. I don’t know if it’s because I’m using a tool grip editor plugin for these tools. Its not a serious issue but I’d like to find out how to stop these warnings from flooding my output as well.

1 Like

having this too, i keep seeing hundreds of them when i’m trying to debug stuff

+1 on this as well having this issue as well

3 Likes

It would seem as though this problem is happening again, I’m getting the warning spam again

4 Likes

Same problem here. Console blowing up.

1 Like

I find it curious how everyone started getting this problem at the same time. It makes me wonder if something changed on Roblox’s side, but that doesn’t quite add up since I tested a problematic qPerfectionWeld tool in a different game (a nearly blank local file) and it was fine. The warns only appear when the tool is given and unequipped. Is it the same story for y’all?

2 Likes

looks like the guys at robe locks dot com messed up again, I’m having this problem all of a sudden as well.

It’s kinda annoying.

3 Likes

it’s annoying to try and debug stuff and you see 40 trillion warnings from qperfectionweld about something nobody cares about

2 Likes

This seems to be recirculating, suppressing important output logs!

1 Like

I have the problem too, seems like a roblox issue because i never touched it. Maybe it has something to do with how parts are streamed or most likely GetConnectedParts is not working because of a roblox function behaving differently etc.

1 Like

best I could come up with is just check if the tool is a descendant of the workspace before triggering the script. Also, if it didn’t show up because the tool was in ServerStorage, it’s simply because scripts in server storage don’t run, as if they were disabled


I have the problem too

2 Likes

Same exact problem here. Anybody found a remedy for this yet?

Gettin this too :confused: any fix? I am looking through the script and it doesn’t seem like it’s coming from the script, it’s a problem on roblox’s end.

I recommend just welding the tool/whatever item you’re working on by yourself.

Extremely annoying.

1 Like

Also getting this, happy that it doesn’t seem to be anything problematic though. Hopefully we get a fix for this.

2 Likes

I got it fixed by adding

local inWorkspace = false
for i,v in (game:GetService("Workspace"):GetDescendants()) do
	if v == Part then
		inWorkspace = true
	end
end
if not inWorkspace then
	return false
end

in front of “local Connected = Part:GetConnectedParts()” in the qPerfectionScript

it is a very dirty fix, because it searches the whole workspace everytime but for me it works.

You know you can just say workspace instead of

right?