Let's say you open WED, build a level and then save it. When you save the level you create a new folder (let's call it LevelStart) to save the files in. Later, for whatever reason, you delete the entire LevelStart folder. The next time you start up WED LevelStart is automatically created. If you click the NEW button then palette.pcx is created in the LevelStart folder.

This is bad (in my opinion). Perhaps I have archived the level onto a CD and I no longer need the folder on my hard drive. Why should WED create it for me? Perhaps I started over, created a folder with a different name and, therefore, I no longer need the folder called "LevelStart". Why should WED automatically create this folder for me? It should not.

Secondly, who here is making games that are restricted to only 256 colors? No one? Then why does WED even bother to create a palette.pcx file? Perhaps there is someone out there that wants to create a legacy game that requires a 256 color palette. Fine. Give then the OPTION of saving out a palette.pcx but DON'T make it mandatory every time you create a new level in WED.

WED should NEVER write a file or folder to my hard drive without my permission.

Amen to that!

I like a clean development folder. I like game.wdl and game.wmp and that's all I need in that folder. I don't even keep my .wmb in there so when what Dan describes happen and I end up with upwards of fourr more files that I don't need to reference (pallete.pcx, game.wed, game.$$w, game.$$m) it annoys...badly.

Oh yeah, and what about standard.wad? I thought that was taken care of and store with the level so that we shouldn't have to reassign whenever a project moves to a differnet folder (like A6 to A7 or release vs. beta or 32 bit system to 64 bit system (and it's program file (x86) flder), etc).

I'll check if WED needs the folder and palette for some reason; if not, we make the palette optional and won't generate a folder at all in future versions.

Fastlane, Michael made a nice little cleaner for this situation. Create a .bat file, call it acklean.bat and copy inside this Code:

---

@echo off
del *.$$M /s
del *.bak /s
del *.$$w /s
del *.$$p /s
del OUIETERR.TXT /s

---

Put the .bat file in your directory and if executed will remove those files. The backup files are there for a reason though.

I save my batch files for starting many 3dgs applications back to back... not for cleaning up after uncessesary file creation.

It's a nice workaround but requires you to run it every time... not my cup of tea. I've never used the backup (that I"m aware of) and thus don't need this in the first place.

Well batch files are not only for starting files, but that's another point. I just wanted to let you know your options right now. If you have problems with pressing on a batch file, then maybe automate it with WED's SDK.