Interactive board games in Lectora

Recently I sat in on the Lectora Inspiration Wednesday, “The Magic Behind Powerful eLearning Design – Learning Theory”. I always appreciate the efforts of organisations such as Trivantis to reach out to the e-learning community and offer webinars such as this to increase my knowledge as an instructional designer and developer.

The topic was really about designing e-learning to ensure it met the learner’s needs but one of the other things I took away from the session was the example; a board game style interaction so I thought I would have a go at creating my own.

I wanted to make the game random so that it would give a more unpredictable element to the experience.

Clicking the die would generate a random number between one and six, and the counter would move the relevant number of spaces on the board. When it stopped a piece of information or a question would display. The learner would need to read the information or answer the question before they could move on to get to the end of the game.

Such interactions are appropriate for presenting bite-sized information in a more engaging way than bullet points. It does take longer to create, of course, so you would need to consider whether the cost, time and effort is justified (although read on to learn about a shortcut). Also the version I created included a random element – the throw of the dice to move the counter – which meant that the learner might not see all the content. As a result you might need to include a summary of the learning points at the end.

It’s the sort of thing that could be used to help reinforce learning particularly on a topic where the learners feel they may already know the subject and may have got into bad habits. It’s an interactive way to present the information they should already know but may have forgotten as fun facts. The multiple choice questions scattered throughout add an extra element.  If you would like to try the exercise, click on the screenshot below

screenshot of e-learning game developed in Lectora
Screenshot of the finished game. Click on it to launch the game in a separate window

There were a few things I needed to do to make this work.

First of all I needed to capture a random value to send the counter on its way around the board. Lectora is one of the better authoring tools when it comes to managing variables. Somehow to me, at least, it seems more intuitive than some of the other products available. It allows you to capture a random value to a variable when you are setting up an action. If you are interested there is a great video on the Trivantis website about working with random variable values.

Screenshot of Lectora Variable dialog box showing random value
At the bottom of the value box click on the expand button to display the dialogue box and then click on the Random Value button. Choose the smallest and largest numbers that can be entered and click OK.

The next thing that I needed to do was to get the counter to move the relevant number of spaces. This was slightly more problematic for a couple of reasons. First of all I needed to counter to move from the square it had landed in which would obviously vary depending upon the random value generated. Secondly I needed to get the counter round corners; as you can see from the screenshot the board game meandered a little bit.

I spent some time wondering whether I could capture the random value and use that to tell Lectora where the counter had got to and needed to move from. In the event it seemed easier to introduce a learner interaction to capture that information. The learner needed to close the box that displayed when they reached the next square; I added an action to that close button to tell Lectora where we were.

Lectora isn’t so great when it comes to animating objects but it does have the move to action which allows you to move objects from one position to another.  It is possible to have objects move in a straight line. In this module I wanted them to go around corners as well.  The solution here was to have a series of move to actions in action groups. The first action group would take the counter to the corner and then trigger a second action group that would move the counter on around the corner (in one or two cases there even needed to be a third action group when the counter had to go around another corner). A crucial thing was the timing of the actions. I needed to put a delay on the actions turning the corner to make sure it didn’t happen until the counter had completed its first move; otherwise it wouldn’t move all the way.

In this screenshot action group “A11 move04a” moves the counter a set distance and then fires a second action I called “turn corner” which then triggered action group “A11 move04b”

Another issue I needed to overcome was an appropriate naming convention for the action groups. I prefix them with the word “action” so that I can differentiate them from groups containing objects. The rest of the name is made up of a description of what the actions will do. In this case I also had to number the actions to keep track of them all. However, if the name becomes too long it is difficult to see it all in the dropdown list when you setting up action to run an action group, as you can see in the picture below. I had to come up with a shortened naming convention in this case.

The names of action groups were shortened so that I could see them all in the target dropdown list.

I hope that you found this an interesting read on some of the practicalities on using Lectora in creating an interactive board game with random variable values and multiple move to actions. One of the joys of Lectora is that it has many ways of doing the same thing so I would be interested in others may have resolved the same challenge. Please add your comments in the comments field at the bottom of the page.

And that shortcut I mentioned? If you feel this interaction might be useful for you but you don’t have time to create it yourself, for a short time I am making the Lectora files for you to use to base your own version on. Simply get in touch to find out more.

Things I wish I’d known when I first starting using Lectora Part 1

Opening new software for the first time can be intimidating.

All these features which in time will make your life easier can look overwhelming right at the start.

I have been using and training people in Lectora for many years now.

I thought I would put together some of the things I have picked up over the years that might be useful to new users.

This is series of infographics. Number 1 is all about the title explorer, layering, inheriting and naming objects.

Click on thumbnail below to download the first one. 

And watch this space for future infographics.

Infographic showing how to use the Title Explorer in Lectora
Infographic: Starting Lectora 1 – The Title Explorer

Changing contents

USING THE CHANGE CONTENTS ACTION TO HAVE BUTTONS CHANGE APPEARANCE

