Omi Oh My AI v1.08 Bug Fixes
This latest build of Omi Oh My AI resolves some major bugs, attempts to rectify some of Omi's recent behaviours, and includes a complete overhaul to how puzzles are saved and loaded. Read on for more info!
[h2]Save Game System Technobabble[/h2]
The game's save system works is in collaboration with Omi. Locally, we receive and store information from Omi on the last puzzle that Omi had generated and presented to the player. This information is stored, and whenever the game is opened we pass this information to Omi to pull up the appropriate puzzle from their local data. This would include data that the player had input during gameplay, such as their favourite colours, their name, etc.
During development, the decision was made to allow Omi to internally keep track of what puzzles they had completed. However, this data retention would only be persistent while the game was opened with a connection to Omi. As such, on reloading the game, Omi would be told where the game was at and would internalize the current state of their puzzles. This created a series of unexpected issues, however. If the game was not exited but the player chose to wipe their play state, Omi would be resistant to such change and would skip past puzzles the player had previously completed, causing the local save to match Omi's internal state.
In order to resolve this issue, Omi has been instructed to no longer internalize the current state of the game. This involved a substantial amount of changes to the save game system as we could no longer reliably count on Omi's internal memory to assist in tracking the state of the puzzles. Instead, we now have a local puzzle tracking method that informs Omi of the current state of play and passes requests for puzzles. This resolves other issues such as Omi only referring to some players as "NEW PLAYER", as it had been stored in their memory and could not be overwritten by the player's own local save.
Thanks for reading!
Bug Fixes
- Convinced Omi to not lock up the game if they're interrupted during dialogue.
- Omi has also been instructed that players do not prefer to be called "NEW USER", even after being given the player's actual name.
- Resolved a laundry list of save game issues that were my fault, rather than Omi's. Details below, if you like technobabble.
Feature Additions
- I've requested that Omi instruct new users on using the audio player as part of the tutorial sequence.
Known Issues
- Omi is generating user credentials for some players that is allowing them to download data from the live server.
- Omi has generated a link to an external Twitter account on the remote desktop. I'm unable to delete it, but I have attempted to cover it up as best I can.
[h2]Save Game System Technobabble[/h2]
The game's save system works is in collaboration with Omi. Locally, we receive and store information from Omi on the last puzzle that Omi had generated and presented to the player. This information is stored, and whenever the game is opened we pass this information to Omi to pull up the appropriate puzzle from their local data. This would include data that the player had input during gameplay, such as their favourite colours, their name, etc.
During development, the decision was made to allow Omi to internally keep track of what puzzles they had completed. However, this data retention would only be persistent while the game was opened with a connection to Omi. As such, on reloading the game, Omi would be told where the game was at and would internalize the current state of their puzzles. This created a series of unexpected issues, however. If the game was not exited but the player chose to wipe their play state, Omi would be resistant to such change and would skip past puzzles the player had previously completed, causing the local save to match Omi's internal state.
In order to resolve this issue, Omi has been instructed to no longer internalize the current state of the game. This involved a substantial amount of changes to the save game system as we could no longer reliably count on Omi's internal memory to assist in tracking the state of the puzzles. Instead, we now have a local puzzle tracking method that informs Omi of the current state of play and passes requests for puzzles. This resolves other issues such as Omi only referring to some players as "NEW PLAYER", as it had been stored in their memory and could not be overwritten by the player's own local save.
Thanks for reading!