(MV) Can't view maps in copied file

[merboy22]

Hey everyone, I'm recovering a MV file that got a bug and stopped playtesting suddenly. I'm copy pasting all the original game's files to a new game. I haven't copy pasted any data over because I don't know how to tell which data is bugged, but I realized this means I can't view my maps in the new game's map window (bottom left) because they are .json files. I can still access all the maps in the playtest, but can't edit them. I'm wondering if any one has tips about how to safely move data over when there might be a bug in the data. I've never really coded before so don't know how bugs work.

Could I just copy paste the new project's current "MapInfos.json" file to my desktop as a backup, so that if pasting the original game's data doesn't solve the problem I can switch them out again? Or do I run the risk of giving the new game a bug by doing that?

Any help is deeply appreciated, I put a ton of heart into this game and it really means a lot to me.

 

[Andar]

you made a mistake that would have been easier to correct before copying the mapfiles.

as you assume the mapinfo file tells the editor what maps exist, but it doesn't contain any other data.
you can try to copy over your old mapinfo file. If that is corrupted and doesn't work, you'll need to start with a new project.

The regular method to restore the maps would have been to start with a project with empty maps.
Then add enough new maps to that project to get the map number up to the number of the highest mapfile you have.
Only after all those empty maps are created, you copy over the mapfiles you have, replacing the empty maps with the surviving maps.

As for the database the usual way is from the other end as well. You would start by trying to open the damaged project, and each time it lists one of the files as unreadable you would replace it with the same file from the last backup (or a new project if no backup exists) untile the project opens, and then see what of your database survived.