Lectora has an option to change the state of buttons but currently the states are active or inactive only (there is also a down and over state when you click or hover over them). There is no option to create a selected or visited state, for example. You may want to include these to allow the learner to see which buttons they have clicked to keep track of their actions.

Trivantis may have plans to update this but in the meantime a simple workaround is to create multiple image files for active, selected, visited and inactive, and use the change contents action to have them switch state.

I have created a couple of examples which you can view from the links below. You can also download Lectora library objects from the same links.

Example 1: active, inactive and selected

In the first example, the learners are required to click the buttons in order. There are three images for each button: inactive, active and selected. This example could be used if you need your learners to click on topics in a certain order. The inactive topics become active (and change to the active image) once the previous button has been clicked. A chosen button changes to the selected state until another button is clicked.

Example 2: active, selected and visited

In the second example, the learners can click on the buttons in any order. Clicking on a button changes its state to selected and any previously clicked buttons to a visited state.

How this was achieved

  1. Create the images for the buttons in each state and add them to the page as images.
  2. Delete all but the images for the state you want them to be in initially
  3. Have an action on each image to change the contents of the object to the selected state image when clicked
  4. Create additional actions to change the states of the other buttons to visited, active etc. You will need to include variables to record when a button has been clicked

Responsive development with Lectora 16

Lectora 16 is the latest version of Trivantis’ rapid authoring tool.

They’ve jumped straight from 12 to 16, using the current year (possibly to avoid unlucky 13). The selling point of the new version is responsive design – being able to create content that can be deployed to different sized platforms from desktop down to phones.

Before Lectora 16 if I needed to create content for different sized platform I had to create different Lectora files

Previously with Lectora I either created multiple versions of the same module, maybe with the theme templates to quickly repurpose the content; or I put some code that detected the platform and resized accordingly. This didn’t allow you to layout the content differently for the different sized platform – which is where Lectora 16 comes in. It allows you to visualise how it will look on different platforms so that you resize and reposition objects accordingly.

So how does it work in practice?

I thought I would find out so I rebuilt an existing piece of content in Lectora 16. You can view the results here.

If you have had any experience with Lectora 11 or 12 the overall appearance doesn’t look too different. There are two main differences, however.

screenshot of New Responsive Title in Lectora 16 The first is on the splash screen which now includes the option to create a new responsive title; there is still the option to create standard e-learning content. If you change your mind and decide that you need to create a responsive module after all you can’t switch; you’ll have to start from a new title. Of course, you can always import the frames from the old module into the new one.


The second is the new toolbar with a series of different devices from a desktop in the middle to tablets and phones (landscape and portrait). The two things to recognise at this stage are (a) the arrows extending out from the desktop – the layout of the other devices depend upon this one; and (b) the colours of the different devices – which we will return to shortly.

When developing responsive content start from the middle – the desktop version. Layout the objects on the screen; the text boxes, images, etc, and add all the interactivity as required. Once you have that sorted move out to the next stage; the tablet. Begin with the landscape version as they may not be too many changes to make here; check the content, and re-position and resize accordingly.

As you do so, take a look at the sizing handles and note how they change colour to match the colour of the device at the top of the screen. This lets you know that it will be different to the desktop version. Changes made here will cascade down to the phone level. You can of course make changes specific to that level as well.

screenshot of the reset button in Lectora 16
If you want to put things back the same as the desktop level click the reset button.

screenshot of the text scaling tool in Lectora 16
There is also an option to change the text size in the text boxes as a percentage of the original size.

 

 

 

 

 

 

At the lower stages you can substitute different sized imagery. This is particularly useful when switching between portrait and landscape views. Also you could use it display different information; have an exercise in landscape and get the learner to turn their device to see more information once they have completed the exercise.

I found it great way to develop content for multiple platforms.

It’s cleverly laid out so the developer can quickly see what they’re doing for each size of content. The colour coding works well in this regard. It doesn’t need any coding knowledge, just some patience switching back and forth to get everything laid out just so. But it is less work than having to build multiple versions of the same file. Publishing is no different except that the published folder contains three new subfolders for each device. File size does not look overly massive.

I did experience one or two issues. The first one was that text in the text boxes did not always appear as I expected. Sometimes it would be cut off by the edge of the box. The best practice appears to be to over-size the text boxes to allow the text room to grow. This fits in well with the best practice of not overloading content on smaller devices.

The second issue was more to do with the appropriateness of re-purposing the same content for different sizes, especially a mobile phone. Whilst you can deliver complex exercises on a desktop or tablet, a mobile phone may be more suitable to smaller bite sized activities. So you may need to consider whether the content you are creating is suitable for delivery on every platform. However you can have unique content for each device – simply drag it off the page when it’s not needed. And I have not tested this yet but I imagine there are ways that you can create specific pages that are only accessible in certain formats. I would be interested to know if anyone has had a go of this yet?

You can view my effort here. Note this module was created in a trial version of Lectora 16 so you will see a small window display to start with.

If you use rapid authoring tools and need to create simple content for multiple platforms, Lectora 16 could be for you.