9 réponses à ce sujet

[ColorsFade]

 I've been saving my work as a directory. I am wondering if I should convert to a .mod file now, or later, and if so, how does that affect things?

The reason I've saved it as a directory, up to now, is so I can easily use Source Control and recover/revert files. 

[kamal_]

Only save as .mod for release (if then, I release as directories).

[andysks]

They say directory is more stable, and who am I to argue ?

[Dann-J]

I've only ever worked in module mode, and haven't had any problems. Not that my modules are very big though.

[Dann-J]

Converting it to a MOD now and then for backup purposes might be useful (it saves you precious seconds zipping up a folder). Otherwise, if you're working well in directory mode then you might as well wait until you're ready to upload something before converting it all to a MOD.

[Lugaid of the Red Stripes]

Somehow I remember that the module description only correctly displays in-game with a .mod file. You should always work in directory mode, though, since it only corrupts your module one area at a time. The toolset like to crash when saving .mod files, and when it crashes, everything is corrupted at once (there is a temp folder to look at, though).

Directories are also good for looking through your files outside of the toolset. You can cut and paste between directory-modules without having to deal with erf's.

[ColorsFade]

I'll stick with directory mode then. It's easier on the source control.

The toolset tells me that if I change it to a .mod, the directory will be deleted... that's what scares me.

[4760]

And it does delete the directory. But you can still save a copy of the directory BEFORE converting to a .mod