OK, as I said earlier, I've been playing with the Skeleton stuff today.
Whilst I was in there, I wondered how fun it might be if I added some kind of overriding features into my default engine.
You might (or not) have noticed, but since Wednesday Workshop Week #1, I've been placing all my game's data into the System folder, then into it's own Weekly numbered folder within.
If you get ALL my games (from the past couple of years), you can bundle them all together into the same folder.
The root contains all your little .exe files, and then the system folder becomes a great big directory full of numbered data.
It all comes together really well.

(If you download the full 2008 archive, you'll notice they're already setup like that, ready for play!)

So, I might as well add extra juicy bits into the mix.

I've got my skeleton to create a folder & file in Program Files. (AGameAWeek/GameData.sav)
If it can't do it there, it tries again in AppData, and if all else fails, it sticks to the actual game's own directory. (Because some folk might not have Windows permissions.. .. You know how some people can get!!)

Once that's in there, your Highscore name will be saved, and reused Over, and Over and Over again! Yeay!
The game will then keep dropping all it's highscores in there, from this point on, and since I'm adding stuff, I figured "Badges" would probably fit in there, too.
So we'll have, say, around about 5 badges per game, give or take, depending on how many I can be bothered to make!! (And, obviously, the more complex games should have more!)

Shouldn't be TOO hard to implement it all, but given that this will be a One-Time-Only deal, I really need to be sure I get it right first time. (ie, A game from this week would have to be compatible with the exact same file as that from a game I might make in a year's time!!)

Yikes!

Better get to work.

I should probably point out, though, that since this all takes time, I won't be re-releasing Not-A-Worm tonight!! .. I'm overthinking things again!!