[BUGFIX-Suggestion] To better meet TCR # 049 (STR) and stop destroying saves
This is a suggestion to better meet TCR # 049 (STR) in the future.
TU8 Passes TCR # 049 (STR).If you load a world on TU9, go to the end, then save. Exit the game, change USB so you have TU8 instead of TU9, then load that game offline, it will respawn you in the overworld with a completely new seed. Your old seed and everything done on that overworld will vanish. Being the type who likes/does test things I had to try that. Surprised it worked at all. Kudos for handling it gracefully. Slight down marks for not sending to the original overworld and instead spawning a whole new one thus losing all work on the original world.The graceful handling shows TU8 as capable of handling and passing TCR # 049 (STR).Further notes are that this occurs regardless of entering The End or not. I've not yet confirmed if one needs new items in inventory or not to trigger this re-write of the save with a whole new seed/world.
Test Characteristics:
Xbox 360Save & Profile on HDDTU8 was saved on USB_1 formatted by 360
TU9 was saved on USB_2 formatted by 360
Status was offline from Xbox Live
Test Scenario:
Start game with USB_1 plugged in to the 360 and USB_2 not plugged in.
Click Play Tutorial.
After game loads, press B, then A 4 times (once per prompt).
Exit the game making sure to save.
Turn off the 360.Plug USB_2 to the 360.
Start game and load the previously saved world named 'Tutorial'
Exit the game making sure to save.
Turn off the 360.Remove USB_2 from the 360 and leave USB_1 connected. (or clear cache removing all TUs).
Start game and load the previously saved world named 'Tutorial'
The seed will be overwritten to seed 0 just by the action of loading the world and everything will be gone. This damage cannot be reversed. Connecting USB_2 after this and loading that same save will also reflect the damage done by having loaded on TU8 even if one exits the game without saving after the load has been done.
Future Suggestion: (example TU10 trying to load a TU11 world as you can't change old TUs obviously)
I will suggest for future updates the TU should either choose not to load and give warning with a message the world/save was created on a newer version than the one attempting to load it.
I would also suggest future TUs if they allow loading such a save/world from a newer TU and it does not understand your current position then it should place you in the overworld that already exists for that save instead of the current action of creating a whole new world and seed. It would likely be easier to just have TUs prevent loading of saves from newer TUs.
Intent: as a user I expect that my old saves will load correctly with all work that I have done. If not I expect appropriate measures to be taken to prevent damage to the saves and progress already made. Therefore, regardless of which storage device is attached during an offline status the program should react appropriately..
Side note to everyone else who might read. You should always do this when downloading title updates for games. That will allow you to keep 2 (or however many USB you format for the 360) Title Update versions.
EDIT: Updating notes as it has been pointed out to me the destruction of the work in the save means TU8 failed TCR # 049 (STR) because a subset of that is TCR # 030.
Games must consider TCR # 030 (UI), UI Confirmation of Destructive Actions, and not delete invalid or damaged content without first receiving confirmation from the user before any destructive action.
Since loading the world on TU older (or none) than the one creating it automatically takes the destructive action it fails TCR # 030 and by extension TCR # 049.
EDIT: as of TU 13 this bug is still valid. Just update the version numbers above replacing as appropriate. Also, the base XBLA package for this game still suffers from this bug since there has never been a full replace TU issued (like the one that was issued against MtG 2012(think it was the 2012 MtG) at one point in the past).
EDIT: Re-added the carriage return line feeds that vanished when edit of the title.
I've updated the notes for this suggestion and I'm adding the following information:
Unfortunately due to the type and nature of the bug, end users can not test/confirm it on TU9 until TU10 comes out. Only 4J Studios and Microsoft can check the bug prior to a TU coming out on the current TU version. I can confirm the bug exists on TU8 as related to TU9. Obviously though I cannot confirm if it exists on TU9 without TU10's availability. By extension end users will not be able to check for the bug in TU10 until TU11 is released.
Awesome. Kind of a strange bug to be hunting down, I'm not sure how many people would naturally run into this. Its still very cool to see someone else interested in why these updates are handled so horribly, why so many things are missed, and also coming up with suggestions to help fix the problem. At least you seem to know what your talking about. I know very little about testing, so it can be difficult coming up with helpful suggestions. Keep it up kelendral.
Sadly instead of updating the main package before putting it on DVD, they released the same broken main package on DVD.
This is still an issue with the main XBLA package and the TUs.
Just a reminder. Loading any save created with a TU, or TU newer than any on the current Xbox attempting to load the save WILL DESTROY THAT SAVE IRREVOCABLY!
There are so many ways to end up with the wrong or no TU.
Clear cache deleting TUs (including one used when save was last loaded), load save, save destroyed.
Remove storage device with current TU, leaving a storage device that only contains older TU, load save, save destroyed.
The correct way to fix this was exactly as described and should have been done as recommended before the DVD release. Same as the original MtG, issue TU that forces re-download of a new main XBLA package that includes a fix for this issue. All newer TUs should then only apply to that main XBLA package. STILL NOT DONE!
This is a suggestion to better meet TCR # 049 (STR) in the future.
TU8 Passes TCR # 049 (STR).If you load a world on TU9, go to the end, then save. Exit the game, change USB so you have TU8 instead of TU9, then load that game offline, it will respawn you in the overworld with a completely new seed. Your old seed and everything done on that overworld will vanish. Being the type who likes/does test things I had to try that. Surprised it worked at all. Kudos for handling it gracefully. Slight down marks for not sending to the original overworld and instead spawning a whole new one thus losing all work on the original world.The graceful handling shows TU8 as capable of handling and passing TCR # 049 (STR).Further notes are that this occurs regardless of entering The End or not. I've not yet confirmed if one needs new items in inventory or not to trigger this re-write of the save with a whole new seed/world.Test Characteristics:
Xbox 360Save & Profile on HDDTU8 was saved on USB_1 formatted by 360
TU9 was saved on USB_2 formatted by 360
Status was offline from Xbox Live
Test Scenario:
Start game with USB_1 plugged in to the 360 and USB_2 not plugged in.
Click Play Tutorial.
After game loads, press B, then A 4 times (once per prompt).
Exit the game making sure to save.
Turn off the 360.Plug USB_2 to the 360.
Start game and load the previously saved world named 'Tutorial'
Exit the game making sure to save.
Turn off the 360.Remove USB_2 from the 360 and leave USB_1 connected. (or clear cache removing all TUs).
Start game and load the previously saved world named 'Tutorial'
The seed will be overwritten to seed 0 just by the action of loading the world and everything will be gone. This damage cannot be reversed. Connecting USB_2 after this and loading that same save will also reflect the damage done by having loaded on TU8 even if one exits the game without saving after the load has been done.
Future Suggestion: (example TU10 trying to load a TU11 world as you can't change old TUs obviously)
I will suggest for future updates the TU should either choose not to load and give warning with a message the world/save was created on a newer version than the one attempting to load it.
I would also suggest future TUs if they allow loading such a save/world from a newer TU and it does not understand your current position then it should place you in the overworld that already exists for that save instead of the current action of creating a whole new world and seed. It would likely be easier to just have TUs prevent loading of saves from newer TUs.
Intent: as a user I expect that my old saves will load correctly with all work that I have done. If not I expect appropriate measures to be taken to prevent damage to the saves and progress already made. Therefore, regardless of which storage device is attached during an offline status the program should react appropriately..
Side note to everyone else who might read. You should always do this when downloading title updates for games. That will allow you to keep 2 (or however many USB you format for the 360) Title Update versions.
EDIT: Updating notes as it has been pointed out to me the destruction of the work in the save means TU8 failed TCR # 049 (STR) because a subset of that is TCR # 030.
Games must consider TCR # 030 (UI), UI Confirmation of Destructive Actions, and not delete invalid or damaged content without first receiving confirmation from the user before any destructive action.
Since loading the world on TU older (or none) than the one creating it automatically takes the destructive action it fails TCR # 030 and by extension TCR # 049.
EDIT: as of TU 13 this bug is still valid. Just update the version numbers above replacing as appropriate. Also, the base XBLA package for this game still suffers from this bug since there has never been a full replace TU issued (like the one that was issued against MtG 2012(think it was the 2012 MtG) at one point in the past).
EDIT: Re-added the carriage return line feeds that vanished when edit of the title.
Unfortunately due to the type and nature of the bug, end users can not test/confirm it on TU9 until TU10 comes out. Only 4J Studios and Microsoft can check the bug prior to a TU coming out on the current TU version. I can confirm the bug exists on TU8 as related to TU9. Obviously though I cannot confirm if it exists on TU9 without TU10's availability. By extension end users will not be able to check for the bug in TU10 until TU11 is released.
This is still an issue with the main XBLA package and the TUs.
Just a reminder. Loading any save created with a TU, or TU newer than any on the current Xbox attempting to load the save WILL DESTROY THAT SAVE IRREVOCABLY!
There are so many ways to end up with the wrong or no TU.
Clear cache deleting TUs (including one used when save was last loaded), load save, save destroyed.
Remove storage device with current TU, leaving a storage device that only contains older TU, load save, save destroyed.
The correct way to fix this was exactly as described and should have been done as recommended before the DVD release. Same as the original MtG, issue TU that forces re-download of a new main XBLA package that includes a fix for this issue. All newer TUs should then only apply to that main XBLA package. STILL NOT DONE!