When you’ve got a rather dry quiz or knowledge check, sometimes incorporating it into a game is just what’s needed to make the experience more enjoyable. While games and gamification aren’t a magic fix for bad content, they can add a spark of fun for an assessment that’s useful but a bit repetitive.

In this bingo-like download, learners test their knowledge of Storyline 360 keyboard shortcuts. Get a quiz question right and the corresponding shortcut on the bingo card gets a correct stamp. Get it wrong and the shortcut gets a red lock stamp instead. All they need is five correct stamps in a row to bingo. But as you might have guessed, those incorrect lock stamps can make completing a line tricky.

With the help of hotspots, states, and variables, it’s easy to create a game like this in Storyline 360. Make each bingo square interactive using hotspots. States make it simple to mark a square as correct or incorrect. And variables keep track of when a player gets five in a row. Put it all together and you’ve got a quiz that makes learners excited to test their knowledge!


View this project in action.

This template will work for folks using Storyline 360, the continuously updated version of Storyline included in Articulate 360. Want to try it out? Get a free trial of Articulate 360 right here.

Will Illingworth

When testing in Storyline 360, we occasionally and inconsistently have an issue where the win condition does not trigger "when the timelines reaches .25s". Example: User sets the ABCDE row to True, all States have successfully triggered, and the page looks like it should be done, but the appropriate "Winner" layer does not trigger. IF the user clicks any other hotspot on the screen (correct or incorrect), they will receive the appropriate feedback layer (correct or incorrect) for that hotspot and THEN the "Winner" layer will trigger for the ABCDE row. This is reproducible for different winning rows or columns. My best assumption is that the Winner layer's trigger is time based (when timeline reaches .25s on layer randomNumber) and that it is either never reaching .25s or is skipping ... Expand