I’m making a platformer PVP game, and I want to use dynamic blocks as terrain. Because they can be damaged, I put a barrier around them to protect them. When I was testing, one of the blocks broke (it’s important to note that this was on the “ground” of my arena). However, none of the other blocks seemed to be damaged like this. After some more testing, I found that if you time it right, you can fire the gadget at a slight angle while falling and clip the projectile into the barrier. Could make for an interesting gimmick, although it’s somewhat finicky.
Update: @JustAToaster ‘s solution seemed to work the best since I didn’t want to make the barrier higher. Sometimes, the block connecting to the below terrain will break and cause a weird visual, but it’s only a 20% chance, so unless your players are trying to break the terrain, it’s very unlikely to happen. Thank you everyone for helping me!
Can you include screenshots of the barrier? Projectiles can clip through barriers partially, and in this situation it sound like making the barrier giant wouldn’t work.
The original purpose of the barrier was to tint the dynamic stone, but now it doubles as protection. The barrier is only a few pixels above the stone, but that protects it from most projectiles. It’s just this very niche case where it’s broken, so I’m not too worried.
Edit: Here’s a photo I managed to get of the glitch.
The problem is likely the barrier is too close. If you wanted, you could increase the barrier height but that makes it look like you are floating in the air. Someone else might have a solution though.
gimkit doesnt detect collision the way that you’d see in real life
the fake hitbox (red box) is clearly touching the breakable (blue box) despite there being a wall in the way
gimkit doesnt look for that wall and instead just looks for the red touching the blue
apparently making the barrier bigger does work according to a guide from zappy_zaptos
i’d guess this is because gkc is looking at what gets hit first and cancels the hitting code or whatever as soon as it detects collision
and when the barrier is as thin as you’ve shown it- the hitbox clips through like this
“It’s just this very niche case where it’s broken”
though it could also hit the barrier first as well and cancel (say offset the red hitboxes to the left a couple centimeters)
this is sometimes a thing that happens in games (and a thing in celeste too! [1])
though this is simply a hunch and could very well be flat out wrong
anyways lemme see if i can find a solution
when moving 4 or more pixels per frame you can clip through spiked platforms (btw this info is from a video i saw like a year ago dont trust me search it up instead) ↩︎
