Forum Discussion
State-change-based interactions breaking
Hello! My team has built interactions that are coded as Complete when all states have changed to "visited." Unfortunately, these are very unstable when played in our own proprietary LMS. We have had...
Hi Kate,
Sorry to hear about the State woes.
I used to steer clear of triggers like this and always use variables...however, since Storyline refined how it handles the "When State...." part of a trigger I so far have found it bulletproof!
One thing I noticed on your screenshot that I would consider might be the culprit is that your variable trigger actually specifically identifies the two assets.
But the State trigger simple says "all rectangles"
I've never seen a trigger like that for State checks, and mine always list out each asset specifically.
So perhaps that's where the problem lies.
One reason to try to get the State solution working is that States are saved as part of the RESUME option for learners, whereas variables sometimes are not (eg. scorm 1.2)
