If you replace data of exactly equal size, comparatively little work is done, as it's only replacing the data.

If the new data is larger than the original data, then a lot of changes have to be made, everything stored under that data has to be moved, and other changes have to be made to accommodate this.

If you added entries, and left everything else alone, it's only a matter of throwing the new data at the end of the file and again, making changes to the files to reflect the additions.

Basically, when FE recompiles all these archives, it has to recalculate offsets and sizes for pretty much everything that gets edited, added and moved. It's not a problem with FE, just the computer using it.

So it doesn't freeze, it works, hard.

See Hunter, I do learn from our conversations.

Files:
So, in the very unlikely event that you make changes to every file, at the very top, replacing things with different amounts of data, you're looking at processing roughly 1502 MB (the laptop killer).

More realistically, for a semi-extensive mod, you're looking at anywhere from 500 to 700 MB, which is still a lot.

• When making mods, add completely new data without editing anything else, or if you must make edits make sure everything is the same size as the original. This will significantly cut down recompile time. Unless of course the mod is intended to replace original data, in which case this idea is useless.
• Recompile files one at a time. So it's not quicker in the end, but if the long wait absolutely drives you crazy, doing them individually may make you feel better.
• To hell with the wad file. Use tngs. It's easier, faster edits, no compile time, it's all good.

The simple fact that I'm saying these things doesn't mean it's true and accurate, as I didn't make FE. So...

This article or section is missing citations or needs footnotes.

If anyone knows that I'm wrong in any of this, let me know (pretty please).

Update: I'm covered.