Behind the Build posts from the GameDavinci studio — news, dev logs, and game recommendations.
Melon Drop is our first game with resting contacts — fruit that piles up and stays piled. Getting it to settle took six changes, and the bug underneath them was an ordering mistake: the position-correction pass ran before positions were integrated, so it separated bodies that were touching, the next frame found no contact, and gravity was never cancelled.
Anyone can put our games on their own site. The route worked, the snippet worked, framing worked. And one grep for who links to it returned zero hits outside the embed pages themselves, so every embed had to be preceded by an email from us. A channel only an email can reach is not a channel.
A player told us our games UI was poor. Rather than start a redesign, we counted: 28 of 81 bundles draw with zero gradients, 16 are under 700 lines, and 38 never load the shared art layer — and they are almost exactly the same 38. The shared layer already existed. The games that most needed it are the ones that skipped it.
Bubble Shooter shipped two instances of the same bug class in one game. A row's parity was stored and also recomputed from its index. The aim guide traced the shot and the shot re-integrated its own flight. Neither computation was wrong on its own, and neither failure ever threw — because a wrong cell is still a legal cell.
Fairway proves each hole clearable at or under par before it deals it. It shipped four separate verification seams, and every one of them replayed the shot through a helper while the player's ball ran through a different function. Nothing asserted the two agreed — so deleting the stroke counter from the real game left all nine tests green.
We shipped three games in one batch and sabotaged each of their suites by deleting the rule the game depends on. All three stayed green, by three completely different mechanisms: the assertion tested a helper instead of the game, a second cause produced the same outcome, and one test inherited an environment where the bug is invisible.
A game shrunk into an aspect-ratio box is not a smaller game — it is a wrong one. We measured every bundle we ship at phone size and found stretched boards, controls pushed somewhere with nothing to scroll to, and a median board area of 21% of the screen. Three of our five predictions from reading the CSS were wrong.
