Paperghost.com

I decided to go with Twine because it's (fairly) easy to pick up, and it reminds me of making way too many text adventures in BASIC on a Commodore +4. I knew going in that it was (in theory) mainly designed for interactive fiction, and you had to sort of bash things into shape in another direction if you wanted to make a game - or at least something people more readily associate with a game. First time around, I just couldn't work out how to make it do what I wanted. When I returned, there were now multiple versions galore. The default version, Harlowe, seemed to have more features. I just sort of vaguely assumed it would now be very easy to add additional elements like audio and visuals. Whoops. As it happens, I realised about 40 locations deep that actually I should probably be using the version called Sugarcube. Why search desperately for code that allows me to save and load games, which may not even work anymore, if it does this in Sugarcube by default? Why struggle with au...

 It actually does have a title, but I'd rather reveal it with a nice logo and not some terrible web font. It's taken me a good few years to getting round to making a game, because putting it off indefinitely is easy. All 6 of you reading this can rest easy that if all goes to plan, there'll be an actual finished game out there in the wild...eventually. One of the biggest time wasters was figuring out which platform to make the game on / with. I know my way around some code, but I'm certainly not a coder. I can do visuals (rusty visuals, because I'm very rusty). I can do music. I like stringing together narratives that have a definite end point but include a lot of wiggle room for doing something entirely unrelated. About eight years ago I had a play with Twine, decided it couldn't do quite what I wanted it to, and continued to not make a game. Now, at the grand old age of a lot, I'm back and digging it out again. I could spend forever messing with the innard...