Score Demo - Jane Veeder, DAI 575.5 Design of Virtual Worlds, SF State University

This file demonstrates a method for keeping score. Currently there is no mechanism - such as variables - for "memory" in AXELedge. This file demonstrates a fairly simple way to register when a surfer action has been accomplished (e.g. putting a puzzle piece in the right place) and know when a specific number of actions have been accomplished for a "win". This way, an object's parameter - it's position in this case - acts as the "memory" and a Position Sensor serves as the if-then conditional test for a "win".

Process:

1. Surfer activates a sensor or otherwise executes an action.

2. Action triggers a Set Position reaction which moves a Keeping-Score object some distance - usually out of the webcams view. This reaction is additive so every time it's triggered, the object moves the same distance again. The "Target Position" is the increment, not an absolute position. Set "Additive" to ON.

3. The Keeping-Score object has a Position Sensor attached to it. Set "Critical Position" to the final location after N increments and use the EnterPos event mode. This will trigger whatever reactions communicate a "win" or completion (text visibility, animation, sound, resetting to start-states, etc.). For the purposes of illustration, this demo has a translucent green cube showing the ending "Critical Position" but it's not necessary to denote that with a object.

Note that this Position Sensor also has links to the previous reactions which moved the Keeping-Score object along its incremental path in order to deactivate them (edit the Link parameters), thus terminating the overall action sequence. To allow the sequence to be replayed, you would include some means of resetting the Keeping-Score object to its beginning position and reactivating any sensors deactivated by the "win".

Note that - in this demo - each of the incremental actions trigger a sound BEFORE "win" is achieved. With Grouped Reactions, you can set them to play In Order, Random, Cycle in Order, etc., so that you don't need separate action-reactions to mark each incremental action.

Note that you could also have a number of Position Sensors attached to the Keeping-Score object to track and register the surfer's progress and activate new sensors along the way rather than simply having all sensors active at the outset. This requires the surfer to find clues or solve puzzles in a specific sequence.

endit: