Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Oh, this post has given me so much to think about. I think my preferences for coding are maybe...simpler is better for most things, but trickier is okay for things like saves/menus? Which Harlowe provides, for the most part. Thank you for your thoughts, this is fascinating. 

I may genuinely take you up on that offer, if you don't mind! I don't see myself switching to SugarCube for this game since it's in Harlowe/I'm familiar with Harlowe and on a deadline already but...maybe for next time? Thank you so much, again. 

Simpler is definitely easier... it took me a few solid days of pounding away on twine, sugarcube's documentation and Google to get what I think is a good template that I like. And even then I find I go back to tweak or change something I'm not happy with. There is definitely more coding than in harlowe, although once you figure out what you are trying to do it's easy to make it quickly repeatable.

Definitely stick with what you know and are comfortable using! That keeps the story coming and holds off the riots for falling behind. It's a significant effort to convert from one format to the other mid-stream, and then having to get up to speed on how to use it. If you wanted to see how I've been able to tweak mine, I can send the project, for purely research purposes of course.

By all means feel free to reach out! I've definitely gotten my feet wet with both formats now and enjoying it more than I had thought I would.