one omega wad file Created 19 years ago2005-01-07 23:57:20 UTC by mimic751

would this be a bad thing???? if i just combined every wad into one big one... or would the download time be astronomical?

That wouldn't just be bad. That would be catastrophic. If someone were to download your map, they woukld have to download the wad too, and if you've combined all your wads, the file size would be gargantuan! So, no, it is defintely NOT a good idea.

Nope, not at all. What you can do however is use a wadinclude in the CSG Compile line. This will include the textures that you've used in the map so that, come distribution time, people won't have to download the WAD files.

But yeah, as WCD said, not a good idea.

would this be a bad thing????

Simple Answer: Yes

just take out the textures you acctually used.

And if the .wad file includes HL.wad... you can just leave...

I did this once, it wasn't THAT bad as you think..

-wadinclude and you are perfectly fine.

don't forget -wadautodetect along side -wadinclude too - removes crappy wads that some people include, like gfx.wad, fonts.wad and cached.wad

If your map used completely original textures you might use -nowadtextures

Its worth to note that those switches include textures as opposed to wad packages

Have a look at your map information to give you an idea of your texture usage. If it says its 2 MB, then your BSP will be up to 2 MB larger - sometimes smaller, sometimes even larger than that.

thank you

Just combine all your custom wad files... (not including hl.wad, xeno.wad)

Before the final compile, take all the custom textures you use and put them in a wad, then wad include that. It's the most space-saving way to do it.

To use -wadinclude, you also put the NAME of the wad after that right? Or does -wadinclude... include all wads used in the map automatically?

"-nowadtextures" does what you described.

"-wadinclude mywad.wad" includes mywad.wad