You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After enabling JSON editing, when changing a data value for mission progress NomNom crashes with a System.IO.IOException and a message "Cannot create a file when that file already exists.".
Reproduce
Steps to reproduce the behavior:
1.Edit JSON for save
2. Search for timed mission (Bio_Ship2 is the mission I am encountering the issue with)
3. Set the "Data" key to 1
4. Click ok
5. Accept the prompt to save changes
6. Go to File > Save account
7. Profit?
Expected Behavior
json file changes saved without NomNom crashing. Additional clarity on whether the confirmation prompt (the one that pops up after editing the json and hitting ok) saves the changes to the save would be a nice bonus (is it supposed to save the account for me or is the user supposed to manually hit save account despite that confirmation?)
Description
After enabling JSON editing, when changing a data value for mission progress NomNom crashes with a System.IO.IOException and a message "Cannot create a file when that file already exists.".
Reproduce
Steps to reproduce the behavior:
1.Edit JSON for save
2. Search for timed mission (Bio_Ship2 is the mission I am encountering the issue with)
3. Set the "Data" key to 1
4. Click ok
5. Accept the prompt to save changes
6. Go to File > Save account
7. Profit?
Expected Behavior
json file changes saved without NomNom crashing. Additional clarity on whether the confirmation prompt (the one that pops up after editing the json and hitting ok) saves the changes to the save would be a nice bonus (is it supposed to save the account for me or is the user supposed to manually hit save account despite that confirmation?)
Files
NomNom 4.30.0.33-beta.3 Crash Report.pdf
save_with_bioship2_active.zip
Additional Context
Add any other context about the problem here or at least complete the following information.
The text was updated successfully, but these errors were encountered: