Action Tab

Name: The name of the Action in focus will appear here.  This name will have been entered directly in the Action window but can be modified here, in the Action tab, or in the Action window.

Monetary Cost: This text box lets you enter a monetary amount which is the cost of taking that particular action.  This amount will be added on to the scenario players' "Money Spent" value each time the user performs the current Action.

Time Cost: This text box lets you enter a period of time which is the time it takes to implement that particular action.  This amount will be added on to the "Current Time" of the Scenario when the current Action is performed by a scenario player.

Is a final task: In addition to a scenario coming to an end due to a budget or time overrun, a scenario can end because a final task has been performed by the scenario user. A final task is simply an action which represents a final thing to do within a scenario, usually a report or scenario final note or explanation, but it can be any other action desired.

To set an action as a final task, check the "Is a final task" checkbox.  When the user performs this task, the following statement will appear on the horizontal bar above the Content window - "The scenario has ended.  A final action was performed." 

Prerequisites (Actions)

Prerequisites provide a means of hiding a location from the scenario user until another event has occurred, such as: a location visited, an item examined or an action taken. For instance, a field on a farm may not be visible in the Location window until the user has made a visit to the farm.

The dependencies are constructed in SBLi by using the Prerequisite Builder (see below, under adding prerequisites). Once set, the prerequisite will appear in the box under Prerequisites, in the Properties panel.

Create Prerequisites Button: (): You can create a prerequisite by clicking on the plus button. When you click on this button, the Prerequisite Builder, that specifically relates to the location;action or item in focus, will appear.

Add a condition button () will add a conditional line where you adjust this sentence: I want this item: "name of item" to be available if ...

The sentence is completed using a series of drop down menus that include specific location maps, locations, items, actions and reports that have been added to the scenario.

Once the condition is completed and changes are saved, close the dialogue box and you will see the prerequisite in the Prerequisite box.

When the scenario is played, this item will only become available when the pre-requisite has been met.

Multiple conditions can also be added to a prerequisite. Click on the () to open the pre-requisite builder again and use the add condition button () to add as many conditions as necessary. In some instances it is possible to chose different options and achieve the same result. The example below wants the location "work" to be available even if the item "Car keys" have been collected (user has chosen to drive to work) OR if the actions "Hail a bus" and "pay fare" have been performed (user has chosen public transport to get to work).

The bottom grey window provides you with the completed sentence so you can check the logic of the pre-requisite.

It is important to note the Parentheses drop downs! The prerequisite builder users mathematical logic and the correct use of the Parentheses will allow you to create very complex prerequisites, creating scenarios with excellent branching capabilities.

To test the functionality of the prerequisites you set within a scenario, click on "Reset State" under the "Scenario" menu and switch to Player mode.

When editing a scenario it is useful to keep all objects available whether prerequisites have been met or not. To temporarily disable the functionality of any prerequisites set in builder mode select the "Disable prerequisites" option under Settings>>Preferences>>.

Note: prerequisites cannot be bypassed when a scenario is played within the stand alone player.

Prerequisites can be edited easily by double clicking on a prerequisite in the prerequisite box. Double clicking will reopen the Prerequisite Builder allowing you to change the elements as required. To delete a condition in a pre-requisite you just need to select the condition and click on the delete icon (see image below).

Also note that columns widths can be easily modified by dragging the column side.

Feedback if visited: You can enter in this box the customised feedback you wish to provide to the scenario user when the scenario is finished.  You may wish to confirm that the user made the correct decision to visit this location or that this was an unnecessary visit.

Feedback if not visited: You can enter in this box the customised feedback you wish to provide to the scenario user when the scenario is finished.  You may wish to confirm that the user made the correct decision in not visiting this location - it would not have been useful - or to inform the user that not visiting this location was an important omission.