It is a reminder that at the bottom of every towering monolith of code we build—every microservice, every database migration, every CI pipeline—there is just a tiny square trying to get from point A to point B without crashing.
The original game has a "bug" where if you jump at a specific frame rate, you clip through a corner. Ethan didn't fix it for months. Why? Because it felt like a "technique." In open source, a quirky feature is better than a perfect, non-existent patch. big tower tiny square github
The most successful forks of BTTS aren't the ones with the best graphics; they are the ones with the clearest README.md . The repo that includes a diagram of the collision response vector is the repo that gets the stars. It is a reminder that at the bottom
GitHub Repo Reference: github.com/ethanmick/big-tower-tiny-square The repo that includes a diagram of the
And sometimes, that is enough.
Just watch out for the sawblade on Level 4. It’s a killer. Have you forked the tower? Share your best mod or death screenshot in the comments below.
Go to the "Issues" tab on the main repo. Look for the closed ticket titled "Square feels floaty" . It has 87 replies. It discusses jump impulse, delta time, and sub-pixel rendering. This is a metaphor for every agile sprint meeting you will ever attend.
