I can't get this one trigger to work!

Jun 15, 2015

Hello! I'm working on a course in Storyline using the elearning brothers templates and the correct answers and responses are registering for all of my quiz questions except one. It's question 3, the correct answer should be "fundraising". Unfortunately, it's registering as incorrect. I have tried everything I can think of to fix it. Any help would be appreciated.

6 Replies
Luke Benfield

Looks to me that since it is a template, there are triggers set up such that any answer could be correct or incorrect (each set of answer triggers has a 'show layer - incorrect' and a 'show layer - correct' set of triggers). I deleted the extra 'show layer - correct/incorrect' triggers so that Option D would have the 'show layer - correct' and the others would only have 'incorrect'.

Also, there is a condition on the 'Option D show layer - correct' trigger that lists Option C being correct, and it's set as 'true'. I changed that to the 'Option D is correct' variable, and left it as 'true'. 

Everything worked after that.

Jan Vilbrandt

Hi Luke, hi Emily,

sorry it's not this easy as Luke described...

Goto layer "Questions3".

The triggers which shows layer "Question 3 - Correct"   have got a wrong condition... (maybe it is already wrong in the template).

Every of the four triggers (Option A, Option B, Option C, Option D) checks against the variable "21536CorrectAnswerC".

The correct conditions are:

Option A -> 21536CorrectAnswerA

Option B -> 21536CorrectAnswerB

Option C -> 21536CorrectAnswerC

Option D -> 21536CorrectAnswerD

Because your correct answer is "D", you will not get the "Correct Layer" with any of the four answers...

If you change the conditions it should work.

E.G.:

Show Layer "Question 3 - correct"

If the user clicks "Option A"

With condition:

21536AnswerCorrectA == is equal to True

AND 21536MultiResponse == is equal to False

++++

By the way:

Using the operator "== is equal to - no case sensitive" is not neccessary because the variable is a boolean type. Instead use the simple "== is equal to".

CU,

Jan

This discussion is closed. You can start a new discussion or contact Articulate Support.