Skip to content
This repository has been archived by the owner on May 1, 2022. It is now read-only.

Duplicating and renaming issue #7

Open
Sim-ian opened this issue May 8, 2020 · 4 comments
Open

Duplicating and renaming issue #7

Sim-ian opened this issue May 8, 2020 · 4 comments

Comments

@Sim-ian
Copy link

Sim-ian commented May 8, 2020

Hi i have used the save editor to create a copy of my Early access game so i could try it on the Experimental branch. The duplicated version shows up in the game load list as i named it but when i try to save it only allows me to save it under the original session name group and not the newly named session name. Also once loaded the session name in the bottom left of the ESC screen is not showing the new session name but the original session name.

@AyrA
Copy link
Owner

AyrA commented May 8, 2020

Saving the file under a new name will not change the session name. To change the session name you can either use the "General Actions" menu of any loaded file, or you can right click on any file in the save file manager window and use the rename option to specify a new file name and/or session name.

@Sim-ian
Copy link
Author

Sim-ian commented May 8, 2020

I have tried both using the file manager window and opening the file and using the General Actions Edit Header option. It does create a session group in the games load file window and i load the save from there but when i save it only gives the option to save it in the original session group and all the auto saves go in the original session group. All the other session groups are greyed out and unselectable in the save window in game.

@AyrA
Copy link
Owner

AyrA commented May 8, 2020

I had a look at it and it seems that the session name actually exists at least 4 times across the entire save file. It'll take me a while to fix that because the two additional copies I was unaware of are in a part of the save file that my editor is not reading.

@Sim-ian
Copy link
Author

Sim-ian commented May 8, 2020

No problem, just glad you are aware of it and now have the chance to fix it. Nice job on the editor by the way.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants