Well, so far so good, but what if the first two eyes don't match? We still need to compare the first to the third. Event #23 takes us to that option. Event #24 looks for either "result1" OR "result2" for matches. If either is found, then Events #25 to #31 append HUD text in a similar manner as before only with a smaller reward.
BUT, what if none of the eyes match? Event #32 handles that for us and randomly "Chooses" its HUD feedback. See the illustration below.
Conclusion
There you are! 32 Events creates a simplified Slot Machine IGM. You should consider replacing the artwork with a different theme once you have a license to do so. For example, I use this "Slot Machine" game mechanics as a dueling system between two combatants. (Hint, Hint! See example in the Scirra Arcade)
Here's the "error-ridden" slot machine.c3p example with HTML layers. If you decide to purchase this from the Construct Asset Store, you'll have all its artwork, a Developer's Guide, permission to use it in one or more projects, and more detailed development information on its construction and integration with external CSS files and parent RPGs (a PHP script is supplied for client/server deployment).