Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
How to use L's sound macros in Sugarcube
Hi folks. I've registered an account here ages ago, and never posted anything, so I guess it's time.
I'm currently working on a game using Sugarcube, and I've noticed that Leon Arnott's sound macro isn't compatible. Basically, you just need to change two characters to make it work: replace storeArea at line 86 by store-area. I've written a small blog post with more details here. I hope someone will find this useful.
I'm currently working on a game using Sugarcube, and I've noticed that Leon Arnott's sound macro isn't compatible. Basically, you just need to change two characters to make it work: replace storeArea at line 86 by store-area. I've written a small blog post with more details here. I hope someone will find this useful.
Comments
Thanks for posting!
Cool blog, Lectronice. Now, get to work on that game!
Did you ever finish your TwineCodex? I agree that the Twine community is scattered. I hope this forum will become the first place everyone goes to discuss and share games, but Twitter seems to currently be the Twine mainstream. Just my take on things.
It's been a long time since I heard TwineQuest mentioned, too.
My change to SugarCube, should I choose to do so, is going to involve a lot of initializing variables and changing <<PassageName>> to <<display "PassageName">>. I think that should be about it. I hope.
I believe that it is not 100% true that all variable have to be initialised in StoryInit.
What is true is that you have to assign a variable a value BEFORE you use it in a comparison or as a parameter to a macro. That assignment could be earlier in the same passage, or in a passage that the user has visited earlier.
A good reason to initialise all variables in one place is that it is easier to keep track of the variables you are using within your story/game. You can even add comments to explain the purpose of the variable because over time even the Author can misremember what a variable is actually for. lol
About my TwineCodex project: I suppose the idea of an offline cookbook still makes sense, but it was more than one year ago, before this forum (so much better than Google Groups!) and before the official wiki. I think twinery.org is a great initiative for the community. It answers well to the need of gathering all Twine-related things, even if it lacks its own games database, in my opinion. Choosing to pull data from the IFDB totally makes sense, because it kind of legitimates Twine games as interactive fiction (there's still some hypertext haters out there), yet I wish there was a kind of official Twine games repository.
Maybe the scattered nature of the community comes from the scattered nature of Twine itself. I mean, it's basically a tool for (dis)playing a wiki as a story. It's all about creating something meaningful by linking meaningless fragments together. And Twitter, well, isn't it a kind of multi-user, vertical Twine ? I guess Twine and Twitter get along pretty well because they are similar.
But let me go back to the Codex: it was a mix of Twine/Twee documentation, L's macros and a few others, and various articles, mostly by Emmanuel Turner. I asked peope if they were OK with that. Chris liked the idea. L liked it too, but told me his macros were updated very often, so it would kind of defeat the purpose putting them in an offline file. And Turner refused for copyright reasons. So it left me with a TiddlyWiki filled with links to online resources, which was precisely what I didn't want. Maybe I'll try again with TiddlyWiki5, someday...
About initializing variables, I've noticed yesterday that Sugarcube has two useful operators : def and ndef (see Control Macros here) which can evaluate if a variable is defined or not.
Me too. I was once a newspaper reporter. I learned to write under deadline and only under deadline.
I invite you to participate in our sporadic challenges such as Super Sudden Surprise Challenge: Flash (Interactive) Ficton. The main purpose of each is to set a deadline and guidelines that will encourage people like you and I to actually finish a game.
I'd say there are way, way more games on Philome.la than IFDB. Twine users have gravitated away from IFDB at this point, it seems to me. Not saying that's a good (or bad) thing. It's just how it is.
However, in my opinion, Philome.la further separates an already diffuse community rather than draws it together like IFDB would help do. But, that's the thing, I don't think one out of ten Twine users care about any sort of "Twine community" outside of a community of which they are already a part. In other words, it seems to me that Twine users are members of other non-Twine specific communities and thus only use the Twine community on this forum for tech support. That's the center of the issue for those seeking or desiring a large, diverse, centralized Twine community: there isn't one because Twine users don't want or need onethey already have their own online community.
Again, I'm not saying there is anything is wrong or right about any of that; it's just how it is, in my view.
Hmm, it's not working for me. To be honest I'm not sure which Sugarcube version I'm using, do you know how I can check? I don't like the idea of updating Sugarcube partway through a WIP in case I break stuff, but I'm probably just being paranoid. I've added your revised macro to a script passage, but when I actually use the syntax in my story, i.e.:
<<timedgoto "wherever" 3s >>
The writing that should be coloured purple shows up as blue. This also happened with the original L macro when I tried to use it before.
Any ideas?
About the SugarCube version, it is usually displayed at the bottom of the sidebar. Thus I'm using a tweaked SugarCube with a modified sidebar I can toggle on or off by clicking at the top of the screen. I'm not 100% sure the original SugarCube displays the version number at the same place, I still need to upgrade to the latest version.
Open the
header.htmlor a story compiled with it (or View Source on a story open in a browser) and check right at the top, there will be a comment along the lines of: The####will be the build. It's also displayed at the bottom of the ui-bar, if you'd prefer to check there.