Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
combined Macro Set code examples
How would I use <<replace>> or <<replacelink> in the sugarcube version Im using in conjunction with if statements inside that give you multiple options to be clicked and replaced instead of just down one path?
Comments
<<if $hullBreached>> <<if $wearingHardSuit>> <<display "That was close">> <<elseif $wearingSoftSuit>> <<display "Hole in suit">> <<else>> <<display "You die">> <</if>> <</if>>Heres my example
How do I make this work?
This uses macros for <replacelink> in javascript that I took .
Does an else have to be followed by an elseif?
Try something like the following: (using the line continuation mark for readability)
If specified, there should only ever be one <<else>> per <<if>> and it should always be the last clause. So, no, it should never be followed by an <<elseif>>.
The order must be like the following:
I noticed you just wrote . This needs more to it to work right? Like a false or true or does it automatically check if its true if you omit a condition to meet?
You do not need to compare a boolean value to either of the literals. Conditional expressions ultimately simply to a boolean, so if your conditional expression consists of a boolean value, then that's all you need.
For example:
http://www.glorioustrainwrecks.com/node/5029
"SugarCube supports a special passage named StoryInit, which is where the creator suggests you place your variable initialization." I always thought it was a requirement. Here it was giving me trouble until I think <<display storyinit>> fixed it? Any ideas why it wasnt working? $day would just show up as $day in the side bar.
All special passage and tag names are case sensitive—i.e. StoryInit and storyinit are not the same passage. Spell it correctly, StoryInit, and it will work.
That said, it's unclear to me whether you're attempting to print things from the StoryInit special passage. If you are, stop. Some special passages do not generate output—i.e. they're silent. StoryInit, in particular, is for initialization purposes, so it is one of the silent ones.
If you wanted to print something within your starting passage that you initialized within StoryInit, then that's what you'd do. For example, setting up a variable in StoryInit: And then printing it in your starting passage, UI bar, or wherever:
Also, as a general rule, most things are case sensitive, so unless something is specifically mentioned to be case insensitive, it's probably wisest to assume that it's not.
The reason is because you may not interleave separate macro invocations, which is what you're attempting to do there. Basically, the <<replacelink>> macro is processed first, meaning that its <<becomes>> are chopping the <<if>> into three separate unrelated pieces, thus the error. What you need to do is to have two separate <<if>> invocations on either side of a <<becomes>>.
Beyond that, the phrasing is currently a little awkward. I'd suggest a bit of a rewrite to eliminate one of the two <<if>> invocations you'd actually need with your current phrasing.
I'd suggest something like the following:
EDIT: In more detail. When <<replacelink>> is processed, its contents are cut into chunks based on the <<becomes>> tags. Each one is a separate entity which is evaluated separately when you click on its link. For example, here's the first chunk: Second chunk: Third chunk: Fourth chunk: Fifth chunk: Hopefully, that will help you visualize why you cannot embed <<becomes>> tags within the <<if>> macro. When the the second chunk is evaluated, it only contains part of the <<if>> macro, which then throws an error because it's incomplete.
Basically, yes.
Not really. I suppose reading documentation of both the <<widget>> macro and the Macro API might do that.
The cliff notes version is thus: The differences between API macros and Widget macros are minor—the <<widget>> macro actually uses the Macro API to create the widget you invoke. The most significant differences are:
For example:
As I've said before, you may place virtually any macro within a container/non-void macro—those with a closing tag—even other container/non-void macros, as long as you do not attempt to interleave their tags. Though, again, some combinations won't make a lot of sense—e.g. putting a macro which generates output, like <<print>>, within <<silently>>, which discards output.
In other words, the following are okay:
While the following are not okay: (you cannot interleave the tags of separate macros)