It looks like you're new here. If you want to get involved, click one of these buttons!
<<set $rightAnswer to [true, false, false, true, false, false, false, true, false]>> <h3>Which of these ingredients do you need for the potion?</h3> <<checkbox "$userInput" false true>>stinging nettle <<checkbox "$userInput" false true>>mandrake <<checkbox "$userInput" false true>>yellow cress <<checkbox "$userInput" false true>>fly agaric <<checkbox "$userInput" false true>>asarabacca <<checkbox "$userInput" false true>>woodruff <<checkbox "$userInput" false true>>garlic <<checkbox "$userInput" false true>>lady's mantle <<checkbox "$userInput" false true>>puffball <<button Check>> <<if $userInput == $rightAnswer>> <<goto "correct">> <<else>> <<goto "false">> <</if>> <</button>>
Second. Trying to compare two reference types as you would two primitive types. Comparing two variables containing references with an equality operator will only tell you if the references are equal. In this case, you want to compare the contents of the arrays.
Third. You should probably be using a temporary variable for the correct answers variable, rather than a story variable. Unless you're using it later on, there's no reason for it to be a story variable—you're bloating your history for no good reason.
I suggest the following for the initial setup:
And the following for your "Check" button:
An alternative, and shorter, way to code the "Check" button—if you don't mind using an Array method and an anonymous function—would be something like the following:
I have been using this button for quite some time now - thank you very much. But I was wondering if there is a way to call the function each time a checkbox is checked or unchecked (like an onclick-behavior on a container element or so).
All the other buttons I use just compare two variables (e.g. _userInput and _rightAnswer), so for the multiple-choice button I have to use the above code, which makes it somehow inelegant. If the above function checked if the right options were selected, I could just go and look if _userInput and _rightAnswer both are set to true.
(That's what "more elegant" looks like in my world at least :-) )
Unless you change that basic behavior, which you could, it's not going to work out very well.
If we leave the <<goto>> behaviour at the end of the original code aside:
Let´s say _allAreCorrect is set to false per default.
I would like the function to be called each time a checkbox is checked or unchecked and if the two arrays match, set _allAreCorrect to true. (and set it back to false if another false option is checked)
From there, I can have the <<button>>-code take care of the proper <<goto>> behaviour.
Just to make sure: In the moment, all the correct options (and only the correct ones) are checked, nothing happens. The player should have to make their choice and then click the button to see what comes next.
Just to ensure that I'm clear on this. You want to change the code you have now, which is working exactly as intended, because you find that having the code within button itself is somehow inelegant?
Please allow to elaborate on my main motivation:
In a quiz-game I have some 50+ passages, all of which finish with a button that sends them to the next level - according to their performance.
Most of these question-passages have either single-choice (radiobutton) or fill-in-the-gap (textfield)-questions, both of which allow me to use a button, that just compares the players answer with a _correct variable stored within each passage.
For about ten multiple-choice questions (checkboxes) I use the button code you provided.
This works as I expected it to, but the fact that I am using two different button codes forces me (I guess?) to put the respective button code at the bottom of each passage,
sometimes the one for the first type, sometimes the one for the checkboxes. Loads of repeated code.
I reckoned, if the variable _allAreCorrect could be set dynamically upon checking or unchecking a checkbox, I could just use one single button code, which could go like
By using just one button, instead of putting the button code at the bottom of each passage, I could put it in a PassageFooter special passage, this way avoiding repeated code.
ps. the way the next passage is determined is more complex than just goto passage A or B, this example is just for the sake of simplicity.
Markup And the check button: