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...
Forum Discussion
I've never had a problem with triggering an action based on objects being in the Visited state—as long as the entire interaction takes place on one slide (as Walt referred to).
If the user leaves the slide (e.g., a custom menu slide), I use variables to track what they complete elsewhere. And I use a custom state to indicate a given interaction is done.
- I typically avoid Visited in these cases, because it's a built-in state. An object will automatically change to Visited when clicked. The change is not based on the user completing something elsewhere.
