300 words
2 minutes
Why Kill-bricks Kill You Even When You Don't Touch Them in an Obby

Ever taken a big jump and seen yourself make it over a killbrick? Everything’s fine, you didn’t touch it, you’re still standing? Then, out of thin air, you’re walking and just die? Why does that happen? Is the game broken?

Hi, we’re Towerable, and we make tower obbies such as Snowflake Stage Tower and Kitsune Stage Tower! We know this can be frustrating, and that’s why we’re here to explain it for you.

Before we begin, in this post we refer to your ‘client’ and the ‘server’. The client is essentially what your device is, it’s what you see. The server is the compute behind the game’s backend, managing everything and making the game run smoothly… or run at all.

The server is where the game is. Your client (device) is just connecting to it. But, often at times, you’re not directly next to a Roblox server. This causes more and more lag the further you are away from the origin server. For fast-pace gameplay, this is a problem.

When you jump over that killbrick just to die seconds later, you’ve actually hit the checkpoint. The issue arises when your client is lagging or desynchronised. Because, on your screen, your client, it looks like you’ve touched it a second ago, but in reality your client is 1 full second behind, and therefore the server only processes the hit when your character hits it on the server. Which, depending on your ping can vary. This gives the illusion that you cleared the killbrick, when in reality, you did not.


Not all games work like this, and we’re personally moving off this system as the benefits are low. Originally, it was to prevent exploits, but we’re seeing that there’s better areas to focus on.

Thank you for reading! Maybe check out some of our other posts too, hmm?

Why Kill-bricks Kill You Even When You Don't Touch Them in an Obby
https://blog.towerable.com/posts/informational/common-desync-killbrick-issues/
Author
Towerable
Published at
2026-01-01
License
CC BY-NC-SA 4.0