Marbles2 - 8-Nov 2020 [devlog/marbles2]

Written by Remy Sharp / Original link on Nov. 8, 2020

I've been making super minor changes since I started this game, focusing mostly on getting the blocks to drop in a way that doesn't halt the entire game play.

Since the game is (currently) written in NextBASIC the maths and logic to check which blocks to drop and how far is pretty intensive even when running at full tilt at 28Mhz.

If you watch the video below you'll notice when I'm selecting the blocks on the far right of the grid, the time it takes to clear out the blocks increases giving the impression of a hang:

So I've been focusing on how to improve perceived performance.

With the fundamental game play mechanics in place, I'm now adding the details to the game like the "next stage" overlays, buttons to quit or retry, an interface to change the game seed - and, if technology permits, a way of submitting high scores online, via the spectrum…

Originally published on Remy Sharp's b:log


« A Week of Symfony #723 (2-8 November 2020) - ★ Store strongly typed settings in a Laravel app »