Script to disable an item with a certain name

1BL1ZZARD · December 22, 2020, 5:09pm

Moonvane:

local listOfPlacesToCheck = {workspace, game:GetService("Lighting")}

local function updateWeldDisabled()
    for _, s in pairs(listOfPlacesToCheck) do
        for _, v in pairs(s:GetDescendants()) do
            if v.Name == "SystemWeld" then
                v.Enabled = false
            end
        end
    end
end

updateWeldDisabled()

for _, s in pairs(listOfPlacesToCheck) do
    s.DescendantAdded:Connect(updateWeldDisabled)
end)

this still goes in??? chars 30

m_orbidlyfat · December 22, 2020, 5:09pm

@Moonvane
workspace. only applies to the Workspace.

game.DescendantAdded:Connect(function(desc)
    if desc.Name == "SystemWeld" then
        desc.Enabled = false
    end
end)

This, however, searches the whole game.
It’d be useful to know where the instance spawns, but you could also use

local SystemWeld = game:WaitForChild("SystemWeld")
SysyemWeld:Destroy()

Ty_Scripts · December 22, 2020, 5:10pm

It’s not

script.Enabled = false

but rather

script.Disabled = true

1BL1ZZARD · December 22, 2020, 5:10pm

local script or normal? chars 30

Moonvane · December 22, 2020, 5:11pm

@gxenious
Yes, but you need to put a pcall because some things don’t give you permission to check them:

m_orbidlyfat · December 22, 2020, 5:11pm

Server (normal) Script, not LocalScript

m_orbidlyfat · December 22, 2020, 5:13pm

This whole comment is incorrect.
You don’t use server scripts just because they “load faster”, that is completely dependant on the game’s mechanics and graphics.

Moonvane · December 22, 2020, 5:15pm

Your entire comment is incorrect, local scripts load in based on a player joining and where they are, server scripts load in before any players join, as soon as the game starts. This is why .PlayerAdded 100% of the time fires in server scripts when placed properly.

m_orbidlyfat · December 22, 2020, 5:18pm

@1BL1ZZARD
I’d recommend one of my suggestions:

These can both be put into Server Scripts

Moonvane · December 22, 2020, 5:20pm

To fix your second comment:

local SystemWeld = game:WaitForChild("SystemWeld")
SysyemWeld:Destroy()

Did you mean to use workspace:WaitForChild(“SystemWeld”) ?
This will never work.

And to fix your first comment:

game.DescendantAdded:Connect(function(desc)
    pcall(function()
        if desc.Name == "SystemWeld" then
            desc.Enabled = false
        end
    end)
end)

Like what I said earlier, it will error saying “Lacking permission” if you attempt to check some items, such as the CorePackages.

1BL1ZZARD · December 22, 2020, 5:22pm

none of these scripts actually work

m_orbidlyfat · December 22, 2020, 5:23pm

No, I’m sure I know what I wrote.

PseudoPerson · December 22, 2020, 5:24pm

You have a plugin inserting scripts into your game. All of the scripts above don’t stop sophisticated viruses. Double check your plugins. You could also be adding free models with viruses.

Moonvane · December 22, 2020, 5:24pm

Ok, I fixed them for you so they work now

1BL1ZZARD · December 22, 2020, 5:25pm

no, if i remove the thing called ‘systemweld’ it will work but there are literally hundreds of them

m_orbidlyfat · December 22, 2020, 5:25pm

Show us what your explorer looks like, we haven’t got enough information.

PseudoPerson · December 22, 2020, 5:26pm

If there are hundreds of them inside studio while not in play test something put them there. You can use madpoint83’s server defender if you’d like. Works well for me.

Edit:

1BL1ZZARD · December 22, 2020, 5:31pm

thanks to everyone who tried to help. i had one of the game devs clear the game of SystemWelds.

1BL1ZZARD · December 22, 2020, 5:31pm

the script is:

for i, v in pairs(workspace:GetDescendants()) do
  if v.Name == "SystemWeld" then
  v:Destroy()
  end
end

Moonvane · December 22, 2020, 5:32pm

Oh I thought you meant to disable it