So I've been messing around with Bongo Cat lately — you know, that adorable little rhythm game that took over Twitter a while back. And being the nerd I am, I started wondering: how would you even build a proper guide site for a game where you're literally tapping along to a cartoon cat banging on a table?
Turns out, the mechanics are deceptively simple but there's some interesting stuff going on under the hood.
What I dug into:
• The beatmap timing system — it's actually more forgiving than osu! or Friday Night Funkin', the hit windows feel deliberately tuned for casual play which makes the skill curve way gentler
• Pattern recognition in the note charts — there's this recurring thing where faster sections almost always follow a left-right-left alternating pattern, muscle memory kicks in faster than you'd expect
• The scoring multiplier is weirdly opaque — it doesn't just reward accuracy, there seems to be a hidden streak bonus that kicks in around 50+ consecutive hits
I ended up putting together a guide over at bongocat.org breaking down the harder tracks and some optimization tricks for high scores. The site itself isn't anything fancy — static HTML with some interactive beatmap previews I cobbled together in vanilla JS — but it's been fun reverse-engineering why certain songs feel so satisfying to play.
Actually, the most annoying part was getting the mobile touch handling right when I was testing the interactive sections. Safari has this ~300ms delay on touch events that drove me nuts until I remembered
touch-action: manipulation
is a thing. Classic.
Anyone else here tried building tools or guides for rhythm games? Curious what approaches you've taken for visualizing timing windows — I went with a basic canvas implementation but I'm sure there's cleverer ways to do it.
Top comments (0)