I used tesfiles to extract my working set (fabulous tool, BTW), and I'm down to about 900MB. This is pretty much the core, though I may add more textures once the interiors get going, so I'm thinking I could hit 1GB easy.

Too much, just right, or keep plowing?

Thanks!
-Morovir

If the mod is worth it, size is not an issue. Also remember you may be able to compress that down by 40% - 50%.

And I was worried that the 70Mb uncompressed of the new NoM could be too much, go figure...

I don't consider the size of a mod before getting it. Hard drive space can be had cheaply, and broadband speeds are sufficiently fast to grab anything in a short time.

Size doesn't matter, if the mod is worth it I'll grab it. Though some people worry about those will poor download speeds, or finding hosting space, it's always possible to split the archive into several smaller parts that the user would have to recompile before use.

i never really care to much about the size of a mod either. ill even download mods that are so large ive had to download multipal files. it really is all about quality. mods get better , textures higher quality, more scripting possibilities you just have to accept larger file sizes. heck. when mournhold expanded first came out i still had dial up. and went and watched television for the 4 hours it took to grab that one

In addition, using appropriate texture resolutions, DDS compression and 7-zip for archiving can really decrease the size of the download.

Morrowind and its mods can never be too fat. Only you HDD can be too slim.

I like my Morrowind excessively obese, to the point where it almost dies crashes!

I define poor size as bad packaging. If the mod is bloated because of poor file format or layout, it's too big. But if it's quality and my game/computer can handle it, I'm just fine with it. I really wouldn't care if a mod was several gigs in size just so long as the content is worth having. Truth be told, I don't even look at size before I dl a Elder Scrolls mod unless my HD is looking kinda slim.

Well I bought Oblivion yesterday.. Browsed through some replacers and I was shocked when a simple silver bow replacer took about 12 mb, a freaking bow lol! 70 mb for a great addition as NoM won't be a problem

I find it lovely that even though I mod the vanilla game completely out of existence in morrowind. I am still able to run it swimmingly, yet with Oblivion on the PC it lags. and lags, and lags, and lags, so I got a refund and exchanged it for Xbox

Seconded. As long as the mod is good/great/fantabulous and maybe provides something new and original, size isn't a problem. And I strongly suggest you to use powerful compressing tools such as 7z which can really trim down the mod's size.

EDIT: you also made me curious about the mod, may you provide some details about it?

Never care about the file size :icecream:

if you make a mod that contains many new stuff (New models and Textures) the size increase rapidly...

Even Breton Boys got to shout, Morrowind got back!

http://www.gamesas.com/index.php?/topic/1094376-wip-ravenwood-island/page__view__findpost__p__15978347__fromsearch__1

Pffft, please... for NOM, I'd download it even if it was 7 GB!
And yacoby's right. If the mod is worth it, who cares about the size. We can't keep trying to compensate for everyone who has an old machine with only 250 Kilabytes of hard drive space. We must press forward and think outside the box, and push mods into the petabyte, exabyte, zettabyte and even yottabyte stages. (I doubt all the hard drive space in the world combined even equals one exabyte lol)

Even the ancient laptop I run has over 2 GB worth of mods on it, and I still need to re-download Alakazar's Lamp. 900 MB is nothing.

Too big is when it is so large that the author never finishes the mod and so it never gets released.

This.

That's not a big deal, but the usual rules for large files apply:
- Break it up: redownloading one 100mb chunk is easier than redownloading the entire 700mb mod, and the corrupt bit will be in the middle.
- The larger a file, the more likely it gets corrupt. Break it up.
- Add recovery records to the archive.
- Use a high-compression tool. WinRAR usually does a much better job than 7-zip for Morrowind mods (25% vs 40% compression for 130mb of textures, on my benchmarks).
- If you can, use a high-density multimedia compression tool and bundle it with your mod. Include a batch file to extract it (UHARC is one of the best available).
- If you include screenshots or a readme, do not include them in a solid archive. If I want to see screens, I may do that before extracting a gig to my HDD.
- If you have a lot of stuff, turn up the compression and turn on special modes. Make a solid archive, it's smaller.
- Do not assume anything, especially not path names above Data Files.
- Do not create an SFX or installer, unless you absolutely need it or are using a rare compression tool (see the tip on UHARC).