Version 2.3.5

Bug Fix

• Don't clear answers after order questions in the generated story scripts.

Version 2.3.4

Updates

• Use graphics names for order question answer options (rather than generic "scene0", "scene1" names) to match what the SAR Opal game loads, which means they will now be marked as correct or incorrect.
• Update demo story to include question type and an order question.

Version 2.3.3

Bug Fixes

• Fix undefined variable name.

Version 2.3.2

Bug Fixes

• Fix variable names for reporting performance metrics.

Version 2.3.1

Bug Fixes

• Fix JOIN and WHERE logic in database query to get the next new story to play.
• Fix the path prepended to scene graphics when sending a load graphics message to Opal.
• Remove duplicate call to record_story_loaded.
• Fix minor syntax errors and typos.

Version 2.3.0

BUG FIXES

• Record user responses to questions in the db.
• Fix JOIN logic in sql query to get next new story to play.

FEATURES

• Add QUESTION line with meta-info about questions to story scripts.

Version 2.2.3

BUG FIXES

• Swap two db arguments that were in the wrong order.

Version 2.2.2

Bug Fixes

• Reopen repeating script for reading each time we repeat it.

Version 2.2.1

Bug Fixes

• Fix an if that was supposed to be an elif.
• Move ros node initialization in ss_game_node out of the launch_game function
  and into a class variable, where it used to be, because the ros node was not
  initializing from the function.

Version 2.2.0

Additions

• Add some unit testing for the script parser, database manager, and personalization manager.
• Add information on unit testing to README.
• Add scene highlighting commands to demo scripts and generated story scripts.
• Add performance metrics for all types of questions asked to GameState.END messages.
• Add session script selection for non-demo sessions.
• Add value checking for session numbers when selecting which session script to load.
• Add "level" field to functions for getting new or review stories so we can account for the current level, since not all stories have the same emotions present at every level.
• Send GameState.READY message when the game node is ready to start the game.
• Add "STORY SETUP" command to scripts and corresponding "pick_next_story" function to the personalization manager so that we can pick the next story without necessarily loading it on an Opal device or playing the story right away.

Bug Fixes

• Change "angry" to "mad" and "afraid" to "scared" in stories.
• Change names of the demo scenes to load based on the actual graphics used for the demo story.
• Update graphics names generated from the ods story spreadsheets that are stored in the database so that they match the actual graphics files.
• Rename "level_id" field in the database tables to "level".
• Refactor main game node so parsing command-line arguments and launching the game are separate functions.
• Refactor SQL queries for clarity and simplicity.
• Fix generation of order questions for story scripts to correctly list responses.
• Make names of all generated story scripts and stories imported into the database lowercase.
• Fix string concatenation in multiple places so everything concatenated is converted to a string first.
• Fix a list copy so the list is actually copied (before the reference to original list was being used for the new list too).
• Add missing "self" as first argument to a couple function definitions.
• Fix database queries that needed to use a left join, not a join, in cases where one of the joined tables may be empty.
• Fix database queries that didn't use "fetchone()" to get the first result to do that.
• Fix levels table initialization to have correct number of answer options listed for each level.
• Fix bug where we tried to load the next story on the Opal device before we picked what the next story would be, so none of the story scene details were available. As noted above, added "STORY SETUP" and "pick_next_story" function to address this.