Drag items - Suppressing "Drop Correct" & "Drop Incorrect" states

Kevin,

I "think" I know what you're trying to accomplish!  If I understand correctly, then my first approach would be to NOT use the built-in Drop Correct and Drop Incorrect states as those seem to be on autopilot and can't be switched off.  

Here's what I'd do (I'll have to play with it, but wanted to let you noodle on it too!).

What if you create two new states.  Call them Correct and Incorrect.  Add the visual elements (ticks/crosses).

Now, using the tracker variable you've already created, trigger a state change to show the correct/incorrect states after the second attempt.  

Basically, we're recreating the correct and incorrect states, but taking off the autopilot and giving you more manual control.

If you're willing to load your .story file, I could take a stab at it with you.

Mike

Hi Mike, I wondered about doing away with the built in Correct and Incorrect states. I'm with you in that I can create new states but I'm not sure how I can use the variable to trigger the new states so they show the actual correct/incorrect feedback?

I've attached my project so you can see how im using a variable to control attempts.

Many thanks if you can point me in the right direction with this

Kevin

KEVIN!!!!

BOOM!  Okay, here's what you do.  

Add a player level trigger (on the base layer) for each object that sets the state to normal if your notries variable is less than 1.

This cancels out the state change for that first attempt.

WOOT!

I did this for the "Has an Infection" element to demonstrate.

Mike

PS.  Big shout out of "Thanks" to the incomparable David Anderson for a brainstorming session this afternoon.

Hi Mike,

You cracked it, or should i say pwned it!
Now that I have seen this solution working I can really see how to make some interesting custom feedback with this method.
Thanks for a timely response and perfect solution!

Kevin

This solution worked great. However, I've come to edit the project (some years later) and find that it no-longer works. As soon as I edit the project file in Storyline 1 or 2 it simply doesn't work any more. If you try opening Mike's solution you will see that this no longer works either.

My query is twofold:

1. has something changed due to subsequent Storyline revisions that "breaks" this solution?
2. how can I achieve the same effect as in the previous solution but in a way that works? (Preferably in Storyline 1 & 2)

Many thanks

Kevin

Hi Kevin,

I'll have to investigate why that worked in the past and isn't now.  But the trigger definitely isn't switching the states like it once did.

Mike

Many thanks Mike

The course I need to update has several of these multi-try drag and drop questions. They're kind of core to the approach I've used.  Anyone know how to solve this?

Many thanks

Kevin