6 réponses à ce sujet

[DragonTayl]

 Okay. I was just scared out of my pants. Not a pretty site. 

I was working on my module. I did a lot of work today. I saved it in order to go test the stuff I'd made and remembered one more thing I wanted to tweak before testing, so I re-opened the toolset and went into my module. 

It was empty.

No areas, no scripts, no conversations, no bluprints, nothing.

The module properties showed the tag and start location for the correct area and location as if the area still existed, but it did not. It was completely gone. 

Now, I only lost one day's worth of work (though it was probably the most work I'd done in one day because I had lined up the chance to work on it and carefully hoarded my time) because I do regular backups, but I want to know if this has happened to anyone else, if there is some sort of pattern, or if there is some sort of extremely easy way to erase all the contents of your module when you think you are actually saving it. My goal is to make sure I don't cause this to happen again.

I'm extremely frustrated I have to do everything I did today over again (and I'm not sure the next time I will have this many hours together) but grateful I have backups. 

This happen to anyone else?

[Morbane]

probably happened before - with the toolset i would not be surprised

2 things to check:
turn off autosave
save in directory mode

there are more things but those are the big 2

okay 1 more
dont save on exit - the toolset can crash and zip everything
so save before exiting and say "no" on exit

[andysks]

Yes I also heard about the big 2.
One time I saved on exit and the toolset crashed, after that never again. I was lucky I didn't lose anything but I realized I had to be very careful with the program .

[Lugaid of the Red Stripes]

Something like that happened to me yesterday, too. When I loaded the toolset, it choked or something, and didn't properly read some of its configuration files. The default settings were turned back on, with autosave and no community modules. When I want to load the module, it didn't actually load, just showed the blank lists of content. I was able to load a smaller module, though.

So, I made a new module, saved it as a directory, and moving the files from the old module into the new directly, and loaded it up. That seemed to work well enough, with only the module properties being lost.

[DragonTayl]

Turning on directory mode right now. I didn't know about that one. Thanks. Though I did have autosave off.

I think it was the save on exit. I almost NEVER save on exit, but I did that time.

It only took me about 2 hours to recreate my work, because I knew exactly what I was doing instead of experimenting and trying to find what I wanted, but still. Two hours I didn't have. Technically speaking. Ah well. I used to thrive on little sleep in college.

[andysks]

On a similar matter, I get this issue quite often. I open a conversation, and then the conversation list is blank. I need to highlight them all in order to see them to select one. It works, I never lost any data, but it still scares me a little :3 .

[Morbane]

Dragon - glad your work was quickly redone

Lugaid - i had to do that once as well - hasnt happened again though

andysks - that happend a few time to me - i just restarted the toolset to avoid any possible crash potential - TS crashes can be deadly and unexpected