It seems that a bug in the hiscore entry code that I thought I'd fixed over a month ago got resurrected in setds v1.0. So I fixed it – refixed it – today and we're now at setds v1.01.
Sigh. Gaddammit >_<
I've finally taken the time to add proper saving that works on hardware (at least on my R4, which is the only card I have right now). I've also fixed a very annoying game-hanging bug and did some tweaking here and there, like correcting the decay constant so that I can finally get the scores that I was used to on tatset (2300+, wooo!).
This is pretty much where I wanted to go with this game, so it's now version 1.0. I may add some other things later, but for now I guess it's done.
Okay, so it's only a card game; but a game nonetheless.
The game in question is an NDS implementation of SET. Set is a card-matching game with 81 cards (see below). The figures on the cards have four properties and 3 possibilities for each property. The key is to find three cards for which the values of each property are either all equal or all different. Looking at the color property, for example, a "Red Red Red" combination could (yes "could"; there are still three other properties to consider) form a set. "Red Green Blue" would also work, but "Red Green Green" would not.
Further details can be found in the readme and the game itself.
The game is mostly finished. There may be some tweaking to do here and there, but right now I don't want to get bogged down in a massive fine-tuning-fest – especially since I'm not sure what parts need fine-tuning … and because there's other stuff I really should get back to.
That said, all important aspects work … with one exception: hiscore saving. Yes, that. I've seen the multitude of threads on the subject but sofar I'm unsure of what would work on both hardware and emulator, so I'm leaving it as is for now. If anyone has a tidy hw+emu solution, please do tell.
Oh, and merry Christmas everybody.