The Sudoku Challenge:
I saw a challenge in the Articulate eLearning Heroes Community regarding someone looking for a Sudoku template. I love the game. I really do. My favourite version are called Samurai Sudoku (example). This is where 5 puzzles merge into one large puzzle. I’ve been wanting to create a Storyline Sudoku for sometime, so I decided to answer the call.
I’ve created a one puzzle template that could be used over and over with some minor modifications. My version uses the traditional numbers within the squares, however, the request was for a puzzle where images could be placed in. The template I created can easily be modified by changing just the states of the squares. In theory, the user needs to only change the states on one square and then format paint that over each other square. The triggers to make it all function would not need to be altered.
The instructions for formatting the template into your own puzzle are included on the base layer (the Setup Layer). There are 2 additional layers. One is the Puzzle layer, where the person would work through the puzzle. The other is the Solution layer, where the designer adds in the correct solution.
Basic instructions for setup are:
- Enter in the “solution hints” into the appropriate Sudoku squares on the Setup Layer.
- Copy all Sudoku squares and paste these on to the Solution Layer. (note – each time you re-use the template the Solution layer must not already have these items on it.) Enter in all the correct answers into this layer. You may want to highlight the squares that are the original hint squares.
- Return to the Setup Layer. Lock the hint squares in the timeline on the Setup Layer.
- Copy all Sudoku squares and Pencil (number selection) squares from the Setup Layer and paste onto the Puzzle layer (note – each time you re-use the template the Puzzle layer must not already have these items on it). Every square will copy over except the hints squares that you have locked.
- Make sure the Puzzle Layer has “prevent base layer from being clicked” selected. This will stop users from being able to click/change the hint squares when they are solving the puzzle.
Somethings to note that are different from typical Sudoku apps:
If you’ve every played Sudoku online or in an app you might be use to having incorrect answers marked as you place them in the puzzle. You may be used to having all the “5s” highlight if you have selected one in the puzzle, making it easier to see where to place others. You might have, what seems to be, an unlimited number of puzzles.
If you’ve ever done a Sudoku puzzle on paper then you’ve never seen these features.
Think of this game version/template similar to that of a paper version. There are no fancy features. This makes it more usable as a template for everyone.
There are a few reasons for this and one is time. I have no doubt it could be all programmed in, but the number of variables and even coding require in-order to create this is a bit more than slightly mindboggling. Because of this reason, creating the triggers and conditions to show why a square might be correctly or incorrectly placed would work for the demo puzzle I created, but would not work for another puzzle of numbers placed into the template.
I did not create a trigger to stop a user from seeing the solution until all squares were filled in, but that could easily be added to the Puzzle layer.
Update May 25:
Once I posted this and then tested it further I noticed some of the squares where not showing as chosen and the numbers could not be entered in. Working backwards from a completed file to a template version I missed copying triggers over for boxes in which I had already added numbers into and now had created blank. I’ve fixed this in the template.
A discovered one more assumption that needs to be made of the user trying to complete the puzzle, and that is that they will only select one square to add a number into. If you pick more than one square they will both display as “chosen” and then when a number is picked the number will go into both squares. (a problem filled with variables and triggers for another day)
Finally, one last thing to be aware of when using the template, and this I have added right into the notes of the template. I found that when I was adding in my hint solution squares that the program took a moment to respond to which square I had clicked. If I went too fast and typed a number into an incorrect square, deleted it and put it in the correct one, the incorrect square would now have an incorrect state. By this I mean, if I typed in 8 and realized that was wrong and removed it. Then the state “8” would now also be appear just blank. I had to go into the state and edit it, adding the “8” back into the state.
Oh the quirks of pushing designs to their limits are always fun to explore and then ultimately solve.