How to make kill bricks in Roblox
Kill bricks and spinning bars are what make an obby a challenge. The plugin tags your hazard parts, writes one server script that handles all of them and adds rotating bars if you ask.
The kill bricks prompt
Select the object in Studio first (or mention it with @), then send this. Change any words you like before sending.
Then keep talking to it
- 2Add two spinning lava bars.
- 3Make the bars spin slower.
- 4Only take half health instead of killing.
What the AI builds
- A KillBrick tag on red neon parts
- One server Script that handles every tagged hazard
- Rotating bars driven by Heartbeat
How it works
Every part with the KillBrick tag is handled by a single script, so adding a new hazard is just tagging another part.
Touches look up the Humanoid and set its health to zero, with a short debounce so one touch is not counted many times.
Spinning bars rotate on the server each frame using the frame time, which keeps the speed steady on any device.
How to make kill bricks in Roblox, step by step
- 1
Make or select the hazards
Select the parts that should kill players, or ask the AI to make red neon parts for you. Each hazard gets the KillBrick tag, so one script handles all of them.
- 2
Send the prompt
The AI writes one server Script that watches every tagged part. Touching one finds the character's Humanoid and sets its Health to zero, with a short debounce per character.
- 3
Add spinning bars
The default prompt also asks for two spinning lava bars. They are anchored parts that rotate a little every frame using the frame time, so the speed is the same on fast and slow devices. They kill on touch like other hazards.
- 4
Press Play
Walk into a hazard to check it resets you, then time a jump over a spinning bar. If the bars are too fast or the hazards too harsh, say so in the next prompt.
- 5
Add more hazards later
Any part you tag KillBrick works right away. Ask the AI to tag a group of parts, or to make a whole lava floor.
Roblox kill bricks settings you can change
Change any of these by asking in plain words, or open the script and edit the value yourself. Each prompt is one undo step, so you can try a value and go back.
- KillBrick tag
- Every tagged part is a hazard. Removing the tag makes it safe.
- Damage
- Kill by default. Ask for half health and the damage becomes an attribute on each part.
- Spin speed
- An attribute on each bar, in degrees per second.
- Debounce
- A short delay per character so one touch is not counted many times.
- Physics bars
- Optional: an unanchored bar on a HingeConstraint motor, which pushes players instead of only killing them.
Fixing kill bricks in Roblox
The hazard does not kill
Check that the part has the KillBrick tag and CanTouch is on. Parts inside a model that has its own scripts can also be affected by those scripts.
The bar spins too fast
Say "make the bars spin slower". The speed is an attribute, so you can also change it in the Properties window.
Players die twice
The debounce prevents repeated hits on one character. If it still happens, another script may be damaging the player too; ask the AI to look for it.
Bars do not push players
Anchored bars move by CFrame, which kills on touch but does not shove. Ask for a physics bar for that.
New hazards I added do not kill
Only parts with the KillBrick tag are handled. Copying a tagged part keeps the tag, but a new part does not have it. Ask the AI to tag the new parts.
More kill bricks ideas to try
Once the basic version works, send one of these as your next prompt. Each builds on what is already in your place.
“Make the lava floor rise slowly over time.”
Moves a tagged lava part upward on a timer, so players have to keep climbing.
“Make some bricks disappear and come back.”
Adds a loop that fades tagged parts out and back in, a classic obby timing challenge.
“Add a short red flash on screen when I die.”
Adds a client-side ScreenGui that flashes when the character's health hits zero.
“Make the bars spin in opposite directions.”
Gives each bar its own spin speed attribute, one positive and one negative.
Where it goes in Explorer
- Workspace / your hazard parts, tagged KillBrick
- Workspace / two spinning bars with a spin speed attribute
- ServerScriptService / KillBricks (Script) that handles every tagged part and the bar rotation
Script names can differ a little; the AI names things to fit your game and tells you what it added.
Tips for a good prompt
Select the object first, or mention it with @, so the AI changes the right thing. Say what the player should see and feel, not how to script it: “the parts should fly a little and spin” works better than naming functions.
Ask for one change at a time and press Play in between. If something is off, describe what you saw, like “it only works once” or “the pieces go through the floor”. If a change goes the wrong way, press Ctrl+Z once and try different words.
Scripting it by hand vs. with AI
By hand you would write a Touched handler per part or a tag-based loop, find the Humanoid safely, add a debounce, and write a rotation loop that uses the frame time. The plugin writes one script for all of it, and new hazards only need a tag.
Before you start
You need Roblox Studio on Windows or macOS and the free Roblox AI Game Maker plugin, connected to your account with an 8 character code. New accounts get 2 credits and a free model you can use every day. A typical prompt on a cheap model costs a few hundredths of a credit, and the AI play-tests and fixes errors as part of the same build. Write in any language; the AI answers in the same one.
Kill bricks FAQ
Can hazards do damage instead of killing?
Yes. Say how much damage and the AI stores it as an attribute on each part.
Will the spinning bars push players?
Anchored bars move by CFrame and kill on touch. Ask for a physics bar if you want it to push players instead.
Can I make a whole lava floor?
Yes. Select the floor part, or ask the AI to make one, and it gets the same KillBrick tag as every other hazard.
Do kill bricks work with checkpoints?
Yes. A kill brick resets the character, and the checkpoint script respawns the player on their last pad.