Setting different trigger for Submit button on second attempt of D&D Interaction

Nov 13, 2020

I have a two bucket sort drag and drop with max two attempts. My customer wants to have it work like this:

FIRS ATTEMPT
User sorts, hits player submit button
If it's correct, the correct layer shows, user hits continue, is routed to next slide
If it's incorrect, the try again layer shows, user hits try again, is routed back to base layer which resets and attempt is tracked (I think I have this much working properly using TryAgain variable)

Here's the kicker... I haven,'t been able to figure our using variables or conditions and I don't know enough about all the triggers)

SECOND ATTEMPT
User sorts, hits player submit button
If it's correct, the correct layer shows, user hits continue, is routed to next slide
If it's incorrect, the incorrect layer shows, then she wants the learner to be able to see their results visually (what's red and green in the different buckets), then take them to a post Quiz Review

She also wants the next button hidden because it was causing her confusion, and thinks Users will hit next instead of submit. Is there a way to have the player next button appear and replace the submit button after the second attempt and after the User clicks review to see the results? 

If so, then they can click next and go to the Post Quiz Review?

I am teaching myself SL and it is VERY robust. I know there is a lot I can do with variables, but I am not sure I can make this work the way she wants. She also wants there to be no states on the drop objects on the first attempt, but then have states on the second attempt. I am telling her that is not doable.

Any advice is much appreciated! 

3 Replies
Math Notermans

Having a sample would clarify your questions for sure.
About the states...well if you donot trigger a custom state it offcourse is not visible to the user... so as far as the user knows, non-existing.

So having a specific state enabled on a second attempt is possible...it is on the drop object on the first attempt, but only not visible/active. 

If secondAttempt = true,
then show my specialState
else
dont show my specialState

Lea Flynn

Hello!

Thank you for the info. I am not sure where/how to write the conditions that way. It only gives me the option to add the variable in a very structured way and no ability to write anything myself, like how you have it written above.

I will attach the file after I figure out how to save as a .story file. I can export to HTML Articulate online (which I don't have an account for), LMS (which I get an error when trying to publish), and CD and Word (but guessing that will not produce a .story file. Help! 

Your help is VERY MUCH appreciated. :)

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