Sometimes life kicks you where it hurts

If you have a basic understanding of how pointer tables work, you should be able to find some relevant to your data needs in a hex editor and be able to extract the data manually from an old backup. However, with disassemblies this is a bit more difficult, so I wish you luck at least on that end.

Hell, you could even probably just make a savestate and grab the level layout that way, then use the data inside the savestate to grab the object location info/mappings info.

 

Not relevent to the question at hand, but, I suggest starting to use a basic backup system. When I work on a hack, after making any major changes, I RAR up my hacks folder, date it, and give it a filename relevent to the change. I have a "s1hack_backups" subfolder next to my "s1_hack" folder to store them all in.

If you do this, or something simular, you can look back at earlier revisions to recover things, should anything like this happen again.

 

It's also a good idea to copy those backups to another drive, CD or flash drive in case your hard drive fails as well. If your hard drive fails and you don't do that, you not only lose your current work, but your backups as well which defeats the purpose.

 

You should have been doing nightly backups all along. I suggest doing what Katelynn said in the first reply before rebuilding everything again and wasting even more time with this project.

On top of nightly backups: use version control and make commits at least nightly (or after fixing bugs or doing steps of adding features). If something crashes, just go back to the last working revision. It's good for both crashed-based data loss (as the repo is never touched by programs other than those that manage the repository) as well as testing new things (as you can make branches and add new features in those branches and then merge them back if you're confident of the features). I suggest using git so you don't have to worry about setting up a server.

 

Andlabs, is there a way to set that up locally, without some sort of server or other location to store the repo?

 

Yes, with git just go into the folder where you want your program and

Code (Text):

1. git init

git is decentralized so there's no central server; "servers" like github are just canonical servers that everyone agrees is the source for de facto builds. There's also a TortoiseGit for Windows users but I haven't had it work.

 

It would help if someone would make a new tool like SonED2 that isn't shit.

 

Then set it to an automatic backup =P

Anyway good luck with everything (including work) =P

 

If only SonEd2 had a data restore system ala chrome or IE restart previous websites, it would be much easier for hackers to backup (takes less space)
In fact, why doesn't it have savestates like SonMapEd?

 

Can you clarify something?

I would hardly call a single session of SonED2 "months of hard work".

The only way I can understand the loss of "months of hard work" is if the crash caused damage to your only copy of the disassembly. Which would imply, as implasuible as it is, that you have no backups, no version control, no archive of previous builds...

Sometimes it takes a hard lesson to make people learn. Download this.

Spoken like someone with vast and extensive experience with the tool. Moron.

 

Edit: eh, the pissing contest isn't worth it

Hope you're able to get back to where you were, Hitaxas.