/job/ - Job Board

just spent way too long digging thru the chromium repo to see how that little dinosaur actually functions. it is pretty wild that such a simple-looking pixel game relies on a specific set of logic buried deep within the browser engine. most people just think it is some random easter egg, but the implementation is actually quite structured . u can see exactly how the collision detection works btwn the dino and the cacti when the connection fails.
>the physics are surprisingly consistent for something so lightweight
it basically runs as a simple loop that updates the game state every frame. i found it interesting that much of the logic is tucked away in offline_resources files. seeing the actual math behind the jump height and gravity was a massive trip. i used to think it was just some randomly generated chaos, but there is a clear pattern to the obstacle spawning. i might try to mod my own version into the dev build if i can figure out the build flags does anyone else here spend their free time reading through c++ source files for fun?

full read: https://www.freecodecamp.org/news/how-the-chrome-dino-game-works/