DEV Community

Jack
Jack

Posted on

Two patches at exactly 13:45. The third came at 17:28 — the cadence held, the clock didn't.

Quick recap of this series: I put "next patch due Sep 13" on the record,
and the developers shipped it on Sep 12 — at 13:45, the exact same
minute as the patch before it. Two data points, one suspiciously
precise clock.

So my working theory was: daily cadence, fixed time slot.

Yesterday's patch settled it. It shipped on Sep 13 — cadence confirmed,
third daily patch in a row — but at 17:28. The 13:45 clock was a
coincidence I over-read from two samples. Half a prediction survived
contact with the data, which is about the usual survival rate.

Meanwhile the game itself had its biggest day yet: +1.78 million visits
in 24 hours (previous record was +1.42M), total now past 13.6 million
in 33 days. Concurrents eased from the 15.5K spike to about 12.8K.

Everything here comes from polling Roblox's public API once a day and
writing the numbers down before I read anyone's coverage. The full
day-by-day table lives here: https://ballvsballgame.com/

Top comments (0)