how to verify all objects to a large/complex game are correct

Okay. Here goes..

I built a game/knowledge check in Storyline 2 where you navigate a game board by rolling two dice to move and then answering questions correctly wherever you land. (Note: the dice #s are all programmed in to roll what I set it to roll and not a random #. I'm *not* technical enough to build a game with a random # generator/etc. In hindsight I wish I had found a way to just put everything on one slide with a ton more of variables/triggers BUT I didn't and I'm not about to start over now.)

If you answer incorrectly, your energy levels will slowly deplete. Answer too many incorrectly and you won’t make it around the board.

There's also special squares throughout, somewhat remincent of chutes and ladders  (correct answer on a ladder square = you advance / incorrect answer on a chute = you go backwards).

The final square of the game board is kind of an all in square.. correct answer = you win / incorrect answer = you lose.)

Make sense?

 

WELL.. the way I built it is this: start with one slide/question 1. Incorrect answers versus correct answers will take you to a different slide. Each of those will go to 2 diff slides depending on correct/incorrect, etc. This means that there are 50 ish slides to my game but someone really only goes to 5-8 slides (depending on how many ?s they get wrong).

 

Now I have it built. I've double checked it a few times. I feel fairly confident that I've got it right and all the branching is set appropriately w/ the battery/energy levels showing properly for whatever slide you branched to BUT I'm paranoid. Since I don't feel 100% confident in it yet, I'd love to triple (quadruple) check it. But how? There's like 20 possible combinations of things and it just gets pretty overwhelming.

 

SO does anybody have a good systematic approach to help me triple check this weird game? Anybody want to play it a few times and see if you spot any discrepancies?

1 Reply
Allison LaMotte

Hi Macy,

If i were you, I would take a systematic approach. I would start by making a spreadsheet or mindmap that maps out all the possible paths, and then I would test out each path individually. Depending on how many possible paths there are, that could take awhile but it's the only way to be 100% sure it's working properly.