Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

The new update is gorgeous!  Two bits of feedback though:

1) Pressing the d-pad quickly enough actually makes the cursor not move, sometimes?  Like, it can move at a high speed, but then it just stops for a beat for no reason.  It definitely didn't have this problem before the update; my muscle memory keeps getting startled. You can reproduce this just by pressing a d-pad direction fairly rapidly and noticing the unsteady rhythm (it seems to be roughly 1 in every 4 moves, but it doesn't always hesitate at the edges, sometimes it hesitates in the middle.)

2) I tried jamming the A button during an auto-move, to test the new build, and it seemed to be fine at first, but then on the next move, the entire playdate crashed and needed to be rebooted!  After rebooting I tried again, and this time the game just softlocked, it no longer accepts input other than the home button -- going home and relaunching fixed it, but it also didn't save my progress, I had to restart from zero.

The second one is still just something that only happens when I'm reproduce it on purpose so far, though I am worried that I'm going to trigger it accidentally when I don't realise an auto-move is coming (which is how I ran into the bugs I reported in the last version)...   The first one is much less harmful of course, but it is fairly distracting while I'm playing because I'm running into it almost constantly.

Issue #1 would be a side effect of the new animation the indicator does. It used to just blink over to its new position, now it will ignore input if the animation is running. I hadn't considered that as I don't play it particularly quickly, and will back the change out.

When a game crashes, you can press B to get a crash report. If you are able to get that to happen again, let me know what it says so I can track down the cause. I'll put up a patch release in a little bit that addresses the cursor movement.

1.2.1 fixes the slow movement problem, thank you!

So far, I've gotten it to freeze/softlock three times this morning (by trying deliberately), but none of them have produced an actual crash, just the situation where the controls stop responding (except for the home button).

I'll let you know if I can ever produce a crash log, but in the meantime, reproducing the freeze seems to be very easy -- the only tricky part is that I believe you have to luck into a 3+ auto-combo, and you have to be hammering the A button on a row that actually has room to move, AND, sometimes the freeze doesn't happen until the NEXT time you clear blocks AFTER that, which might be several moves later.