@Imperial_Squid
There are 3 problems you'll encounter when coding: naming variables and off by one errors
@JonnesTT
"Every fucking time" programming ladies and gents, programming
@veroxid
That "No...!" leading right into crying out "every fucking time" is just gold.
@Nationless36
I would tell you what I can say, but I won’t bore you with it
@blakksheep736
Rule number 3 of coding: there is no code too simple to not have bugs.
@Rogue_Smile
this man could litteraly dominate youtube and makes one video a decade
@misterree
This reminds me of the old school mario wall jump. You can force yourself into a wall if you time your speed and frame perfectly, allowing you to jump off a wall.
@gamermugs3107
Classic code bullet moment
@peterrobson7525
I'm sorry but I use my eyes to eat most of the time so I did not pick it up
@tesethebeast
I normally use my hands to see things. Good thing I was using my eyes this time.😗💨
@Droplets21
This is what the collision for my old games looked like
@slwsnowman4038
It's a CodeBullet video, I expect the freestyling collisions.
@AngryBaldG
The bots are insane here wtf
@smallestchannel1
Beginning: SMB1 Bowser Near end: Mari0 portal End: Mari0 unrealistic falling physics
@Connorses
he is slowly learning what every game developer has figured out a million times before
@flamixin
-Lay down to forget everything after a day of debugging. -Watch a short. -Bring back ptsd of my work. 💀
@FreddieSodium
Man been waiting for your next upload like the plague…. But its a short that is almost spoiled 😂 I waiting for ya next one!!
@daleodorito
Usually, if you have any kind of physics, the snapping occurs instantly. Like when the engine sees two things slightly overlapping it pushes them apart, and since the floor usually has infinite weigth it just affect the cube
@greyson7325
The way I used to fix this is by pushing it back out until it's not colliding.
@KlementtM