Skip to main content

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

For the MODE[1000] task (TASK 10011), I have a solution (optimizing for minimum number of words) that uses both UP and DOWN (to rescan input region), but it seems I run out of test cycles before I run out of input. Is that expected, or a bug?

I think it's a bug disguised as a feature. I implemented a timer to check if you get stuck in an infinite loop, and if so, quit. I suppose a better way to do it would be to first check if you're still on the same input, or increase the maximum number of cycles. I'll fix it soon.

Just to make sure, you're not going beyond the final input before writing the final output? There's an error that clearly says "Too many cycles" or smth like that? (I don't remember anymore how exactly this game works...)

Anyhow thank you for still showing interest in this game! :)

Thanks for looking into this!


if you ever consider updating this game for release on Steam, let me know.


I’m very interested in helping design/beta test scenarios for the yet-unimplemented peripherals (BCD, string, display) described in the manual. I can help test both the Linux and Windows releases.

Thanks! Although I don't think I'll be going into Steam yet, there's legal mumbo jumbo and tax stuff. We'll see when that happens.