How to create a killbrick for a part named a specific name only

Help and Feedback Scripting Support
#1

Hey, so I’ve been working on a game where you get a block to avoid obstacles, and I want to add a way to make the block die after they hit the part. The part’s name is simply “Blok”, any help?

#2

When you say:

You can add a Humanoid to it and damage the Humanoid so the part takes damage. Or you can use part:Destroy() which removes the part entirely from the game.

#3

Do you mean like Portal’s emancipation grid, or do you mean that the part they get is what kills the player? I’m a bit confused.

#4

I want to completely destroy it from the game when the “Blok” is touched by the killbrick

#5

yeah i want to completely destroy the block

#6

Still a bit confusing and I don’t know how you’re controlling that part, but you can either use the Touch event or GetPartsInParts to detect the touch, then use an if statement to see if the touch is the kill part, and if it is, use Destroy(). But note that the Touch event won’t work if both parts are anchored.

#7

So just add a touched event, check if it touched the Blok, if it did Blok:Destroy()

#8

its unanchored and the player can move the block

#9

You would use part:Destroy() then

#10

how do I put all of this into a script?

#11

add script into the part and write

local part = --- wherever the part is located

part:Destroy()

example:

local part = workspace.Part -- stored in workspace and the part name is 'Part'

part:Destroy()
#12

If you want to make it detect if a part get’s touched, but see what’s the parts name, if the part’s name matches exactly what you want, you can run :Destroy()`.

You can implement it like this:

local blok = -- (DIRECTORY)
local event

event = blok.Touched:Connect(function(h)
 if h.ClassName == "Part" or h.ClassName == "BasePart" then
if h.Name == "" then -- put what name is required for the main part to get destroyed.
event:Disconnect()
blok:Destroy()
    end
  end
end)
#13

You can also use h:IsA(“BasePart”) instead of checking className for the several different types of parts.

#14

I’m fully aware of that, I like using ClassName.